search

soundasleep / iaml

Automatically exported from code.google.com/p/iaml
3 stars 1 forks source link

Merge DecisionCondition and DecisionOperation types #160

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What new or enhanced feature are you proposing?
As far as I can tell, "DecisionCondition" node is the same as
"DecisionOperation" node, except with a different shape - and one is
avaiable in the condition editor, the other in the operation editor.

DecisionCondition should be merged into DecisionOperation, and
DecisionOperation made to look like the DecisionCondition node (with an
orange ellipse border).

What goal would this enhancement help you achieve?
Cleaner metamodel and less confusion.

Original issue reported on code.google.com by soundasleep on 11 Mar 2010 at 11:24

GoogleCodeExporter commented 9 years ago 
moving all unresolved 0.5 issues to 0.6

Original comment by soundasleep on 17 Apr 2010 at 6:58

GoogleCodeExporter commented 9 years ago 
Perhaps also merge into DecisionNode. Currently DecisionNode is simply 
evaluating the
incoming ConditionEdge for "true?"; we could make this the default of the 
DecisionNode

Also, DecisionXXXs should have a builtin (and defined) suite of potential 
operations.
Perhaps this information can be obtained automatically from the codegen 
templates (or
similar).

Original comment by soundasleep on 27 Apr 2010 at 2:08

GoogleCodeExporter commented 9 years ago 
Resolved in r2042.

Original comment by soundasleep on 27 Apr 2010 at 4:20