Hi Gregor,
in my experience, it is not a good idea to mix graphical notations
for control- and data-flow. Most visual languages try to avoid this
and focus on only one part in the graphical notation. Moreover, in
order to be concise with the textual representation of parameters
that already exists for rules in the graphical editor, I believe it
makes more sense to use text to indicate the parameter passing.
Cheers,
Christian
Am
10.01.2012 00:29, schrieb Gregor Bonifer:
The basic idea is, that the ParameterMappings inside a unit
form a net structure, whereas the structure of the subUnits is
a trivial list. To allow free arrangement of a flat list
structure requires more graphical elements than actual model
elements. In a way this corrupts the premiss one wishes to
have, when it comes to visualizing the ParameterMappings. To
avoid ending up with a cluttered mashup of two graph-like
structures, I vertically aligned the subUnits. On the one hand
this clarifies how the subUnits relate to each other. On the
other hand this defines a horizontally aligned area for each
unit which allows free arranging of its parameters. I think
the result is relatively clear and concise.
|
