[PAPoint] Connectionpoint for physical paths (developer guide)

collapse
  • Scope /
  • [PAPoint] Connectionpoint for physical paths (developer guide)
Overview

Classname/ID Comment
ID 5e495bde-72aa-463c-984c-817ba72d2a0b
ACIdentifier PAPoint
ACUrlComponent Database\ACProject(Variolibrary)\ACClass(PAPoint)
Is abstract
Is abstract
Namespace gip.core.autocomponent.PAPoint
ACUrlComponent Connectionpoint for physical paths
Comment Connectionpoint that represent physical relationships between components. The physical relationships are configured in the development enviroment and stored in the database-table ACClassPropertyRelation. The ACPostInit()-Method reads ACClassPropertyRelation (where ConnectionTypeIndex == Global.ConnectionTypes.ConnectionPhysical) and creates instances of PAEdge for each relation. PAEdges are stored in the ConnectionList. One PAEdge-Instance exists always in two different Connectionlists. One in a PAPoint, that represents a source and one in another PAPoint, that represents a target. This two-way connection allows you to define a network of physical paths in which you can search for or navigate targets in both directions. This pathfinding algorithms are implemented in the class ACRoutingService which uses this kind of Connectionpoints.

Hierarchy Table

Classname/ID Comment
PAPoint Connectionpoint that represent physical relationships between components. The physical relationships are configured in the development enviroment and stored in the database-table ACClassPropertyRelation. The ACPostInit()-Method reads ACClassPropertyRelation (where ConnectionTypeIndex == Global.ConnectionTypes.ConnectionPhysical) and creates instances of PAEdge for each relation. PAEdges are stored in the ConnectionList. One PAEdge-Instance exists always in two different Connectionlists. One in a PAPoint, that represents a source and one in another PAPoint, that represents a target. This two-way connection allows you to define a network of physical paths in which you can search for or navigate targets in both directions. This pathfinding algorithms are implemented in the class ACRoutingService which uses this kind of Connectionpoints.
ACPointBase
IACObject Base interface for classes that are registered (or known) in the iPlus-Type-System. They appear in the iPlus-Development-Environment in the Variolibrary-Project or Variobatch-Project. Instances of IACObject have a unique address (ACUrl) in Application-Trees and can be accessed by ACUrlCommand. Therefore every implmentation of IACObject should implement ACUrlCommand to be accessible. IACObject's also can have Designs to be able to be presented on the GUI.
IACObjectBase This is the ultimate base interface for implementing classes in the iPlus-Framework. It's comparable to the .net-Type System.Object. This interface helps to present objects on a GUI with its description and to indentify them inside a generic list through its uniqe indentifer (ACIdentifier)
IACPointBase An IACPointBase is used to abstractly describe the relationships between any object. It is called a Connectonpoint because in graph theory objects are represented as points and relationships as lines. Using this abstract interface, Variobatch is able to graphically represent any relationships between objects (e.g. workflows, visualizations, routes...). The relationships are stored in the IEnumerable<T> ConnectionList property.
IACMember Abstract interface for implementing classes which can be listed in the ACMemberList of a ACComponent. Members can be Properties, Points and other ACComponent-Instances (childs)
INotifyPropertyChanged