For components with children, it would be nice to get the multi-column view for the children in the text view by default.
The multi-column view is associated with the platform collection type.
It's possible that #87 can also address this, if Components with children are given collection type properties.
oops, didn't mean to close the issue.
MultiColumnView now is able to display not just children components, but rather entire graphs of components (e.g: given a collection, MultiColumnView displays every component associated with a feedID, regardless of the component's depth in the collection, or whether there exists a cycle within the collection). (Pull request possibly today, but definitely tomorrow)
code altered: MultiColView.java
To clarify, I don't think visiting deeper components was the desired behavior here, but rather that the view was only available for Collection objects (and not the more general case of other objects with children, such as My Sandbox, which are not of the Collection component type)
Victor is correct that the original design of this feature was to suit the particular need of replacing an existing type of JPL's non-MCT display. But beyond JPL, and probably even for JPL, there is no need to restrict this feature's availability to "Collection" type objects. "Collection" object type was supposed to be a type for plain old dumb boxes. But darn near any type of object should be able to have children. Sounds like we need to spend some design thinking time....
Thanks - that is what I meant to say. (It would have been a much better "clarification" if I didn't switch between talking about desired and undesired behavior mid-sentence.)
There is a small design choice about whether to allow this view for non-leaf components with zero children (that is, components which could have children, but don't at the moment.) I'd lean toward "allow it" but have no strong opinion. (Note for harleigh, there is an "isLeaf" method on AbstractComponent which would make writing a policy for that fairly trivial.)
I think this view should be allowed on "non-leaf" components having zero children, because the view should not change based on the maybe-trivial fact that a particular component happens to not have children at this moment.
Verified in hackathon 9/25/2013 (Mac OS X & Windows 7)
Verified in Hackathon 9/25/2013 (Linux on otf2)