| Using Different Model & Diagram File [message #175070] |
Mon, 03 March 2008 02:22  |
Eclipse User |
|
|
|
Originally posted by: kamesh.sampath.gmail.com
Hi,
I am trying to follow the example and do the "Integrating EMF and GMF
Generated Editors by by Volker Wegert and Alex Shatalin".
What are the problems that we will be facing when we use seperate file for
model and diagram , how to work around that ?
The reason am asking this is because ideally we will be using the model to
generate the Code , it will be easier to write the templates when the
model has only the EMF objects and no diagram elements.
Also it will the XML parser will consume less time when parsing a small
file instead of the big files (both diagram + model together)
~Kamesh
|
|
|
| Re: Using Different Model & Diagram File [message #175124 is a reply to message #175070] |
Mon, 03 March 2008 07:46  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Kamesh,
If I understand the issues I've seen correctly, when you keep the model
in separate resource, it's obviously far easier for the diagram and the
model to be out of sync since you can change the model and save it
without have touched the diagram. So an important consideration is what
form do the URI references from the diagram to the model take. If they
are based on IDs, you'll generally be in good shape most of the time
since broken references can be discovered quite easily to be repaired
and IDs don't generally change. If you use the default EMF fragment
paths that are used in the absence of IDs, you're more likely to get
intro trouble since such references are based on position and location
in the resource and hence moving, removing, or adding objects can make a
reference refer to a different object than before. EReference.eKeys can
help make such references more robust by making the reference into a
list be based on attribute values of the referenced object.
Kamesh Sampath wrote:
>
> Hi,
>
> I am trying to follow the example and do the "Integrating EMF and GMF
> Generated Editors by by Volker Wegert and Alex Shatalin".
>
> What are the problems that we will be facing when we use seperate file
> for model and diagram , how to work around that ?
>
> The reason am asking this is because ideally we will be using the
> model to generate the Code , it will be easier to write the templates
> when the model has only the EMF objects and no diagram elements.
> Also it will the XML parser will consume less time when parsing a
> small file instead of the big files (both diagram + model together)
>
> ~Kamesh
>
|
|
|
|
| Re: Using Different Model & Diagram File [message #176697 is a reply to message #175124] |
Tue, 11 March 2008 16:53 |
| Eclipse User |
|
|
|
Originally posted by: mail.volker-wegert.de
Hi.
Ed Merks <merks@ca.ibm.com> writes:
> Kamesh Sampath wrote:
>> I am trying to follow the example and do the "Integrating EMF and GMF
>> Generated Editors by by Volker Wegert and Alex Shatalin".
>> What are the problems that we will be facing when we use seperate file for
>> model and diagram , how to work around that ?
> If I understand the issues I've seen correctly, when you keep the model in
> separate resource, it's obviously far easier for the diagram and the model
> to be out of sync since you can change the model and save it without have
> touched the diagram.
That's usually what you'd implement a single joint editor for. To avoid this,
I mean. But thanks for the warning - another bit for the article.
Volker
--
* Volker Wegert * http://www.volker-wegert.de/contact *
A computer scientist is someone who, when told to "Go to Hell", sees the "go
to", rather than the destination, as harmful.
|
|
|
Powered by
FUDForum. Page generated in 0.03116 seconds
Home