[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on FORGE-719: ------------------------------------------- My biggest gripe/concern with the current Forge approach is that it is all very "(re)action based". i.e. plugins seem to follow the pattern of "ask user question 1,2,3,4 (based of the cmd annotations)", do something - realize something was not possible to ask about via cmd annotations "ask user question 2,3,4", do something, "ask user some more questions", do things. This is all great in a cmd-line world but really really hard for newbie users to grok (IMO) and when you actually have to do or combine multiple forge level operations things becomes really hard from an IDE user perspective - i.e. IDE users expect to be able to just press Cancel in a multi-step wizard and not see any change in his project from that, also when driving from the IDE, we'll need to be able to call out to Forge and query for the possible values etc. (something the current 'single Is this issue about solving/improving this challenge or "just" about providing an UI on top of the existing "cmd line/reaction pattern" ? Things to consider here is how forge can provide rich enough info to have "Browse.." buttons work for file/resource, database resource selection, etc. And how a multistep wizard could be created outlining pages needed to provide the questions ...and in a way that does not require fully running forge inside something like Eclipse. -- 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