Expand class tree to show superclasses and subclasses

[KSchopmeyer]

Today we do a ascii class tree either as the subclasses or the superclasses. I have been asked several times to be able to display both the subclasses and superclasses as a single diagram.

The idea would be to merge the subclass tree and the superclass tree and designate the class that represented the intersection.

If there was a named class in the request, from the defined target class the subclasses would be just as they are now. From the target class up, it would be a single tree path to the root

The real questions are:

1. Should this be a new option or simply the default.
2. If we do this are the current options useful
   default - Subclasses from the target class
   -s - superclasses from the target class

The result of a full tree with TargetClass CIM_MemberOfCollection would look like:

class tree CIM_Collection                                            
CIM_Collection
root
 +-- CIM_ManagedElement
     +-- CIM_Collection*
         +-- CIM_SystemSpecificCollection
         |   +-- CIM_MaskingGroup
         |    |   +-- CIM_InitiatorMaskingGroup
         |    |   +-- CIM_TargetMaskingGroup
         |    |   +-- CIM_DeviceMaskingGroup
         |    +-- CIM_ConnectivityCollection
         |    |   +-- CIM_RemoteReplicationCollection
         |    +-- CIM_StorageTier
         |    +-- CIM_RedundancySet
         |    |   +-- CIM_StorageRedundancySet
         |    +-- CIM_OperationalPowerManifestCollection
         |    +-- CIM_StatisticsCollection
         |    +-- CIM_TargetPortGroup
         |    +-- CIM_ReplicationGroup
         |    +-- CIM_BlockStatisticsManifestCollection
         |    +-- CIM_LogicalPortGroup
         |    +-- CIM_StorageResourceLoadGroup
         |    +-- CIM_FailoverStorageExtentsCollection
         |    +-- CIM_AllocatedResources
         |    +-- CIM_RemoteResources
         |    +-- CIM_DeviceSet
         +-- CIM_FilterCollection
             +-- CIM_CollectionOfMSEs

[KSchopmeyer]

The open questions for this one are:

1. Worthwhile doing??? I think so since it is low development cost.
2. Changes to options to allow selecting subclasses, superclasses, all
3. If we show all should we somehow mark the class that was the target at least when showing all.

[KSchopmeyer]

I would like to move this to version 1.1