[forge-issues] [JBoss JIRA] (FORGE-719) Design an user interface API for addons

[ https://issues.jboss.org/browse/FORGE-719?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on FORGE-719: ------------------------------------------- My comment about "fully running forge" was about not having to run Forge *inside* eclipse since that brings a whole slew of other problems with it. For this jira my concern is not about memory/performance/startup etc. thats a separate topic which I put on forge-dev so i'll leave that out of this part about UI interaction. This one is about how we avoid having Eclipse users to have to relate to things like absolute paths, keep entering data that eclipse can already provide good defaults for and how to combine commands. The wizard UI api looks interesting, but would like to see an example of how it would be used to fully grok it. I'm not sure what you mean by "build a menu" and "generate metadata for eclipse to use to build its menu" - the wizard API talks about wizards which aren't menus ? And looking at the API its dynamic (understandably) so the wizard can't be generated/deduced before actually having the input data to know which pages to show etc. -- 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