[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Policy on implementing SWT listener interfaces
|
If it is an API class then it must use inner classes but if it is a
internal class, it is up to the developer.
I like anonymous inner classes better. If the class is very simple (which
is not the case here), I don't mind if the class implements the SWT
listener.
Eduardo.
"Knut Radloff" <knut_radloff@xxxxxxx>
Sent by: platform-ui-dev-admin@xxxxxxxxxxx
09/23/2002 06:10 PM
Please respond to platform-ui-dev
To: platform-ui-dev@xxxxxxxxxxx
cc:
Subject: [platform-ui-dev] Policy on implementing SWT listener interfaces
There are many places in platform ui where classes implement SWT listener
interfaces. In general I think this is a bad idea.
For example org.eclipse.ui.internal.PartDragDrop, which I'm currently
working on, has a bunch of mouse listener methods that clutter the public
interface.
What is the UI team's policy on this topic? Is there one?
If I change PartDragDrop to use inner classes for the listeners it would
be a matter
of "different but right" vs. "same as everybody but wrong" (in my opinion
anyway).
Does anyone care?
Knut
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
