melange
melange copied to clipboard
diverse-project
The Melange Language Workbench
A part of my work last week. The openas menu is "working". there is still a problem with the cast of the adapters. The completion is working and I'll improve...
I modified the 3semantics example to test uniqueness of created adapter and I get a NullPointerException: Modified part of FSM.melange ``` xtend transformation execute(FiniteStateMachineUMLMT stateMachine, String input, String outputFile){ val...
Just like EMF uses URI and a registry to identify metamodels, Melange should manage its own registry of languages (incl. their aspects, etc.) meant to be used by other tools.
currently the Emfruntime (ecore+project) is generated on request only via a quickfix (because it take too long to be done on the fly in the xtend) As it is generated...
``` language A { ... } language B inherits A { ... } ``` B inheris the Ecore and aspect definitions of A. If the Ecore/Aspects of A evolve, B...
With a Metamodel with several packages, When aspects are copied, the package name of each Metaclass is changed for the name of the first package of the Metamodel.
If we defined an attribute of type Set in an aspect on a Metaclass, Melange tries to wrapper the Set in a ListAdapter when generating the corresponding adapter. -> compilation...
Currently, a transformation can only be applied on models typed by the interface it specifies.
Melange should provide an API for all the operations on models outside from Melange We should finalize melange resource implementation.
