[jbosstools-issues] [JBoss JIRA] (JBIDE-10264) Wizard-ify the project examples
Snjezana Peco (JIRA)
jira-events at lists.jboss.org
Wed Feb 15 18:17:36 EST 2012
[ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Snjezana Peco resolved JBIDE-10264.
-----------------------------------
Resolution: Done
Fixed according to Max's suggestions.
The Requirements and "Project ready" pages have been changed.
> Wizard-ify the project examples
> -------------------------------
>
> Key: JBIDE-10264
> URL: https://issues.jboss.org/browse/JBIDE-10264
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: project-examples
> Affects Versions: 3.3.0.M4
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 3.3.0.Beta1
>
> Attachments: jbide-10264page1.png, jbide-10264page2.png, jbide-10264page2.png, jbide-10264page3.png, jbide-10264page4.png, jbide-10264page4.png, jbide-10264page5.png, simplified-workflow.bmml, simplified-workflow.png, wizardsuggestion.bmml, wizardsuggestion.bmml, wizardsuggestion.png
>
>
> In the wake of JBIDE-9776 and JBIDE-10140, it turns out that, in order for us to contribute 5 new wizards to the "New " menu under the Jboss perspective and in the "New project" section of JBoss central, "project examples" based projects should be created via a Wizard implementation from the get go.
> Current project examples workflow involves :
> - displaying a form dialog : to display missing runtimes and let the user install/download the required runtimes
> - launching a workspace job, which in turn :
> * downloads the example
> * does the actual project import (launches a wizard for maven archetypes)
> * resolve quickfixes
> Ideally, all these steps would be part of a single wizard, spanning one to N pages (depending on the complexity/requirements of the examples). Everything contributed by the form dialog would be replaced by a wizard page, which would bring consistency to the UI.
> In other words, that means the project example dialog needs to be refactored into a Wizard, providing an API so that client plugins can contribute wizard pages.
> I'm aware this is not a simple task to refactor the existing workflow to such an infrastructure but ultimately, that would allow us to easily contribute new project wizards to the IDE in a standard way.
> Current target is 3.3.0.Beta1. Snjeza, WDYT?
--
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
More information about the jbosstools-issues
mailing list