[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15189: ------------------------------------- [~mmalina] [~rhopp] Do you guys have any good suggestions here for expected behavior? Should we simply not create the runtime if a compatible runtime isn't available? Should we add some UI popups that require user interaction? We have to remember that this dialog for runtime detection can open up on workspace startup OR from the runtime detection preference page, so whatever changes we make here should fit seamlessly in both situations. In some ways, I feel popping up a new dialog on top of the existing may be inappropriate or intrusive for the user. We also need to remember that the workflow may be in the process of creating several different runtimes in a row... is it better to allow each handler to open UI elements individually (with no unity for look-and-feel) or is it better for each to return some type of indication that further information is needed, and then conglomerate these into some type of wizard with multiple pages? I'm concerned that if two EAP folders are being scanned, for example, we may end up presenting the user with two identical pages for each runtime being scanned, and the user may not understand why multiple similar pages are being shown. I've played on paper with some ideas, but none of them seem like good solutions to me really... so it'd be great if I could get some additional feedback or ideas from you all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)