[
https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-19178:
---------------------------------------
[~maxandersen] It's not clear to me how this now mock up differs from the original one
I proposed. I thought your concerns with the original proposal was that there was too
much 'tree' in the overall view, and that it would be cleaner to limit the
explorer view to minimal amount of resource info. The supporting resources and details
(e.g. deployments, builds) would be represented in a tab of the properties view. I think
this approach would make the explorer look MUCH more like v2 and off load many of the
other details into properties. I image this approach would give you something simple
like:
{noformat}
service (route)
|-pod
{noformat}
My biggest issue is that all the supporting details would be in a properties view, but
maybe that doesn't matter since we are trying to hide them (sort of) from the
developer. I do think something like builds are of interest and maybe that is a
'right-click' on the 'app(service)' to open the properties view.
Also, we do have an open issue (I believe) to add label filtering to the current view
which would make sense to carry over into this one.
Explorer, Servers view: Add logical view to OpenShift v3 explorer
-----------------------------------------------------------------
Key: JBIDE-19178
URL:
https://issues.jboss.org/browse/JBIDE-19178
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Alpha1
Reporter: Jeff Cantrill
Labels: explorer, openshift_v3
Fix For: 4.3.x
Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of
'App' with the pieces wired.png, Pipeline view mockup.bmml, Pipeline view
mockup.png
Add an alternate view in the openshift v3 explorer to try to 'link' resources in
a similiar fashion to the web console
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)