[JBoss JIRA] (JBIDE-16876) New Application wizard: page#1 needs fields disabled based on user actions
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16876?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16876:
---------------------------------------------
[~mlabuda] these all use the same workflow afaik (this wizard) thus if you remove the option of choosing existing application from that you remove it from all these...
> 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
12 years
[JBoss JIRA] (JBIDE-16876) New Application wizard: page#1 needs fields disabled based on user actions
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16876?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-16876:
---------------------------------------
[~maxandersen] yeah, if that was only way, it could be annoying :) But there is still third way - Servers view - add server and import application from OpenShift from this place. To be clear - we have now 3 ways, how to import application:
1) New application wizard - there are 3 ways how to open it:
a) OpenShift explorer (context menu of connection or domain, select New - Application...)
b) Shell menu (File - New - OpenShift application)
c) JBoss Central
2) From servers view - context menu New - Server, choose OpenShift - OpenShift server, click Next button and there is Import this application link
3) OpenShift explorer - from context menu of application
I agree, that first choice - through wizard - is fastest, but it also need some agreement on UI - previous UI, as I have mentioned, was overcrowded and with new features (support for downloadable cartridges) it would be much more overcrowded. Maybe task for UX team to find some better solution?
> 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
12 years
[JBoss JIRA] (JBIDE-16876) New Application wizard: page#1 needs fields disabled based on user actions
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16876?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16876:
---------------------------------------------
btw. importing wizard (removing page or rather skip) can still be done by the import in openshift explorer just starts on the second page.
> 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
12 years
[JBoss JIRA] (JBIDE-16876) New Application wizard: page#1 needs fields disabled based on user actions
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16876?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16876:
---------------------------------------------
I'm not ok requiring that the only way for users to get an existing app is to open up the openshift explorer, add a connection, fill in details, wait for tree to load and then right click to import app.
versus simply start the openshift wizard and make a choice.
OpenShift should be possible to use without the user even knowing OpenShift Explorer exist. Just like you can use git,cvs, svn etc. without knowing about the repo browser.
> 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
12 years
[JBoss JIRA] (JBIDE-16966) Warning isn't shown if bom file is in local repository
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16966?page=com.atlassian.jira.plugi... ]
Rastislav Wagner edited comment on JBIDE-16966 at 4/1/14 7:35 AM:
------------------------------------------------------------------
Yeah, for maven its normal, but previous JBDS (I just tried JBDS6) shows warning even if I have bom in my local repo.
my mistake: bom in local repo wasnt -redhat version so maybe when JBDS6 checked for dependencies they werent downloaded ? Just guessing..
was (Author: rawagner):
Yeah, for maven its normal, but previous JBDS (I just tried JBDS6) shows warning even if I have bom in my local repo.
> Warning isn't shown if bom file is in local repository
> ------------------------------------------------------
>
> Key: JBIDE-16966
> URL: https://issues.jboss.org/browse/JBIDE-16966
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Beta1
> Reporter: Rastislav Wagner
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.2.0.Beta2
>
>
> When I try to import some central example (HTML5, JavaEE) no warning is displayed if jboss-javaee-6.0-bom is in my local repository. This is causing issues when I had enterprise repo in my settings.xml in the past but right now its not there (but bom was downloaded into my local repo).
>
> I think that in past we didn't check local repository right ? Why was this behaviour changed ? Is it because of offline mode ? In that case maybe we should check if maven is in offline mode, if not than we should check remote repositories, not local.
> Steps to reproduce:
> 1. open HTML5 wizard from central
> 2. add enterprise repo via warning
> ASSERT: warning disappears
> 3. close wizard
> 4. remove enterprise repo from settings.xml
> 5. open HTML5 wizard from central
> FAIL: no warning is diplayed even that enterprise repo is missing (only local repo contains javaee-6.0-bom)
--
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
12 years
[JBoss JIRA] (JBIDE-16876) New Application wizard: page#1 needs fields disabled based on user actions
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16876?page=com.atlassian.jira.plugi... ]
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
12 years