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

[Snjezana Peco (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664327#comment-12664327 ] 

Snjezana Peco commented on JBIDE-10264:
---------------------------------------

I have a few questions:

1) The mockup doesn't show the first page when calling the Project Examples wizard using Help>Project Examples. Would it be as it is now?

2) If a project doesn't have any requirements, the Project Examples Requirements page wouldn't be shown. 
If they are satisfied, the Project Examples Requirements page would be shown with the "green checkmark" (JBIDE-10691). Right?

3) Why wouldn't we set the QuickFix/Readme checkboxes to the first page and remove the last page?

4) If there is a Quick Fix, would it be on the new wizard page or in the dialog as it is now?
readme/cheatseet have to be separated

5) 
> It would mean download start on Page 3 and if you choose to go in background and the job finishes the wizard will open up again starting from what would have been Page 4.

I am not sure what page you mean when saying Page 3 or 4. Do you mean the page I mentioned or a page in the mockup?

I can try to solve this, but it would be good if you would know an example of an Eclipse wizard that works this way?
I haven't succeeded to find any wizard that goes to the background and gets back at some point.
Wizards use a modal dialog. What will we do if the user opens some other wizard or a modal dialog when our wizard should be shown again?

6) The page containing "project name, package, ..." is specific for maven archetypes. It should be added as a contribution to o.j.t.maven.project.examples if we don't want to introduce maven dependencies to the project examples.

The  mockup seems to be created to solve project examples of the mavenArchetype type when they are called from JBoss Central.
I have understood that this jira requires creating a wizard that could be used for any type of project examples and could be used from JBoss Central as well as using Help>Project Examples.
As to the project examples of the mavenArchetype type, the problem has been solved by JBIDE-9776. It would be enough to make JBoss Central not to open the Project Example dialog for those project examples that have the "wizard" tag, but to call their implementation method directly.






                
> 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: 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