| design question - bundle feature classes as local classes? [message #640401] |
Sun, 21 November 2010 12:43  |
Eclipse User |
|
|
|
Hello,
I'm unsure about how to keep my editor structured "the right way". I've got
some stuff that occurs throughout all feature classes that handle a certain
model element. Since the feature classes all have different superclasses, I
can't use inheritance to keep them together. So I was thinking about putting
them as local classes inside a "wrapper class" that also provides the common
constants, methods, whatever. I've tried it and it's technically possible, but
is it a good idea? What do you think?
Thanks
Volker
--
* Volker Wegert * http://www.volker-wegert.de/contact *
"Documentation is like sex: when it is good, it is very, very good; and when
it is bad, it is better than nothing." (Dick Brandon)
|
|
|
| Re: design question - bundle feature classes as local classes? [message #640787 is a reply to message #640401] |
Tue, 23 November 2010 02:46  |
| Eclipse User |
|
|
|
Sure, this is a valid approach. From Graphiti side there are no issues with
that involved that I can currentyl think of.
An alternative approach would be to use delegation for implementing common
functionality.
Michael
"Volker Wegert" <mail@volker-wegert.de> wrote in message
news:84y68mbmij.fsf@zak.home.volker-wegert.de...
> Hello,
>
> I'm unsure about how to keep my editor structured "the right way". I've
> got
> some stuff that occurs throughout all feature classes that handle a
> certain
> model element. Since the feature classes all have different superclasses,
> I
> can't use inheritance to keep them together. So I was thinking about
> putting
> them as local classes inside a "wrapper class" that also provides the
> common
> constants, methods, whatever. I've tried it and it's technically possible,
> but
> is it a good idea? What do you think?
>
> Thanks
> Volker
>
> --
> * Volker Wegert * http://www.volker-wegert.de/contact *
> "Documentation is like sex: when it is good, it is very, very good; and
> when
> it is bad, it is better than nothing." (Dick Brandon)
|
|
|
|
| Re: design question - bundle feature classes as local classes? [message #641302 is a reply to message #640787] |
Wed, 24 November 2010 13:43 |
| Eclipse User |
|
|
|
Hi Volker and Michael,
as I indicated to Michael at the recent Eclipse Summit Europe in
Ludwigsburg I also follow this approach an am quite happy with it.
I also used the EMF generated model switch to dispatch to feature
providers by the EClass of the involved business object.
Soon all this will be public as we make our initial contribution for the
eTrice project (http://www.eclipse.org/etrice is still under
construction but have a look on http://www.eclipse.org/proposals/etrice
and http://wiki.eclipse.org/ETrice).
Cheers,
Henrik
Am 23.11.2010 08:46, schrieb Michael Wenz:
> Sure, this is a valid approach. From Graphiti side there are no issues
> with that involved that I can currentyl think of.
>
> An alternative approach would be to use delegation for implementing
> common functionality.
>
> Michael
>
>
> "Volker Wegert" <mail@volker-wegert.de> wrote in message
> news:84y68mbmij.fsf@zak.home.volker-wegert.de...
>> Hello,
>>
>> I'm unsure about how to keep my editor structured "the right way".
>> I've got
>> some stuff that occurs throughout all feature classes that handle a
>> certain
>> model element. Since the feature classes all have different
>> superclasses, I
>> can't use inheritance to keep them together. So I was thinking about
>> putting
>> them as local classes inside a "wrapper class" that also provides the
>> common
>> constants, methods, whatever. I've tried it and it's technically
>> possible, but
>> is it a good idea? What do you think?
>>
>> Thanks
>> Volker
>>
>> --
>> * Volker Wegert * http://www.volker-wegert.de/contact *
>> "Documentation is like sex: when it is good, it is very, very good;
>> and when
>> it is bad, it is better than nothing." (Dick Brandon)
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03873 seconds
Home