Bug 88844

This is obvious need feature. 

Use Cases:

Space consolidation case - User wishes to make large diagram more manageable
within Design view. 

Noise reduction case - USer wishes to reduce noise in diagram by reducing number
of visible elements.

Both cases can be improved by  allowing user to collapse and expand each
container view (including PartnerLinks). 

Basic feature desription:
Each "expandend" container should have an action to collapse the container.
Each "collapsed" container should have an action to expand the container
The exception to this is the Process view. Does anyone see any value to a
collapse action on the entire process?

Some open issues:

What should happen to Element Toolbar actions when element is in collapsed state? 
Example: If element is collapsed. Currently, If toolbar contains an "Add Else"
action. Similar cases exist for most container. 
Should this action be enabled or disabled when containe is collapsed?
If we decide to enable it. What should be result of activation? Should element
auto-expand?


What should be relationship of collapsed diagram view and Navigator?
Should navigator view be completely non-responsive to diagram and diagram
non-responsive to Navigator expand collapse actions?

Under what conditions if any should a currently "collapsed" container be
auto-expanded? 

What should be response of collapsed elementto DnD of element from palette?
Should it be non-repsonsive?

What should be response of collapsed element to Debug Step? What if there is
breakpoint set in collapsed element?

What if user goes to source view and selects a section of source that is deep in
the collapsed element, and then switches back to Diagram view - see other new
feature request to keep Source and Diagram views in mutual selection
synchronization.