IDE object type system

Since the running IDE consists of different extensions from different sources, possibly developed at different points of time, it is necessary that a standard and extensible system is available to exchange selection information between the view extensions which the user interacts with and the command extensions that perform operations for the user.

IDE provides a basic set of object types that cover the commonly used galaxy objects. All the view extensions should publish their selection information using these standard types so that command extensions can use this information to distinguish between the different objects that are in the user’s selection.

The object types provided by IDE are explained below:

• IaaObject – This is the most basic type for any kind of object that can be selected in the IDE. This is an abstract type.

• IaaGalaxyObject – This is the base type for a galaxy object (gObject). This type provides the basic information about the object via the “Id” property. This is used to distinguish between gObjects and folders (template toolsets etc).

• IaaAutomationObject – This is the base type for an automation object. This is used to distinguish between automation objects and visual elements.

• IaaAutomationObjectTemplate – This represents an automation object template.

• IaaAutomationObjectInstance – This represents an automation object instance.

• IaaGalaxyInstance – This represents the top-level galaxy object instance, which contains all other objects in the application.

• IaaFolderObject – This represents a generic container object which could be toolsets, unassigned area/host and library folders. This is an abstract type.

• IaaUnassignedFolder – This represents the unassigned sections of the application views, which is just an UI presentation.

• IaaToolsetObject – This represents a template toolset.

It is is important that when publishing selection using these types, the type that matches the object as closely as possible is used so that the menu items and toolbar states are as accurate as possible. Following is the pictorial presentation of the interface hierarchy.