vainolo/object-process-programming

Eclipse plug-in to create, edit, and execute Object-Process Progaming models

object-process-programming's Issues

Add state to model and diagram

Add tooltips to show OPMThing description

Implement validation rules for model

Define when links can be added between model entities:

1. What procedural links are valid.
2. What structural links are valid.

Add "type" attibute to objects

1. Not mandatory (complex object can are defined by the model an not by their types).
2. The name of the attribute is added to the name of the object "<object_name>:<type_name>"
3. Currently available types: Number, String
4. Types are currently added using a string.

Add Structural Link

Automatic Resize of Primitive Nodes

The size of a node should be calculated based on the size of its text.
There is an action that already does this, we must call it after the text of a node is edited.

Add invocation link

Add Special Decorators for Event and Condition Links

Added new decorators to event and conditional links. They may not look nice but show the idea how this should be done.

Function to find the next processes that can be executed

Implement the function in OPDAnalyzer, using the OPDDAG

Add possiblity to create internal nodes

OPM lets user create nodes inside other nodes (objects inside objects, processes inside processes).

Add grid functionality

• Added new actions to the graphical editor and to the action bar/tool bar.
• Implemented edit policies in OPD and Thing and adapters for snapping.

Let the user create more bendpoints for structural links

Currently structural links are connected to and from elements using Manhattan routers. A better way to connect them would be to create special bendpoint routers which allow the user to create new perpendicular benpoints like this:

---

thing1

  -------
          |
         / \
         ---
          |            ---------
          ----------| thing2 |
                        ---------

Solution can probably be implemented using a limited bendpoint connection router

Resize to contents does not take into account states

Maybe also doesn't take into account inner figures.

Refactor code and model to remove duplication

Specifically created because the implementation of OPMState created duplications.

Add structural link to editor

Structural links are added using an aggregator.

1. the first structural link of each kind that is added to a thing creates a new aggregator.
2. when the source thing is deleted all aggregators that are connected to it must be deleted.
3. when the aggregator is deleted all links are deleted.
4. links use manhattan router.
5. when a new structural link is added we have to check if there is already an aggregator of its kind and use it.

Fix Strucutral Links for Internal Nodes

Structural links created between things that are contained in other things are not located correctly. Create two things inside a thing and connect them with a structural thing to see this happen.

Do not show description tooltip if there is no thing description

Implement OPM Event and Condition Link in Diagram

Partially implemented already. What was done:

1. changed the model
2. added new links to the diagram using special decorators, but they look ugly. So will re-implement using the endpoint decorator of the link.

Status update 30/5/2012:

• Added new link types to the editor, but the new implementation of the decorators is still lacking. Added task to implement new decorators for these links
• During the implementation I too the time to create icons in the palette for all editor operations. Looks nicer.
• Changed the default font of the diagram to match (my) java code font. Added new task so that the font is loaded from the current workbench definition.

Implement direct editing for state and label

direct editing is currenly implemented only for things. Must also be implemented for states and labels. Should only be implemented once...

Add procedural links to the model

• Add a new class OPMProceduralLink that exends OPMLink and contains an OPMProceduralLinkKind
• OPMProceduralLinkKind can be AGENT, INSTRUMENT, CONS_RES (Consumption/Result) and EFFECT

user can add structural links starting at structural aggregators

Divide tools in the palette into different groups

Three groups:

1. selections (implement like in logic diagram)
2. things - objects, processes, links
3. procedural links
4. structural links
5. miscellaneous: lable and such

[Canceled] Automatically resize a diagram entity when its label is changed

resize so that all of the label's text is inside the entity.

Add helper function to OPMObjectProcessDiagram to retrieve all objects and processes

Create static class to analyze OPDs for execution of interpreter

1. find which processes should be executed when the OPD is executed.
2. given that a process has ended, find all processes that should be started.

Add structural link to model

Add structural link to model.
A structural link is defined using three classes: source link, structural aggregator and target link.
Source link connects one thing to the aggregator
Aggregator defines the structural link's kind.
Target link(s) connect the aggregator to at least one thing (but can be connected to many).

Interconectivity with Java

Processes can be build-in java functions of two kinds:

1. static functions: no need of a special "this" reference
2. object functions: need to add reference to "this"
   the "new" operator is a static function.

Load workbench java font as the default font of the editor

In the current implementation the font is hard-coded. This needs to be changed to dynamic loading of the font from the defaults of the workbench.

Resize to contents must not be applied to structural link aggregators

Structural link aggregators should not change size when a resize to content action is applied on them.
Furthermore, the action should no be enabled if they are selected.

Add decorators to links

1. decorator to structural links for number of possible instances: min,max
2. decorator for procedural links: argument name

Change title of editor tab to match name of edited file

Creation of OPD DAG for execution

The execution of an OPD is defined by a DAG (direct acyclic graph) defined by the upper and lower point of the locations.
Process P1 executes before P2 if the lowest point of P1 is located above the upper point of P2.
If process P1 executes before P2 and P2 executes before P3 then P3 will only depend on P2 and not on P1.
This task should create this DAG with the minimum required links needed to fully define the execution order of an OPD.

Special decorators for event and condition links

event links:

1. instrument event:
   e
   -----------O(

2. consumption event
   e
   ----------->(

3. instrument condition
   c
   -----------O(

4. consumption condition
   c
   ----------->(

Implement zoom capabilities for editor

Create initial Interpreter

The interpreter should be able to:

1. Read input from the user using a dialog box containing a single field where the user can insert numbers and strings.
2. Basic add, delete and input from user operations.
3. Handling of instrument, information-transfer links.
4. single diagram execution.
   The interpreter will not handle at this stage:
5. Structural Links.
6. Multi-diagram execution.

Create action on link to delete all existing bendpoints

Implement "Select All" action in editor

Add Colors to Model

Object - Green
Process - Blue
State - Grey

Add procedural links to editor

• Each procedural link is created with a different tool.
• The factory used by the tool is the place where the kind of the link is set.
• A procedural link acts just like a regular link therefore the existing functionality should work, must check code that uses OPMLink to verify this

Generalize the OPMThing functionality to be used for OPMNode instances.

Currently there is a OPMNodeEditPart and OPMNode but much functionality that should be implemented for nodes is currrently implemented only for OPMThing and OPMThingEditPart. Search where this happens and update the code.

Structural link connections must use ManhattanRouter instead of the default router

Currently the incoming and outgoing links of a structural link are created as simple OPMLink instances that use default router. Must find elegant way for them to use a manhattanrouter

Fix Thing Delete Action/Policy so that removal is done recursively.

When a container thing is deleted, the internal thing are deleted but not the links that start/end at the internal things. Furthermore, they are probably also referenced by this links and may cause persistency problems.

Enable Save Action

Be able to save the model after it has been changed.
The action should be active when there have been changes to the model. The action should be inactive if after the last save no changes have been done to the editor.

Change return value of OPMNode getProceduralLinks and OPMNode getStructuralLinks

Methods should return the specific type of link, since this is what they do.

Add key handler for F2 key to execute direct edit when selected element is a named edit part

Add properties sheet to the diagram

Enable viewing and setting element properties in the eclipse properties sheet.

Implement generic label for adding anywhere in the model

Implement a label that can be added anywhere in the model, for better visibility and documentation

Intrepreter for OPM defined processes

Create OPMNodeEditPart

Some of the functionality of the OPMThingEditPart can be transfered to a newly created OPMNodeEditPart so that it can be used also with the future OPMStructuralLinkAggregatorEditPart.
This shoud be done with refactoring!

Add auto resize popup menu on things