Current status of QVTd? [message #1006608] |
Fri, 01 February 2013 02:16  |
Eclipse User |
|
|
|
Hello QVT-Declarative experts,
I am curious about the current status and future plan of QVT-Declarative.
I tried the following.
- Installed eclipse modeling (Juno) package
- Installed QVT Declarative 0.9.0 using All-In-One Update site [also tried other versions but did not work]
- Installed OCL package using "Install Modeling Components" (to utilize ModelRegistry Model Editor)
- Introduced ModelMorf distribution Examples into the workspace
I see introduced *.qvtr files have lots of red flags. It seems most of them are due to the fact that they are unable to recognize metamodels (.emof files -- even modified as ecore files). I am curious to learn if there is any way to fix this. If not, is there any plan?
It seems QVT Declarative is not usable at this moment (if above is not fixable). Or, is there any configurations or previous package etc. we can use for the time being? Also, with the installation of QVT Declarative, it provides (from File -> New menu) creating empty QVTc project capability. Is QVTc actually implemented in the same distribution?
Thank you for clarification in advance.
Akira
|
|
|
Re: Current status of QVTd? [message #1006613 is a reply to message #1006608] |
Fri, 01 February 2013 02:39   |
Eclipse User |
|
|
|
Hi
The QVTc and QVTr editors should be usefully functional. The 0.10
editors from the download pages may be slightly better.
The ModelMorf examples had only a couple of errors with the 0.8
IMP-based editors. I must confess that I haven't checked them properly
with the newer Xtext-based editors. I suspect that they just need import
declarations. In 0.8, a Model Registry was required to specify the
meta-model name to location mapping. I eventually decided that this was
a language bug and introduced import, include and library declarations.
Look at the Rel2Core which is what I use mostly for exercising.
My company, Willink Transformations, is sponsoring an EngD student at
York to pursue the progressive transformation approach outlined in
http://wiki.eclipse.org/MMT/QVT_Declarative_Languages. Currently some
very simple QVTi transformations are working. This gives confidence that
the approach is good. The execution work is all Open Source and
currently on GitHub at git://github.com/arcanefoam/qvtMustus. It will
move to Eclipse in a few months.
The goal is basic QVTc execution for Kepler, basic QVTr execution for
Kepler+1, optimized execution for Kepler+2.
The code is all layered on top of the new Xtext-based, UML-aligned pivot
OCL binding, so the new direct OCL to Java code generator can be
exploited to give high quality compiled transformation code.
Regards
Ed Willink
On 01/02/2013 07:16, Akira Tanaka wrote:
> Hello QVT-Declarative experts,
>
> I am curious about the current status and future plan of QVT-Declarative.
> I tried the following.
>
> - Installed eclipse modeling (Juno) package
> - Installed QVT Declarative 0.9.0 using All-In-One Update site [also
> tried other versions but did not work]
> - Installed OCL package using "Install Modeling Components" (to
> utilize ModelRegistry Model Editor)
> - Introduced ModelMorf distribution Examples into the workspace
>
> I see introduced *.qvtr files have lots of red flags. It seems most of
> them are due to the fact that they are unable to recognize metamodels
> (.emof files -- even modified as ecore files). I am curious to learn
> if there is any way to fix this. If not, is there any plan?
>
> It seems QVT Declarative is not usable at this moment (if above is not
> fixable). Or, is there any configurations or previous package etc. we
> can use for the time being? Also, with the installation of QVT
> Declarative, it provides (from File -> New menu) creating empty QVTc
> project capability. Is QVTc actually implemented in the same
> distribution?
>
> Thank you for clarification in advance.
>
> Akira
|
|
|
|
|
|
|
|
|
|
Re: Current status of QVTd? [message #1069160 is a reply to message #1069135] |
Mon, 15 July 2013 05:43  |
Eclipse User |
|
|
|
Hi
There is an interpreted and a code generated execution capability for
QVTi inherited from OCL. (Probably the first M2M project with Java code
generation at Eclipse).
However QVTi is just a simple imperative semantics. Just like assembler,
very useful to have, but you wouldn't want to use it manually.
We hope to get M2M transformation chain from QVTr to QVTc to QVTu to
QVTm to QVTi in place for Luna
See wiki.eclipse.org/MMT/QVT_Declarative_Languages,
http://www.slideshare.net/EdWillink/icmt2013-talk,
http://link.springer.com/chapter/10.1007%2F978-3-642-38883-5_8
We also hope to have a debugger for Luna.
Advanced optimisations for QVTr are targetted for Luna+1 and Luna+2.
So we now have editors/parsers and low level execution. Just need to
transform across the abstraction gap from QVTr/c to QVTi.
Regards
Ed Willink
On 15/07/2013 09:21, Goood Guy wrote:
> Hi,
>
> just recently I became really aware of the QVTd project, which is very
> exciting. Since 0.10.0 was recently released, I am interessted in an
> update of the project status. Especially if the release already comes
> with an execution implementation and how the execution can be triggered.
>
>
> Simon
|
|
|
Powered by
FUDForum. Page generated in 0.05486 seconds