Modlr plugins

This article was moved to MDriven Wiki Modlr plugin

We added a plugin interface for Gaffr and ECO. We want to enable you to extend Modlr so that you can implement a special file format import, or export, or what have you.

This is how it works:

Given these two interfaces…

Code Snippet
  1. namespace Modlr.Plugins
  2. {
  3.   Public Interface IModlrPlugin
  4.     {
  5.         string GetName();
  6.         List<IModlrPluginMenuOperation> ProvideOperations();
  7.     }
  8.   Public Interface IModlrPluginMenuOperation
  9.     {
  10.         string GetName();
  11.         void CheckEnableOrExecute(IEcoServiceProvider esp, bool execute,
  12.     }
  13. }

…you can implement a plugin in an assembly like this:

Code Snippet
  1. public class Class1 : IModlrPlugin
  2. {
  3.     #region IModlrPlugin Members
  4.     public string GetName()
  5.     {
  6.         return “Demo plugin”;
  7.     }
  8.     public List<IModlrPluginMenuOperation> ProvideOperations()
  9.     {
  10.         List<IModlrPluginMenuOperation> ops = new List<IModlrPluginMenuOperation>();
  11.         ops.Add(new OperationShowDialog());
  12.         ops.Add(new OperationActOnClass());
  13.         return ops;
  14.     }
  15.     #endregion
  16. }

The code above installs two Operations; OperationShowDialog and OperationActOnClass.

Looking closer on the operation ActOnClass:

Code Snippet
  1. public class OperationActOnClass : IModlrPluginMenuOperation
  2. {
  3.     #region IModlrPluginMenuAction Members
  4.     public void CheckEnableOrExecute(IEcoServiceProvider esp,
  5.     {
  6.         enabled = false;
  7.         if (maincontext != null && maincontext.AsIObject().AsObject is Eco.ModelLayer.Class)
  8.         {
  9.             enabled = true;
  10.             if (execute)
  11.             {
  12.                 (maincontext.AsIObject().AsObject as Eco.ModelLayer.Class).Name += “X”;
  13.             }
  14.         }
  15.     }
  16.     public string GetName()
  17.     {
  18.         return “Operation on class“;
  19.     }
  20.     #endregion
  21. }

The code checks that the context is a class, and if it is the code says that the operation should be enabled. If this was an “execute” call we perform the desired logic – in this case I just add an “X” to the back of the class name.

You can do a lot of stuff in a plugin. You get access to the IEcoServerProvider for the EcoModelLayer. The Modlr application is a standard ECO-built-application so you can use the IOCLService to get to any object, of any class that builds up your model content. You can access Diagrams, PlacedClasses, StateMachines etc. You can inspect and set TaggedValues, you can run thru every Attribute and check for spelling errors. You can create reports that you share with other ECO/Gaffr users…

So even if the interface is very small and simple, it is very powerful.

When you build your Plugin you will want to reference the following assemblies (found in the eco or gaffr install directory):


Compile your plugin and put the assembly in the folder %ProgramData%/CapableObjects/Plugins

Restart or VisualStudio and you will find your plugin operations in the context menu:


Simple and powerful.

This entry was posted in Plugin. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.