| Extending EditDomain or EditPartViewer to Store Custom Information [message #173701] |
Sat, 26 March 2005 08:28  |
Eclipse User |
|
|
|
Originally posted by: rudolf.vaum.net
I am implementing some customizations to my gef editor. I was wondering what
is the most appropriate place to store some additional information (like
custom selection information) that would be specific for one editor
instance.
(this info would definitely be not model-specific, so I wouldn't want to
store in the model)
So far, I thought of extending either the EditDomain or the EditPartViewer
and put my variables in there.
Which one should I use? What is the best design choice for this?
Thanks
Rudi
|
|
|
| Re: Extending EditDomain or EditPartViewer to Store Custom Information [message #173733 is a reply to message #173701] |
Sat, 26 March 2005 10:48  |
| Eclipse User |
|
|
|
Originally posted by: rudolf.vaum.net
I have also discovered in the JavaDocs that the RootEditPart might also be a
candidate as it "allows the application's 'real' EditParts to be more
homogeneous", so it might seem logical to override it and add some
functionality/data there.
Also, are the properties that can be set in a GraphicalViewer via
"setProperty" meant to be used by client code?
Rudi
"Rudi Vaum" <rudolf@vaum.net> wrote in message
news:d23b9f$ti1$1@news.eclipse.org...
> I am implementing some customizations to my gef editor. I was wondering
what
> is the most appropriate place to store some additional information (like
> custom selection information) that would be specific for one editor
> instance.
> (this info would definitely be not model-specific, so I wouldn't want to
> store in the model)
>
> So far, I thought of extending either the EditDomain or the EditPartViewer
> and put my variables in there.
>
> Which one should I use? What is the best design choice for this?
>
> Thanks
> Rudi
>
>
>
|
|
|
|
| Re: Extending EditDomain or EditPartViewer to Store Custom Information [message #173802 is a reply to message #173701] |
Mon, 28 March 2005 15:27 |
| Eclipse User |
|
|
|
Originally posted by: none.us.ibm.com
Are you saving the info? you can use viewer properties. If the info needs
to be saved, but not in the model, the resource plug-in provide metadata
facilities. Basically, a ghost file with "terd" data in it that gets
deleted should the resource go away.
"Rudi Vaum" <rudolf@vaum.net> wrote in message
news:d23b9f$ti1$1@news.eclipse.org...
>I am implementing some customizations to my gef editor. I was wondering
>what
> is the most appropriate place to store some additional information (like
> custom selection information) that would be specific for one editor
> instance.
> (this info would definitely be not model-specific, so I wouldn't want to
> store in the model)
>
> So far, I thought of extending either the EditDomain or the EditPartViewer
> and put my variables in there.
>
> Which one should I use? What is the best design choice for this?
>
> Thanks
> Rudi
>
>
>
|
|
|
| Re: Extending EditDomain or EditPartViewer to Store Custom Information [message #174109 is a reply to message #173802] |
Tue, 29 March 2005 07:22 |
| Eclipse User |
|
|
|
Originally posted by: rudolf.vaum.net
I did use the viewer properties. I don't intend to save the info - it's just
a custom selection property - I only need it as long as an editor instance
is
open.
It's working quite nicely - thanks guys.
Rudi
"Randy Hudson" <none@us.ibm.com> wrote in message
news:d29clk$6rt$1@news.eclipse.org...
> Are you saving the info? you can use viewer properties. If the info
needs
> to be saved, but not in the model, the resource plug-in provide metadata
> facilities. Basically, a ghost file with "terd" data in it that gets
> deleted should the resource go away.
>
> "Rudi Vaum" <rudolf@vaum.net> wrote in message
> news:d23b9f$ti1$1@news.eclipse.org...
> >I am implementing some customizations to my gef editor. I was wondering
> >what
> > is the most appropriate place to store some additional information (like
> > custom selection information) that would be specific for one editor
> > instance.
> > (this info would definitely be not model-specific, so I wouldn't want to
> > store in the model)
> >
> > So far, I thought of extending either the EditDomain or the
EditPartViewer
> > and put my variables in there.
> >
> > Which one should I use? What is the best design choice for this?
> >
> > Thanks
> > Rudi
> >
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 5.03523 seconds
] 
Search
Help
Register
Login
Home
