|
IBM Rational Software Modeler Release 6.0 |
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
Anchor | A representation of the model object 'Anchor'. |
Bendpoints | A representation of the model object 'Bendpoints'. |
Bounds | A representation of the model object 'Bounds'. |
CanonicalStyle | A representation of the model object 'Canonical Style'. |
ConnectorStyle | A representation of the model object 'Connector Style'. |
DescriptionStyle | A representation of the model object 'Description Style'. |
Diagram | A representation of the model object 'Diagram'. |
DrawerStyle | A representation of the model object 'Drawer Style'. |
Edge | A representation of the model object 'Edge'. |
FillStyle | A representation of the model object 'Fill Style'. |
FilteringStyle | A representation of the model object 'Filtering Style'. |
FontStyle | A representation of the model object 'Font Style'. |
Guide | A representation of the model object 'Guide'. |
GuideStyle | A representation of the model object 'Guide Style'. |
IdentityAnchor | A representation of the model object 'Identity Anchor'. |
Image | A representation of the model object 'Image'. |
LayoutConstraint | A representation of the model object 'Layout Constraint'. |
LineStyle | A representation of the model object 'Line Style'. |
Location | A representation of the model object 'Location'. |
Node | A representation of the model object 'Node'. |
NotationFactory | The Factory for the model. |
NotationPackage | The Package for the model. |
PageStyle | A representation of the model object 'Page Style'. |
Ratio | A representation of the model object 'Ratio'. |
RelativeBendpoints | A representation of the model object 'Relative Bendpoints'. |
RoutingStyle | A representation of the model object 'Routing Style'. |
ShapeStyle | A representation of the model object 'Shape Style'. |
Size | A representation of the model object 'Size'. |
SortingStyle | A representation of the model object 'Sorting Style'. |
Style | A representation of the model object 'Style'. |
TitleStyle | A representation of the model object 'Title Style'. |
View | A representation of the model object 'View'. |
Class Summary | |
Alignment | A representation of the literals of the enumeration 'Alignment', and utility methods for working with them |
Filtering | A representation of the literals of the enumeration 'Filtering', and utility methods for working with them |
JumpLinkStatus | A representation of the literals of the enumeration 'Jump Link Status', and utility methods for working with them |
JumpLinkType | A representation of the literals of the enumeration 'Jump Link Type', and utility methods for working with them |
NotationPlugin | This is the central singleton for the notation model plugin |
NotationPlugin.Implementation | The actual implementation of the Eclipse Plugin |
Routing | A representation of the literals of the enumeration 'Routing', and utility methods for working with them |
Smoothness | A representation of the literals of the enumeration 'Smoothness', and utility methods for working with them |
Sorting | A representation of the literals of the enumeration 'Sorting', and utility methods for working with them |
SortingDirection | A representation of the literals of the enumeration 'Sorting Direction', and utility methods for working with them |
Notation meta-model primary package.
This package exposes the notation meta-model API which is used to create notation models. These models usually play the model part of a Model-View-Controller (MVC) architecture for diagrams. Notation models reference other business models (eg. UML models) and store information needed for the visualization of these business models in diagrams. One advantage of maintaining two separate models it to allow the business model to be visualized differently with each notation model.
The views are the central abstraction in a notation model. View objects reference a business model and contain other notation objects that together hold all the properties needed to visualize that business model. The reason the view object does not have all the properties itself but rather delegates to other abstractions is to allow for easy extension of properties.
The abstract view class is the super class of all view
elements. It extends off EModelElement, which is in the EMF core package. It
inherits from EmodelElement the ability to be extensible through annotations.
The view class has the following properties:
A node is a view that can composed and laid out in a container view. The node class has the following property:
An edge is a view that represents a connection between two other views. The edge class has the following properties:
A diagram is a view that represents the top level containment of views. The diagram class has the following properties:
A style is an object containing properties that affect the visualization of a view. An instance of a style class is created and stored in the 'styles' collection of a view instance.
The style interface captures the concept of a style.
The fill style is a style to specify the fill properties of a node. The class has the following property:
The line style is a style to be installed on views with lines. The class has the following property:
The font style is a style to be installed on views with text. The class has the following properties:
The routing style is a style to be installed on edges to guide their routing. The class has the following properties:
The description style is a style to be installed on views to give them description texts. The class has the following property:
The drawer style is a style to be installed on nodes that can be collapsed like a drawer. The class has the following property:
The title style is a style to be installed on views that have a title. The class has the following property:
The sorting style is a style to be installed on nodes representing lists to be sorted. The class has the following property:
The filtering style is a style to be installed on nodes representing lists to be filtered. The class has the following property:
The canonical style is a style to be installed on views that need to be synchronized with business model. The class has the following property:
The page style is a style to be installed on multi-page diagrams. The class has the following property:
The guide style is a style to be installed on diagrams that support guides. A 'Guide' is an object with the following properties:
The guide style class has the following property:
Layout constraints are used by layout managers to properly set the location/size/bounds of a node's visuals. Since the layout constraint can be different based on the type of layout manager using it, the composition pattern is used to allow for changing the layout constraint type easily.
The layout constraint interface captures the concept of a layout constraint.
The location constraint specifies the position of a node. The class has the following properties:
The size constraint specifies the extent of a node. The class has the following properties:
The bounds constraint specifies the bounds of a node. The class inherits its properties from the super classes 'Location' and 'Size'.
The ratio constraint specifies the size ratio of a node in its container. This constraint is suitable for layout algorithms where each child gets a ratio of the container. The class has the following properties:
'Bendpoints' is a routing constraint installed on edges to suggest that their routing pass through a specific collection of points.
A type of bendpoints representing a collection of points with relative distances along the x- and y-axis to the source and target views of an edge. The class has the following properties:
An anchor is a routing constraint installed on edges to identify where the source/target views should anchor that edge. This abstract class only captures the concept of an anchor without restricting it by properties.
The identity anchor is an anchor constraint which has a unique string id. The class has the following property:
|
IBM Rational Software Modeler Release 6.0 |
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
Guidelines for using Eclipse APIs.
Copyright (c) IBM Corp. and others 2004. All rights reserved.