[jbosstools-issues] [JBoss JIRA] (JBIDE-10264) Wizard-ify the project examples

[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-10264: --------------------------------------------- I guess - you loose the info on wether this example will easily work. Maybe just add a single line warning/info label that additional requirements are needed? Huh ? Where else will you have the output directory ? You do - since they always will be there. Yes, so what is left is just the instructions that the projects have finished downloading and ready to use. Thus don't enable Finish ;) How do you ensure that the project is fully imported, the user knows what happened and he isn't doing something else that will trip the import or confuse the user when the "selection" of the project is implemented to make Run As work ? The problem now is that there is ~3 or 4 dialogs shown with different styling, layout, content dependening on what example you are using. Trying to align that. So you are saying you now in the code are waiting for the project build to finish before showing the quickfix dialog? That's ok for me - that mechanism works for both type of project examples. I'm not following you at all - I deliberatly did not show the selection of the example since that is *outside* this wizard flow. No, the download have to happen *before* those pages since these pages depend on the content/choice of this afaics. A project examples that don't contribute some page and start from JBoss Central B project examples that don't contribute some page and start using Help>Project Examples C project examples that contribute some page (mavenArchetype) and start from JBoss Central D project examples that contribute some page (mavenArchetype) and start using Help>Project Examples Why do you see *any* need for a different workflow when starting from project examples or central ?! The only difference is the starting point (which I claim should have no impact on the flow) and then wether it is a maven archetype or not - and the suggestion here just relate to having one more page shown or not. The *only* optional page is the wizard archetype - the rest is there no matter which flow you suggest. The suggestion here is actually to make the "old" project examples behave more sane. The maven archetype is way less confusing than the old project examples (i.e. it provides options to how the project is named and where it is stored, project examples shows it up front on top of all the content - ugly and non-intuitive). The "old" project examples shows just as many dialogs as i'm suggesting pages (see previous discussion). If you don't like this suggestion please suggest how to fix the current weird old example workflow ? And I understand my suggestion has problems too with the download part - but i'm then fine to just remove the "move to background" download, then the flow has no "gaps". What would be good then is to actually cache these examples...maybe we should simply just release them as bits to mvn repo and use aether to get them for built-in caching ? Then there would be no delays the second time you use the wizard. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira