Code generation with Essential. Back to Basics

One day I had and keep having the feeling that mainstream tools for Code Generation are over-engineered and provides a lack of Separation on Concerns.

This was the motivation for me to build Essential as a MDE tooling for creating and maintain custom code generators. Time has arrived I need to get it back to life, refresh it and adapt to the new needs.

In the meantime, for the people interested in:

3 comments.

  1. Do you think the best way to look at is as a lightweight alternative to EMF?
    If this is the case, is it usable outside Eclipse?
    Would be possible to run this from Gradle for example?

  2. Hi Federico! Sorry for the late reply.

    >Do you think the best way to look at is as a lightweight alternative to EMF?
    Yes it is much lighter than EMF and MS Corona (MS DSL Tools) approaches. It also do not depends on IDEs.

    >If this is the case, is it usable outside Eclipse?
    It is .NET based so yes: it was designed to be used standalone where no Visual Studio or Eclipse is needed.

    >Would be possible to run this from Gradle for example?
    Yes: It provides a command line interface (CLI) called esl.exe that accepts parameters for validating models and code-gen them.

  3. Hi Pedro,

    Nice demo !!

    A few high level questions.

    What has pushed you to work on this tool?

    a) Is it that .NET/MS community is not used MDE tools and you wanted to provide something useful for them in its familiar IDE?

    b) Is it that tools from MDE community (i.e. EMF/Eclipse) are simply not good enough ?

    If it is a). Is there any, at least half-way, useful tool in that community ? If so, what´s wrong with them that you have come up with your own tool?

    If it is b). What do you think it´s wrong with current MDE solutions in Eclipse/EMF. Eclipse itself ?

    —-

    It´s not clear from the presentation that you support the following but, if you wanted to increase the adopters of your tool (from MDE community), I think you need to support XMI import/export.

    —-

    I´m not a .NET user but it seems to me that you can only support a single output model in your model-to-model transformation language.

    Good luck and keep good work going.

    Cheers,
    Adolfo.

Post a comment.