[JBoss JIRA] (JBDS-3719) Initial search for an existing JBDS is present but disabled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3719?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3719:
--------------------------------
Fix Version/s: 10.0.0.Alpha1
> Initial search for an existing JBDS is present but disabled
> -----------------------------------------------------------
>
> Key: JBDS-3719
> URL: https://issues.jboss.org/browse/JBDS-3719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
>
> The installer calls the functionality to search for an existing JBDS when the confirm page loads, but the method has a built-in check that just interrupts it. Meaning - checking an existing installation will only proceed if a folder was selected by the user, the initial search will not.
> Is this by design? If it is there is no point in initiating the search automatically.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3697) Installed vagrant version in not validated against anything
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3697?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3697:
--------------------------------
Fix Version/s: 9.1.0.GA
> Installed vagrant version in not validated against anything
> -----------------------------------------------------------
>
> Key: JBDS-3697
> URL: https://issues.jboss.org/browse/JBDS-3697
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> It looks like the installer stores the version of a vagrant installation it finds/the user selects, but there is no value it would check it against. (Which is strange because I remember putting it into the code and the html file still references the fields which apparently don't exist anymore).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3696) Browse buttons should not respond when a file dialog is opened
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3696?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3696:
--------------------------------
Fix Version/s: 4.1.4.GA
> Browse buttons should not respond when a file dialog is opened
> --------------------------------------------------------------
>
> Key: JBDS-3696
> URL: https://issues.jboss.org/browse/JBDS-3696
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 4.1.4.GA
>
>
> Clicking the 'Browse' buttons on confirm page opens a native file dialog. Once open, the user can just navigate back to the main window and keep clicking those buttons. What happens is - for every click a new dialog is queued up. Once the current one closes the next one in the queue will open. We should not allow this kind of chaining - it is fairly annoying.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3651:
--------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> Reduce the delay between the main window opening and the first page being rendered
> ----------------------------------------------------------------------------------
>
> Key: JBDS-3651
> URL: https://issues.jboss.org/browse/JBDS-3651
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: installer
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.0.0.Alpha1
>
>
> Starting the installer right now leaves the user with about 3 seconds of staring at an empty window before the content shows up.
> I've done a few tests on this matter and it seems majority of those 3 seconds is spent on angular bootstrap - mainly loading the required files and registering controllers. Replacing the index with simple static HTML causes the page to render almost instantaneously.
> We should consider some way of showing the GUI before the user falls asleep (before angular fully loads the entire app).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3642) Installer is too opaque - need a debug/verbose mode to track progress and debug failures
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3642?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3642:
--------------------------------
Fix Version/s: 10.0.0.Alpha1
(was: 9.1.0.GA)
> Installer is too opaque - need a debug/verbose mode to track progress and debug failures
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3642
> URL: https://issues.jboss.org/browse/JBDS-3642
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.GA
> Reporter: Len DiMaggio
> Labels: havoc
> Fix For: 10.0.0.Alpha1
>
>
> The install.log created by the installer does not contain a detailed listing of all actions performed by the installer. Setting the install browser into a debug mode ( "set PDKI_DEBUG=true" ) generated additional information, but it is still node a detailed dump of all actions. Can we add a debug/verbose/trace mode?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years