Red Hat Bugzilla – Bug 849761
UX: We need a comprehensive, scalable, and performant approach to large resource trees
Last modified: 2014-12-17 18:17:41 EST
For resource trees that may need to display large numbers of children/siblings we need to give the user something they can work with.
Today we protect ourselves from unbounded queries but at the expense of possible truncation/pruning of the tree.
More importantly we:
- Don't give any visual indication that the tree has been pruned (i.e. that we didn't pull all of the resources because there were too many).
- Pull a lot of resource that may not be necessary. For example, we pull all the direct children of a parent resource regardless of what the user may be trying to look at. We may want to consider pulling only the child *types* before we actually pull the instances of those types.
We need UX design for how the tree can best interact with the user while still not allowing unbounded data fecthes (perhaps easily leading them to a more paging oriented search/list view).
Per triage with loleary, crouch, mfoley: Move to JBoss ON product, set target release JON 3.2, clear priority (will be subject to further triage in JON 3.2 timeframe).
This is not going to make it into 3.3 and I'm not sure the priority merits keeping it, perhaps consider Won't Fix.
*** Bug 848853 has been marked as a duplicate of this bug. ***
See Bug 849761, which has been marked duplicate but may offer ideas if this ever moves forward.