- You can uninstall Together. Removing Together (by also deleting the
bpl files) will improve the responsiveness of your D2006 IDE, and make
Delphi 2006 startup speed increase.
- ECO State machines can be created for Delphi 2006 Enterprise and
- A fully ECO customised GUI means that you are working with a UML tool
that looks like it was made for ECO. Class derivation expressions, class
default string representation, association embedding, association end delete
- The power of ModelMaker 9. Being based on ModelMaker 9 means that
Eco3Modeler allows you to additionally create Use case diagrams, Robustness
- You also have the refactoring tools, and method-override wizards. You
may even model (non ECO) overloaded methods.
- Full merging is supported from the model into a previously generated
class. Modeled properties / methods which have renamed in the model will be
renamed in your source. You can even add your own implementation properties
/ methods etc within your source file without risk.
- Regions added for auto hiding of ECO specific code, making your source
- Less autogenerated code. Each attribute/association only appears once
in the source, the additional "protected _Attribute1" underscored protected
properties are not generated because they are not needed. Exception:
Attributes with HasUserCode - this is required by ECO.
- Better interface support. Eco3Modeler presents a time saving
Interface Implementation Wizard whenever a class realizes an interface in
the model. The advanced code-merge will also prevent any interface
declarations added in code being lost when when the class's source code is
- Eco3Modeler stores the entire model plus all diagrams in a single
file. No need for a ModelSupport folder full of diagram files.
- Eco3Modeler is customizable. It is possible to add custom editors, or
even additional tabs in existing editors. A comprehensive model API allows
you to write plug-ins capable of manipulating your models in code.
- You can organise your diagrams into folders/subfolders and so on. This
really helps when organising a large model, and it all still gets saved into
a single file.
- The diagram surface in my opinion is much better. It doesn't lose
layouts, it is more responsive, it is more flexible.
- Deleting elements from a diagram does not remove them from the model,
only from the diagram.
- You can emit source code documentation from your model.
- You can automatically implement interfaces just by drawing a realization
line to the interface.
- C# can optionally create source for the interfaces in your model.
- You can set diagram display options at EcoModeler level, override at
project level, diagram level, or diagram element level.
- You can colour your association lines. I find this very useful (green = transient, red =
derived for example.)
- You can create UML 2 diagrams.
- You can drag/dock the various windows in EcoModeler and save / restore
the layouts by name.
- In Together you cannot have 2 associations going to person with the role name "Owner", you would have to name them "AnimalOwner" and "HouseOwner" for example. This is a Together restriction which does not exist in either EcoModeler or ECO itself.
- Unlike Together adding tagged values does not emit [USER_PROPERTY] at the start of the name.
- You can add tagged values to an association end.
- You can visually specify association classes (a special line that connects a class to an existing association line.)
- You can select the platform-independent-mode property types (AutoInc, Blob, Text etc) in EcoDataTypes.XML from a dropdown list in the property dialog, so you don't need to remember what is available.
- Classes on diagrams visually indicate persistent/transient classes. Persistent classes have a small database symbol on them.
- You can add hotlinks to diagram elements. For example, if you added links to 3 different diagrams on a diagram element 3 small icons would appear next to the class name, clicking on them would take you to that diagram.
- EcoModeler has a Back/Next to navigate through recently viewed diagrams.
- EcoModeler has multi-level undo/redo for diagrams. This includes all visible changes to the diagram elements, but does not undo/redo changes to the class itself such as renaming, adding properties etc.
- The documentation editor has a live spell checker built in.
- From a commercial point of view I think it is also good news that being a smaller company means it is much quicker to issue a release if there is a critical bug (which I have never seen in EcoModeler since I first used it for ECO 2).
I hope this is of interest :-)