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

Help

Home

Home » Modeling » M2T (model-to-text transformation) » [Acceleo] Progress Reporting

Show: Today's Messages :: Show Polls :: Message Navigator

[Acceleo] Progress Reporting [message #695813]

Tue, 12 July 2011 15:17

stuart mackey

Messages: 7
Registered: July 2009

Junior Member

Acceleo doesn't seem to do anything with the Monitor instance passed into it other than check for cancellation while visiting nodes of the template file model.

Is that intentional or a not-yet-implemented feature?

As a workaround currently I add an IAcceleoTextGenerationListener and update my progress monitor for each fileGenerated event.

That's a rather course level of progress reporting though. The template engine could provide more fine-grained progress as it proceeds through the template.

Report message to a moderator

Re: [Acceleo] Progress Reporting [message #696086 is a reply to message #695813]

Wed, 13 July 2011 08:38

Stephane Begaudeau

Messages: 458
Registered: April 2010
Location: Nantes (France)

Senior Member

Hi Stuart,

Which version of Acceleo are you using? If you have Acceleo 3.0, do you reproduce this issue with Acceleo 3.1?
You can grab Acceleo 3.1, here: http://download.eclipse.org/modeling/m2t/acceleo/updates/releases/3.1

Regards,

Stephane Begaudeau, Obeo

--
Twitter: @sbegaudeau
Blog: http://stephanebegaudeau.tumblr.com
Acceleo Documentation: http://docs.obeonetwork.com/acceleo

Report message to a moderator

Re: [Acceleo] Progress Reporting [message #758739 is a reply to message #695813]

Thu, 24 November 2011 12:51

Thomas Buchmann

Messages: 53
Registered: November 2010

Member

I'm encountering the same problem with IndigoSR1 and Acceleo 3.2.0. I tried to use a ProgressMonitorDialog to pass some feedback about the current progress to the user. However, the code is being generated, but no ProgressMonitorDialog is shown to the user.

ProgressMonitorDialog dlg = new ProgressMonitorDialog(PlatformUI.getWorkbench().getActiveWorkbenchWindow().getShell());
dlg.create();
dlg.setOpenOnRun(true);			
generator.doGenerate(BasicMonitor.toMonitor(dlg.getProgressMonitor()));

Report message to a moderator

Re: [Acceleo] Progress Reporting [message #760081 is a reply to message #758739]

Thu, 01 December 2011 09:00

Laurent Goubet

Messages: 1902
Registered: July 2009

Senior Member

Hi,

How exactly are you launching the generation? You don't usually create your own progress monitor, but reuse one that you are fed. For example in this case I'd use something of the sort :

IRunnableWithProgress runnable = new IRunnableWithProgress() {
    public void run(IProgressMonitor monitor) throws InvocationTargetException, InterruptedException {
        ...
        generator.doGenerate(BasicMonitor.toMonitor(monitor));
    }
};
PlatformUI.getWorkbench().getProgressService().busyCursorWhile(runnable);

Laurent Goubet
Obeo

Report message to a moderator

Re: [Acceleo] Progress Reporting [message #760268 is a reply to message #695813]

Thu, 01 December 2011 17:43

stuart mackey

Messages: 7
Registered: July 2009

Junior Member

My code does pretty much exactly what your sample code shows Laurent.

SubProgressMonitor codegenMonitor = new SubProgressMonitor(monitor, 70);
final Monitor acceleoMonitor = BasicMonitor.toMonitor(codegenMonitor);
acceleoMonitor.beginTask("Generating code...", countFilesToBeGenerated(...));
			
Generate generator = new Generate(someArgument, targetFolder , Collections.emptyList());
			
generator.addGenerationListener(new AcceleoGenerationAdapter() {
	public void fileGenerated(AcceleoTextGenerationEvent event) {
		acceleoMonitor.worked(1);
	}
});

generator.generate(acceleoMonitor);

Here you see my workaround for progress - since Acceleo doesn't seem to update the progress monitor I added a GenerationListener and update the monitor myself for each file I see generated.

Report message to a moderator