|Parent/Child hierarchy for shapes and GraphicsAlgorithm [message #1202727]
||Fri, 22 November 2013 09:33
| Antoine Lorence
Registered: September 2013
I am writing a graph editor for a dataflow application. I follow Graphiti online help and create for each object on my diagram a top level ContainerShape containing other ContainerShapes or Shapes. Each one has its own corresponding GraphicsAlgorithm and it works but the resulting model is pretty complicated.
I saw that IGaCreateService.createXXX methods asks for a GraphicsAlgorithmContainer as parameter. So a new GraphicsAlgorithm can be created as child of a PictogramElement OR a GraphicsAlgorithm.
My question is : Is it interesting to create Shapes/ContainerShapes only when it is necessary and create complex graphical objects by appending GraphicsAlgorithm to other GraphicsAlgorithm (when it is possible) ?
Is it a mistake, a very bad thing or could it be a nice choice to simplify the diagram hierarchy ?
[Updated on: Fri, 22 November 2013 15:49]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01626 seconds