[JBoss JIRA] (JBDS-3490) Include Capabilities preference page into jbdevstudio product
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3490:
--------------------------------
Attachment: jbds-capabilities.png
> Include Capabilities preference page into jbdevstudio product
> -------------------------------------------------------------
>
> Key: JBDS-3490
> URL: https://issues.jboss.org/browse/JBDS-3490
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: javascript, target-platform
> Affects Versions: 9.0.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 9.0.0.CR1
>
> Attachments: 3490-error.png, jbds-capabilities.png, jbds-preferences.png
>
>
> Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug for example tern related issues.
> Current approach is using capabilities to hide Tern category from Preferences and Properties dialogs. If something goes wrong there is no way to see preferences and properties in hidden categories, because Capabilities Preference page is not included into ibdevstudio product. Before it was included by default but in Mars release it seems moved to EPP side. For example Committer Package does not provide Capabilities preference page, but Java EE Package does.
> In current devstudio product package preferences categories looks like
> !jbds-preferences.png!
> as you see there is no Capabilities node in categories tree (1) because Capabilities preference page is not defined for jbdevstudio product and Tern node (2) is filtered out by default. It means in case of any problem with tern it is not possible do enable tern console tracing using Tern Preferences or see node.js configuration.
> It is probably should be implemented as additional feature/plugin to include it into JBDS product, but it should beexcluded from BYOE feature to avoid preferences categories conflict in case of installation BYOE feature into Java EE EPP.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBDS-3490) Include Capabilities preference page into jbdevstudio product
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3490:
--------------------------------
Summary: Include Capabilities preference page into jbdevstudio product (was: Include capabilities preference page into jbdevstudio product)
> Include Capabilities preference page into jbdevstudio product
> -------------------------------------------------------------
>
> Key: JBDS-3490
> URL: https://issues.jboss.org/browse/JBDS-3490
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: javascript, target-platform
> Affects Versions: 9.0.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 9.0.0.CR1
>
> Attachments: 3490-error.png, jbds-preferences.png
>
>
> Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug for example tern related issues.
> Current approach is using capabilities to hide Tern category from Preferences and Properties dialogs. If something goes wrong there is no way to see preferences and properties in hidden categories, because Capabilities Preference page is not included into ibdevstudio product. Before it was included by default but in Mars release it seems moved to EPP side. For example Committer Package does not provide Capabilities preference page, but Java EE Package does.
> In current devstudio product package preferences categories looks like
> !jbds-preferences.png!
> as you see there is no Capabilities node in categories tree (1) because Capabilities preference page is not defined for jbdevstudio product and Tern node (2) is filtered out by default. It means in case of any problem with tern it is not possible do enable tern console tracing using Tern Preferences or see node.js configuration.
> It is probably should be implemented as additional feature/plugin to include it into JBDS product, but it should beexcluded from BYOE feature to avoid preferences categories conflict in case of installation BYOE feature into Java EE EPP.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBDS-3490) Include Capabilities preference page into jbdevstudio product
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3490?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3490:
--------------------------------
Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/336, https://github.com/jbosstools/jbosstools-base/pull/445 (was: https://github.com/jbdevstudio/jbdevstudio-product/pull/336)
> Include Capabilities preference page into jbdevstudio product
> -------------------------------------------------------------
>
> Key: JBDS-3490
> URL: https://issues.jboss.org/browse/JBDS-3490
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: javascript, target-platform
> Affects Versions: 9.0.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 9.0.0.CR1
>
> Attachments: 3490-error.png, jbds-preferences.png
>
>
> Currently there is no way to enable/disable capabilities to see hidden nodes in preferences/properties dialogs. It might be needed as a backup to be able to debug for example tern related issues.
> Current approach is using capabilities to hide Tern category from Preferences and Properties dialogs. If something goes wrong there is no way to see preferences and properties in hidden categories, because Capabilities Preference page is not included into ibdevstudio product. Before it was included by default but in Mars release it seems moved to EPP side. For example Committer Package does not provide Capabilities preference page, but Java EE Package does.
> In current devstudio product package preferences categories looks like
> !jbds-preferences.png!
> as you see there is no Capabilities node in categories tree (1) because Capabilities preference page is not defined for jbdevstudio product and Tern node (2) is filtered out by default. It means in case of any problem with tern it is not possible do enable tern console tracing using Tern Preferences or see node.js configuration.
> It is probably should be implemented as additional feature/plugin to include it into JBDS product, but it should beexcluded from BYOE feature to avoid preferences categories conflict in case of installation BYOE feature into Java EE EPP.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20082) Application wizard: it's not userfriendly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20082?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-20082.
---------------------------------
Resolution: Partially Completed
* dont show just long list of variables with no particular order: variables listed alphabetically now
* warn/error about required fields (or at least make templates that works out of the box - i.e. have git refs filled out): done, now supports templates with required parameters
* label page has no information/context on what its needed for: done
* let me see what is going to be created before creation happens: done
* let me delete/undo the creation (i.e. if parts of it fails its tedious to cleanup after it): partially done. OS3 doesn't support atomic operations, so we at least detect resource name collisions BEFORE actually creating anything
* let me edit fields by double clicking - now i need to edit: done
The following is not covered:
* find a way to only show the important fields and put rest under "advanced" or something similar to avoid the "wall-of-variables": we have no way to know which fields to show/hide, except for the required ones.
> Application wizard: it's not userfriendly
> -----------------------------------------
>
> Key: JBIDE-20082
> URL: https://issues.jboss.org/browse/JBIDE-20082
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.0.CR1
>
> Attachments: defined-resources-button.png, explanation-for-labels.png, projects-combo.png, template-resource-details.png
>
>
> The feedback from various sources says that the current implementation of the application wizard that creates an application on OpenShift v3 via templates is not userfriendly.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-19975) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19975?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19975:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.CR1)
> v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19975
> URL: https://issues.jboss.org/browse/JBIDE-19975
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.x
>
> Attachments: edit-template-parameter-value.png, required-value-decoration.png
>
>
> # ASSERT: make sure that you have a connection to a v3 OpenShift server
> # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection
> # ASSERT: new application wizard pops up, listing your project
> # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next"
> # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit"
> # ASSERT: editing dialog pops up
> Result:
> !edit-template-parameter-value.png!
> "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value?
> # EXEC: provide some value and back in the wizard page hit "Next"
> # ASSERT: "Resource Labels" page shows up.
> # EXEC: Hit "Add"
> # ASSERT: dialog pops up so that I can create a new label
> Result:
> !required-value-decoration.png!
> The dialog decorates missing values with a red error marker.
> In OpenShift tooling we usually use "*" when required values are missing, not the error icon.
> Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19181:
--------------------------------
Issue Type: Task (was: Enhancement)
> correct naming of internal packages so that they're consistent across all openshift plugins
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-19181
> URL: https://issues.jboss.org/browse/JBIDE-19181
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.x
>
>
> Internal packages across the openshift plugins are non-consistent:
> ex.
> org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal
> org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal
> the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins.
> For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages
> {quote}
> org.eclipse.jdt.internal.core.compiler - Correct usage
> org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name.
> org.eclipse.core.internal.resources - Correct usage
> org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
> org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-19181) correct naming of internal packages so that they're consistent across all openshift plugins
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19181?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-19181:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.CR1)
> correct naming of internal packages so that they're consistent across all openshift plugins
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-19181
> URL: https://issues.jboss.org/browse/JBIDE-19181
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.x
>
>
> Internal packages across the openshift plugins are non-consistent:
> ex.
> org.jboss.tools.openshift.client: org.jboss.tools.openshift.client.internal
> org.jboss.tools.openshift.express.client: org.jboss.tools.openshift.express.client.internal
> the base is imho org.jboss.tools.openshift and thus internal packages should always be at org.jboss.tools.openshift.internal across plugins.
> For reference, here's the official Eclipse documentation on the topic: http://wiki.eclipse.org/index.php/Naming_Conventions#Java_Packages
> {quote}
> org.eclipse.jdt.internal.core.compiler - Correct usage
> org.eclipse.jdt.core.internal.compiler - Incorrect. internal should immediately follow subproject name.
> org.eclipse.core.internal.resources - Correct usage
> org.eclipse.internal.core.resources - Incorrect. internal should never immediately follow org.eclipse.
> org.eclipse.core.resources.internal - Incorrect. internal should immediately follow Eclipse Platform component name.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20023) Show in browser: missing project/server that we're listing the routes of
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20023?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20023:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.CR1)
> Show in browser: missing project/server that we're listing the routes of
> ------------------------------------------------------------------------
>
> Key: JBIDE-20023
> URL: https://issues.jboss.org/browse/JBIDE-20023
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: help_wanted, openshift_v3
> Fix For: 4.3.x
>
> Attachments: show-in-browser-routes.png
>
>
> how to reproduce:
> # ASSERT: make sure that you have a project with several routes on a v3 OpenShift server
> # ASSERT: make sure that you have a connetion in explorer to this server
> # EXEC: in Explorer: unfold Routes and pick "Show in->Web Browser"
> Result:
> !show-in-browser-routes.png!
> A dialog requiring to select the route that you want to open up in the browser pops up. The dialog wont tell you what server, project the routes are listed for.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20023) Show in browser: missing project/server that we're listing the routes of
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20023?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20023:
--------------------------------
Labels: help_wanted openshift_v3 (was: openshift_v3)
> Show in browser: missing project/server that we're listing the routes of
> ------------------------------------------------------------------------
>
> Key: JBIDE-20023
> URL: https://issues.jboss.org/browse/JBIDE-20023
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Priority: Minor
> Labels: help_wanted, openshift_v3
> Fix For: 4.3.x
>
> Attachments: show-in-browser-routes.png
>
>
> how to reproduce:
> # ASSERT: make sure that you have a project with several routes on a v3 OpenShift server
> # ASSERT: make sure that you have a connetion in explorer to this server
> # EXEC: in Explorer: unfold Routes and pick "Show in->Web Browser"
> Result:
> !show-in-browser-routes.png!
> A dialog requiring to select the route that you want to open up in the browser pops up. The dialog wont tell you what server, project the routes are listed for.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months