| [news.eclipse.technology.ldt] Re: Beyond textual represenations... |
|
Guillaume, We'd be ever so grateful to increase the sales of the EMF book: Eclipse Modeling Framework Eclipse Modeling Framework Sample ChapterI personally don't like that word meta-model much, but we did use it in the overview paper: However, to avoid any confusion, the MOF-like core meta model in EMF is called Ecore.I find the term is kind of confusing and I tend to think that a model is a model is a model. I'm pretty sure that focusing on the Ecore meta-model in the overview paper would just turn most people right off because most of our clients care only about their own models not about Ecore (until sometime later). But Ecore is indeed a UML-like model, and UML itself is a meta-model, right? EMF does support strong Java binding for Ecore instances but that is in addition to being able to emulate the all model instance behavior dynamically without generating any Java code; this is because the full EObject API can be supported either reflectively or with generated code. I'm rather fond of the model diagrams in the JavaDoc. Almost everything you need to know about the Ecore API is available directly from the second diagram: API Guillaume Pothier wrote: Ed Merks wrote: |