Eclipse Community Forums: M2T (model-to-text transformation)

Home » Modeling » M2T (model-to-text transformation) » Out of Order text generation

Out of Order text generation [message #727433]

Wed, 21 September 2011 05:38

Eclipse User

Hi

Is there any mechanism for non-linear text emission?

For instance when generating Java code, the need for imports may be
detected and accumulated by an ImportManager, but, in a one pass
algorithm, the resulting imports must be emitted before detection.

The Mof2Text spec in 7.3 suggests that the FileBlock can be used as a
stack to change context. Perhaps a similar StringBlock could emulate a
'Program Section' accumulating contributions which are finally pasted
together.

[string body][emitBody()/][/string]
[string prefix][emitPrefix()/][/string]
[file ('useful')][prefix/][body/][/file]

Perhaps some query such as [emitImports(theImports)/] could be marked as
'late' or 'lazy' so that the invocation marks the insert point for the
late evaluation once theImports has been populated.

Regards

Ed Willink

Re: Out of Order text generation [message #727489 is a reply to message #727433]

Wed, 21 September 2011 08:09

Eclipse User

Hi Ed,

we (EEF team) found a solution very similar to what you propose for the
EMF.Edit and EMF.Editor generation using Acceleo.

We do use a let block to generate body and then generates import block
before the body.

We reuse the EMF importManager to manage import calculation.

You can have a look to our templates here :
http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.emf/org.eclipse.emf.eef/plugins/org.eclipse.emf.eef.codegen.ecore/src/org/eclipse/emf/eef/codegen/ecore/edit/ItemProvider.mtl?view=markup&revision=1.7&root=Modeling_Project

Le 21/09/2011 11:38, Ed Willink a écrit :
> Hi
>
> Is there any mechanism for non-linear text emission?
>
> For instance when generating Java code, the need for imports may be
> detected and accumulated by an ImportManager, but, in a one pass
> algorithm, the resulting imports must be emitted before detection.
>
> The Mof2Text spec in 7.3 suggests that the FileBlock can be used as a
> stack to change context. Perhaps a similar StringBlock could emulate a
> 'Program Section' accumulating contributions which are finally pasted
> together.
>
> [string body][emitBody()/][/string]
> [string prefix][emitPrefix()/][/string]
> [file ('useful')][prefix/][body/][/file]
>
> Perhaps some query such as [emitImports(theImports)/] could be marked as
> 'late' or 'lazy' so that the invocation marks the insert point for the
> late evaluation once theImports has been populated.
>
> Regards
>
> Ed Willink
>
>

--
Cheers,

Stéphane Bouchet, OBEO

Re: Out of Order text generation [message #729288 is a reply to message #727489]

Sun, 25 September 2011 14:49

Eclipse User

Hi Stephane

On 21/09/2011 13:09, stephane.bouchet@obeo.fr wrote:
> Hi Ed,
>
> we (EEF team) found a solution very similar to what you propose for
> the EMF.Edit and EMF.Editor generation using Acceleo.
>
> We do use a let block to generate body and then generates import block
> before the body.
That's really cool. Obvious really, and although not what the spec
says, it's what the spec could be clarified to say. What I wanted is
already there.

This just makes a template the same as a query with an implicit String
return, and support for polymorphic matching. Once queries have
polymorphic matching there will be even less difference.

Regards

ed Willink

Re: Out of Order text generation [message #730087 is a reply to message #727433]

Tue, 27 September 2011 11:28

Eclipse User

Hi

I found that there is a really handy PreviewStrategy that exposes the
internal implementation of fileblocks as stringbuffers so that
generate() returns a map of 'filename' to 'filecontent'; just what's
needed for program sections.

Regards

Ed Willink

On 21/09/2011 10:38, Ed Willink wrote:
> Hi
>
> Is there any mechanism for non-linear text emission?
>
> For instance when generating Java code, the need for imports may be
> detected and accumulated by an ImportManager, but, in a one pass
> algorithm, the resulting imports must be emitted before detection.
>
> The Mof2Text spec in 7.3 suggests that the FileBlock can be used as a
> stack to change context. Perhaps a similar StringBlock could emulate a
> 'Program Section' accumulating contributions which are finally pasted
> together.
>
> [string body][emitBody()/][/string]
> [string prefix][emitPrefix()/][/string]
> [file ('useful')][prefix/][body/][/file]
>
> Perhaps some query such as [emitImports(theImports)/] could be marked
> as 'late' or 'lazy' so that the invocation marks the insert point for
> the late evaluation once theImports has been populated.
>
> Regards
>
> Ed Willink
>
>

Previous Topic:	[acceleo 3.1] editor doesn't see inheritance
Next Topic:	Modularizing an Acceleo transformation

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 00:25:58 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter