Eclipse Community Forums: Graphiti » Parent/Child hierarchy for shapes and GraphicsAlgorithm

Home » Modeling » Graphiti » Parent/Child hierarchy for shapes and GraphicsAlgorithm(Do I always need to create a shape for each child of a GraphicsAlgorithm ?)

Parent/Child hierarchy for shapes and GraphicsAlgorithm [message #1202727]

Fri, 22 November 2013 04:33

Eclipse User

Hi,

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 10:49] by Moderator

Re: Parent/Child hierarchy for shapes and GraphicsAlgorithm [message #1208848 is a reply to message #1202727]

Mon, 25 November 2013 02:54

Eclipse User

Hi,

I think the answer to your question is yes. Shapes are created when you
want to link to a model element, whereas GraphicsAlgorithms provide the
visualization of the shape it's within and can be arbitrary complex and
nested.

Hallvard

On 22.11.13 10:33, Antoine Lorence wrote:
> Hi,
>
> 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 children 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 entire diagram hierarchy ?

Previous Topic:	Create palette icons
Next Topic:	Multiple textfields in AddFeature

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 05:08:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter