I just wanted to let you know that EMFT has new component: JS4EMF -
Javascript for EMF! The objective of this component is to integrate
Javascript with every part of EMF where it is useful.

One use case is similar to what the OCL component is used for: define
the behavior of models, by means of constraints/invariants, derived
features and operations. Another use case is using Javascript as a
scripting language in your own application, e.g. implement edit commands
that navigate in and update you EMF model.

Both these use cases are currently supported. In addition there is UI
support for editing the scripts that are stored in annotations, and for
invoking operations on EObjects in the EMF-based editors.

The initial code is currently part of e4 (I think it's only used by TM),
but it will require some refactoring (plugin and package naming) and
some API cleanup. We will likely be merging in code from EMFScript, too.

We have not decided how to transition from e4 to js4emf, yet. One
possibility is moving the code first, and then clean it up while keeping
e4 updated. The second option is to clean it up first, use the cleaned
up code as the initial code, and later re-integrate it into e4. If there
are other options, or good reasons for choosing one over the other, we'd
like to hear about it.