[jbosstools-issues] [JBoss JIRA] (JBIDE-16876) New Application wizard: page#1 needs fields disabled based on user actions

[Marián Labuda (JIRA)]

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

Marián Labuda commented on JBIDE-16876:
---------------------------------------

I suggest to remove  whole first section (Import existing app) with this solutions:
1) New application Wizard should contain fields required in New application creating process (whole section with importing could be removed)
2) Removed importing existing app already exists in context menu of application - right click on application in OpenShift explorer and choos Import Application... After click on this item, new application wizard with preselecting first radio button is opened. After removing this part of wizard, it could be automatically set on the second wizard page (data from first wizard page would be processed before opening this wizard page) - where user made decision, whether disable maven build, whether import, whether create adapter. 

What this brings?
- simple and intuitive new application wizard
- importing become "faster" (removed wizard page)

What are cons?
- maybe some users used to use current approach for importing application (from New application wizard) and they could start wondering, what happened with it - but they also should be aware of importing from context menu of application in OpenShift explorer

Current first wizard page with tree of possible cartridges should stay - this is bcs. of adding quickstarts/templates in future as mentioned in JBIDE-14744 - I think, it does not matter whether there is only tree with cartridges and nothing else or not. Previously version of wizard was overcrowded - on single wizard page were cartridges, embeddable cartridges, name, gear size, scalability, domain, environment variables, field for providing template URL. So I strongly recommend to not revert this behaviour, just modify it.
                
> New Application wizard: page#1 needs fields disabled based on user actions
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-16876
>                 URL: https://issues.jboss.org/browse/JBIDE-16876
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.2.0.Beta1
>            Reporter: Michelle Murray
>            Assignee: Andre Dietisheim
>              Labels: application_wizard
>             Fix For: 4.2.0.Beta2
>
>         Attachments: create-new-application.png, import-existing-application.png, out-3.ogv
>
>
> In the New OpenShift Application wizard, user has two choices 1) use existing app or 2) create new app.
> * If user clicks 'Use my existing OpenShift application', then list of cartridges should be disabled. I was able to give name of app to import and then select cartridge which was meaningless as app was imported with original cartridge (as expected) and not the new one I had selected.
> *  If user clicks 'Create a new OpenShift application', the field for app name and browse button should be disabled.
> But this also raises the question for me as to why these two choices are shared on the same wizard page. I wonder if it would be cleaner to separate them.
> * So when in OpenShift Explorer view a user right-clicks an application and clicks 'Import Application' they would just see the wizard starting from the page 'Set up project for new OpenShift Application'. They've already decided they want to import so offering fields about creating a new OpenShift app isn't useful.
> * Similarly, when a user selects 'New > Application' then they don't need to be offered the information about using an existing OpenShift application. To me as a user, the action 'New > Application' makes me thing that I am creating a new OpenShift Application so having fields about using an existing OpenShift app is confusing.

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