[ https://issues.jboss.org/browse/JBIDE-16896?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16896: ------------------------------------- There is no description in stacks unfortunately. Most of the info url's are all the same unfortunately. The table would look very repetitive. Fixing this for the credentials page, but I still believe the button has a proper place in the sign-tc page. Fixing this. These are specific workflow issues only seen when entering from the new server wizard. I believe a new bug should be opened for these two. > download runtime UI wizards has some weird workflow > --------------------------------------------------- > > Key: JBIDE-16896 > URL: https://issues.jboss.org/browse/JBIDE-16896 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.2.0.Beta2 > > Attachments: OS_signup.png > > > using download runtime the dialogs gets maxed out dependent on the lenght of the URL it looks like. > Making the wizard very clumsy to look and work with. > - the table is just taking up all space - and the url is not useful (can't copy/paste/link it) > - the table is in a dailog and there is 90% whitespace > How about > A) show the name and description in table > B) Show the *info* url and if authorization is required enable username/password on the first page instead of requiring a second page for just that ? > or at least tell the user to validate instead of just blanking out Next and *once* the credentials are valid actually show that isntead of just enabling Next. > D) the license text shown is LGPL license - not $0 subscription (opening separate bug for this) > F) when clicking finish the dialog returns instantly to JBoss Runtime creation and it tells me the home dir does not exist...why did it not fill it in and let me wait ? > G) It actually creates the server for me in the background *while* im in the server wizard flow....thats just weird. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira