Hi Adolfo
On 04/01/2013 08:15, Ed Willink wrote:
I have very preliminary org.eclipse.qvto.pivot.imperativeocl and
org.eclipse.qvto.xtext.imperativeocl plugins that I could commit,
but I guess they must be ".examples" since their first release
will be an experimental adjunct to a non-incubation project (only
QVTd can skip the ".examples'" phase). I'll do a quick rename and
commit them. I don't think we need a QVTo Tools build. There will
clearly be nothing ready for release with Kepler; for Kepler+1, I
hope we can just ship both together, and maybe in Kepler+2 drop
the ".examples".
I've done a quick rename and pushed
org.eclipse.qvto.examples.pivot.imperativeocl and
org.eclipse.qvto.examples.xtext.imperativeocl to master. In so far
as your new work is 100% in examples/... it can be pushed to master
quite regularly; no need for an asbh/397429 branch that doesn't get
merged till 2015. [I'm inclined to switch to asbh/... and edw/...
rather than bug/... as an aid to understanding what is happening
with branches.]
I've created https://bugs.eclipse.org/bugs/show_bug.cgi?id=397429 as
a catchall for the bread and butter part of your EngD. You can
create one more (or many more) for the innovative part; check with
Dimitris in case you need to preserve some temporary secrecy on your
innovations.
org.eclipse.qvto.examples.pivot.imperativeocl is plausible. It
GenModels ok, but there is no copyright/dynamicTemplate to define
the Willink Transformations + York copyright. The autogenerated code
has no accept() method in each Impl class. The underlying EMF
limitation has now been fixed so
org.eclipse.ocl.examples.build.utilities.VisitableAcceptGenerator
might now work if it was uncommented in
org.eclipse.ocl.examples.build/GeneratePivotModel.mwe2. This might
be a useful introduction to MWE2 and the
org.eclipse.ocl.examples.build.GenerateXtextModels approach. You
need something rather similar to
org.eclipse.qvtd.build.mwe2/GenerateQVTModels.mwe2.
NB. org.eclipse.ocl.examples.build/GenerateAll.mwe2 should work but
it doesn't; there is a 'trivial' interaction to sort out in the
various scripts startups.
org.eclipse.qvto.examples.xtext.imperativeocl is very much a work in
progress; you can see commented out LPG remnants in the Xtext files
where they have yet to be converted. The committed files are not
error-free. The CST seems to be set to autogenerate; odd; it
shouldn't be, maybe back in June, I was having a bad Xtext day and
switched to automated just to try and get something working. My
vague recollection is that I started on a translation of the Eclipse
QVTo LPG grammar to Xtext, since it was a working grammar, got
depressed by its divergence from the OMG QVTo grammar and so
switched to a translation of the OMG QVTo grammar to Xtext and
realized that ImperativeOCL.xtext needed to be done first to
modularize the grammars; then it was time for bed. Once we have a
runnable Xtext QVTo editor, we need to go back to the old Eclipse
QVTo grammar to discover any extra syntaxes or corrected syntaxes.
Regards
Ed
|