|
|
|
Re: Provide context specific "views" on an EObject [message #1021040 is a reply to message #1020916] |
Tue, 19 March 2013 12:23 |
Ed Merks Messages: 33217 Registered: July 2009 |
Senior Member |
|
|
Johannes,
Comments below.
On 19/03/2013 8:08 AM, Johannes Wachter wrote:
> Hi Ed,
>
> thanks for your response.
>
> Concerning your comments:
>
> Perhaps the term view was a bad choice, it's more like our framework
> chooses which features are allowed to be seen (and edited) by a 3rd
> party form showing a certain entity type.
I see.
>
> The additionally added features are transient since they are normally
> calculated based upon other features in the same class.
Transient and derived...
> I had the idea with the idea to solve it via a subclass but I was
> concerned about duplicating and synchronizing all the information
> between the original instance and the subclass.
Yes that could be quite a bit of work.
> For that we would essentially need an Adapter that relays all
> Notifications in both directions if im correct? Or is there a more
> lightweight solution I'm not aware of?
Not really.
>
> Concerning your last comment with stateful adapters: This seems to be
> a good solution but would mean to lose the nature of the EObject since
> we can only react to "set" calls but not to "get" calls which would be
> the interesting thing in our case.
I see.
>
> Regards,
> Johannes
>
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03424 seconds