[news.eclipse.tools.emf] Re: extending eType(s)

[Ralf Buschermoehle <buschermoehle@xxxxxxxx>]

Hi Ed,

Ed Merks wrote:

> > How do I get the sources for a specific emf build, e.g., 2.5.0 
> > (2009/06/16), that I use into my package explorer as java project to 
> > modify the sources and (re-)build the complete (&modified) emf package?
> We set up source using these instructions:
>
>     http://wiki.eclipse.org/EMF/Getting_Source
>
> I've not done any 2.5 maintenance work yet so I'm not sure if we created 
> a 2.5 branch yet...

Ok. Does the tagged build 200906151043 of the CVS correspond to the 
Latest Release 2.5 (from 2009/06/15) (or e.g., already to 2.6)?

> But I'm not sure why you're asking this in response to my suggestion?  
> Normally source is available when you install the SDK and I'm not 
> suggesting you modify it.  I'm suggesting you create your own package 
> with your own data types.

Sorry for the confusion, I would like to have some additional data types 
directly on the ecore level (now called level 0). I thought you were 
refering to this level as well when you pointed to EcorePackage and 
XMLTypePackage in the EMF sources.

We build new ecore or merge existing ecores on level 0 dynamically on 
base of existing models (level 1) - yes, it's a strange concept - 
nevertheless it works fine ... so far ... ;)

As far as I understood (now) ... you refered to add a new ecore 
package/edata type on level 1, generate the sources and extend/bind them 
to the API's covering the types (e.g. converters)? The problem then 
would be the dynamic generation of level 0 models - thus we don't have 
source code to extend - maybe one could use reflections at this point, 
but I think the extension of the emf sources would be simpler?

Greetings,

	Ralf


P.S. Another possibility would be to introduce jscience data types in 
EMF (http://www.jscience.org/) or other libraries dealing e.g., with 
rationals? But I assume this is more a license related question.