Eclipse Community Forums: GMF (Graphical Modeling Framework)

Home » Modeling » GMF (Graphical Modeling Framework) » TaiPan and EditingDomains

TaiPan and EditingDomains [message #148887]

Tue, 04 September 2007 11:20

Eclipse User

Can anybody explain why the Taipan example does not used shared editing
domain ids? What are the concrete effects resulting from this decision?
Would be nice if anybody could bring some light onto this and tell us
the reasons for using shared editing domains or not.

Re: TaiPan and EditingDomains [message #148991 is a reply to message #148887]

Wed, 05 September 2007 06:52

Eclipse User

Originally posted by: jan.herriger.gmx.de

Using shared EditingDomains means, that multiple editors are working
with the same ResourceSet instance. The advantage is, that one editor is
able to reflect model changes made by another editor immediately
(without saving).

Using different EditingDomains means, that each editor works with his
own ResourceSet. This way editors can't receive notifications resulting
from changes made by other editors. The user has to save the model, so
that WorkspaceSynchronizer can do the synchronization job.

I prefer the second solution, because the first one means, that changes
made in one editor would dirty all other editors. I think users wouldn't
expect that.

Axel Guckelsberger schrieb:
> Can anybody explain why the Taipan example does not used shared editing
> domain ids? What are the concrete effects resulting from this decision?
> Would be nice if anybody could bring some light onto this and tell us
> the reasons for using shared editing domains or not.

Re: TaiPan and EditingDomains [message #149014 is a reply to message #148991]

Wed, 05 September 2007 07:56

Eclipse User

Thanks :-)

Jan Herriger schrieb:
> Using shared EditingDomains means, that multiple editors are working
> with the same ResourceSet instance. The advantage is, that one editor is
> able to reflect model changes made by another editor immediately
> (without saving).
>
> Using different EditingDomains means, that each editor works with his
> own ResourceSet. This way editors can't receive notifications resulting
> from changes made by other editors. The user has to save the model, so
> that WorkspaceSynchronizer can do the synchronization job.
>
> I prefer the second solution, because the first one means, that changes
> made in one editor would dirty all other editors. I think users wouldn't
> expect that.
>
> Axel Guckelsberger schrieb:
>> Can anybody explain why the Taipan example does not used shared editing
>> domain ids? What are the concrete effects resulting from this decision?
>> Would be nice if anybody could bring some light onto this and tell us
>> the reasons for using shared editing domains or not.

Re: TaiPan and EditingDomains [message #157603 is a reply to message #148991]

Tue, 30 October 2007 07:44

Eclipse User

Originally posted by: trommas.yahoo.com

Jan Herriger wrote:
> Using shared EditingDomains means, that multiple editors are working
> with the same ResourceSet instance. The advantage is, that one editor is
> able to reflect model changes made by another editor immediately
> (without saving).
>
> Using different EditingDomains means, that each editor works with his
> own ResourceSet. This way editors can't receive notifications resulting
> from changes made by other editors. The user has to save the model, so
> that WorkspaceSynchronizer can do the synchronization job.

What gets synchronized here? Ex: say I create a "Book" in one editor,
and then a "Book Category" in another editor. Save both. Can the Book
object now relate to a Book category?

This would truly solve my biggest issue at the moment :)

Best Regards,

Tomas Zijdemans

Re: TaiPan and EditingDomains [message #157989 is a reply to message #157603]

Thu, 01 November 2007 06:26

Eclipse User

Originally posted by: jan.herriger.gmx.de

> What gets synchronized here?

DocumentProvider reloads changed resources.

Ex: say I create a "Book" in one editor,
> and then a "Book Category" in another editor. Save both. Can the Book
> object now relate to a Book category?
>
> This would truly solve my biggest issue at the moment :)

Did you try this? This should not be an issue. I assume both editors are
using the same model file. So adding an element in one editor and
performing save would force the other editor to relaod the model (and
"see" the new element).

Previous Topic:	EditPart Table
Next Topic:	Workspace editing domain + memory leak issues (attn: Ed Merks)

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jun 08 01:13:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter