[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [omelet-dev] documentaion
|
- From: "Ed Willink" <ed@xxxxxxxxxxxxx>
- Date: Sat, 15 Jan 2005 08:53:22 -0000
- Delivered-to: omelet-dev@eclipse.org
- Importance: Normal
Hi Matteo and others
> I am a new OMELET users,
> I'd like to know how OMELET works and how I can develop some OMELET
> application ( I need to analyze some model and I now their metamodel)
>
> Where can I find some documentation?
> Where can I find some example about OMELET?
> Thanks
Thanks gfor the inquiry. It's appropriate to answer it with a status report.
At the beginning of the year, I put all the code I've been working on
for the last few months back in CVS as OMELET 0.1.0, but have yet to
upgrade the major documentation, and so have not released it as an
installable feature.
There is now some support for EMF, which provides e.g. some XSD/Rose to
XMI transformations. There is a disciplined threading policy allowing
multiple transformations to operate in concurrent threads. There is
now a distinction between a transformation (that changes the meta-model)
and a conversion (that doesn't); e.g. UML to Ecore is a transformation
while File to Stream to XMIResource is a conversion. A model can therefore
have many representations with conversions between available and a required
representation performed automatically. In order to isolate the framework
requirements from user code, the information for each representation is
provided by a manifestation that is an unconstrained choice of user class.
I started using Java generics to improve the coding reliability, and found
that they gave me a lot of trouble; you just cannot do C++ style traits.
So a fair number of usages got unwound.
Anyway, OMELET 0.1.0 supervises a number of useful transformations, but not
sufficient to allow me to use OMELET for any of my applications. So since
I cannot use OMELET, I cannot really recommend anyone else to.
I hope this will change very soon. I am putting together a conversion and
a transformation from XMI1[UML1] so that tools such as Poseidon that generate
XMI1 can be used to create EMF meta-models, which will enable EMF to create
an editor for an meta-model instance, and ATL (see the GMT project) to
transform to an instance of another meta-model.
With the above gaps filled, I think OMELET will become usable, and I will
then make an effort to update the documentation and produce examples.
For now, the Examples section of the OMELET User's Guide, (fetch 0.1.0 from
CVS, or just /omelet.doc/html/examples.html describes some examples, but does not
yet point to the underlying Java files.
/omelet/src/org/eclipse/omelet/core/representations has a number of example
representations showing how to integrate user-defined manifestation classes.
/omelet/src/org/eclipse/omelet/core/conversions has a few basic conversions.
/omelet.bridges.emf shows how to integrate facilities from EMF. This code can
be significantly improved now that I have read relevant arts of the EMF book.
EMF offers a lot to integrate. /omelet.bridges.nicexsl shows a much simpler
integration.
Regards
Ed Willink