[
https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10264:
---------------------------------------------
Following dialogs is shown for basic project example:
1) project example choice
2) details about "missing requirements"
3) wait for download (can be put in background)
4) open quickfix dialog
5) "open the readme.*"
Thus project examples even without maven have several steps.
dependency to m2e can be fixed by extensions point providing "UI" for specific
example types.
Any issue concerning "having UI block while downloading" can be solved by
providing a "go to background" for the wizard and once it has finished
donwloading showing a dialog reporting download have completed and we are now going to
import + open readme.whatever (unless user cancles) is worthwhile to "guide" the
user.
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
Fix For: 3.3.0.Beta1
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