Text presentation as metaprogram

I think it will be very helpful if text presentation would be simply a kind of metaprogram, generated from model concepts only we are interested in (not all as it's now) to the target language like textLanguage.

Advantages:

- conceptual easy (no need for additional study cases);

- simplier support (if model had changed & we need to update text presentation) because it's possible to view text presentation lacks directly;

- no more need to comply with hardcoded Java reflection naming conventions;

2 comments
Comment actions Permalink

hi,

in my view the text/file generation is not part of a model mapping/transformation.

It is rather separate finalization step which requires certain configuration facilities and dedicated DSL, but talks about target language are not look like very  relevant.

igor.

0
Comment actions Permalink

Hi,

That's right, metaprogramming isn't relevant in this case. Saying "metaprogram" I meant "templates engine". I guess that advantages you can achieve with making text presentation with MPS support instead of hardcoding may be great.

It's good idea to address special DSL for this issue:)

0

Please sign in to leave a comment.