| Ecore 2 Ecore - Could use some input [message #958045] |
Thu, 25 October 2012 18:06  |
 Daniel Kasmeroglu
Messages: 5
Registered: July 2009
Location: Berlin |
Junior Member |
|
|
Hi there,
I have to write some UI for a predefined ecore which is quite large and cannot be altered by myself. Apart from that this ecore provides several really inconvenient constructs. F.e.
- From a semantical point of view there is a datatype definition Enumeration, Primitive, Record which will be established by a single model type DataType. The semantical distinction has to be made by several attribute/element values provided with that type.
- Another thing is that there are several types which are basically identical as they provide exactly the same information (same attributes, same references etc.). They are simple redundant so there are type like RValue, LValue, ZValue which are equal but still different types.
From my development perspective I would like to simplify the application code which is somewhat ugly as it's necessary to deal with the abovementioned differences.
So I basically intend to use my own ecore internally which would achieve something like this:
- Instead of the model element DataType I will get distinctive model elements Enumeration, Primitive and Record .
- The redundant types RValue, LValue and ZValue should be mapped into something like this: Value [ type : {R, L, Z} ] .
Looking for such a possibility I found ecore2ecore. Unfortunately I failed to locate thorough tutorials/documentation about it.
So here are my questions:
1. Are my goals achievable using ecore2ecore or did I miss something ?
2. Where can I find detailed infos about it ?
3. Does anyone know about another technology to realize my goals ?
Thanks in advance.
Bye
Kasimir
|
|
|
| Re: Ecore 2 Ecore - Could use some input [message #959254 is a reply to message #958045] |
Fri, 26 October 2012 15:13  |
Ed Merks
Messages: 33141
Registered: July 2009 |
Senior Member |
|
|
Daniel,
Comments below.
On 26/10/2012 3:43 PM, Daniel Kasmeroglu wrote:
> Hi there,
>
> I have to write some UI for a predefined ecore which is quite large
> and cannot be altered by myself. Apart from that this ecore provides
> several really inconvenient constructs. F.e.
>
>
> From a semantical point of view there is a datatype definition
> Enumeration, Primitive, Record which will be established by a single
> model type DataType. The semantical distinction has to be made by
> several attribute/element values provided with that type.
> Another thing is that there are several types which are basically
> identical as they provide exactly the same information (same
> attributes, same references etc.). They are simple redundant so there
> are type like RValue, LValue, ZValue which are equal but still
> different types.
>
>
> From my development perspective I would like to simplify the
> application code which is somewhat ugly as it's necessary to deal with
> the abovementioned differences.
> So I basically intend to use my own ecore internally which would
> achieve something like this:
>
>
> Instead of the model element DataType I will get distinctive model
> elements Enumeration, Primitive and Record .
> The redundant types RValue, LValue and ZValue should be mapped into
> something like this: Value [ type : {R, L, Z} ] .
>
>
> Looking for such a possibility I found ecore2ecore. Unfortunately I
> failed to locate thorough tutorials/documentation about it.
> So here are my questions:
>
> 1. Are my goals achievable using ecore2ecore or did I miss something ?
No. It's purely a data structure representing a mapping. It doesn't do
anything useful other than to represent the mapping.
> 2. Where can I find detailed infos about it ?
There really aren't any.
> 3. Does anyone know about another technology to realize my goals ?
It sounds more like you want to do a model-to-model transformation.
>
> Thanks in advance.
>
> Bye
> Kasimir
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Powered by
FUDForum. Page generated in 0.03461 seconds
] 
Search
Help
Register
Login
Home
