Eclipse Community Forums: Visual Editor (VE) » Choose an external listener

Home » Archived » Visual Editor (VE) » Choose an external listener

Choose an external listener [message #11053]

Tue, 16 December 2003 03:55

Eclipse User

When adding an event on a bean, it don't seems to be possible to choose an
external listener class. Is it a future enhancement ?

Re: Choose an external listener [message #11067 is a reply to message #11053]

Tue, 16 December 2003 05:01

Eclipse User

Hi bdemeyere

> When adding an event on a bean, it don't seems to be possible to choose an
> external listener class

Right now the pattern used for adding listeners is anonymous inner classes
that either implement the interface or extend the adapter class (if one is
specified in the BeanInfo).

Is the listener shared or unique for that Java bean ? Would you expect a
third radio choice of "Choose external listener" with a browser button that
then selected from available classes in the build path implementing the
listener interface and just code-gen'd something like

button.addActionListener(new MyOwnActionListener());

or would it be
private MyOwnActionListener myOwnActionListener;
....
button.addActionListener(myOwnActionListener);
....
text.addActionListener(myOwnActionListener);

Best regards,

Joe

Re: Choose an external listener [message #11203 is a reply to message #11067]

Tue, 16 December 2003 08:39

Eclipse User

Hi Joe,

If the two patterns you propose are valid, my first choice go to use an
unique listener (in a manner to bundle all the listener methods of one
bean).
Perhaps the choices could be like :
- add a new listener
that generate
private MyOwnListener; buton.add(MyOwn...)
- use an existing listener (that generate buton

If a such enhancement was added, it would be nice that the user can choose
the listener in a list restricted to the listeners in the project
classpath that implement the right listener interface regarding the nature
of the event.

Joe Winchester wrote:

> Hi bdemeyere

> > When adding an event on a bean, it don't seems to be possible to choose an
> > external listener class

> Right now the pattern used for adding listeners is anonymous inner classes
> that either implement the interface or extend the adapter class (if one is
> specified in the BeanInfo).

> Is the listener shared or unique for that Java bean ? Would you expect a
> third radio choice of "Choose external listener" with a browser button that
> then selected from available classes in the build path implementing the
> listener interface and just code-gen'd something like

> button.addActionListener(new MyOwnActionListener());

> or would it be
> private MyOwnActionListener myOwnActionListener;
> ....
> button.addActionListener(myOwnActionListener);
> ....
> text.addActionListener(myOwnActionListener);

> Best regards,

> Joe

Re: Choose an external listener [message #11219 is a reply to message #11203]

Tue, 16 December 2003 08:43

Eclipse User

bdemeyere wrote:

(soory my previous message was not finished)

Hi Joe,

If the two patterns you propose are valid, my first choice go to use an
unique listener (in a manner to bundle all the listener methods of one
bean).
Perhaps the choices could be like :
- add a new (external) listener
that generate
private MyOwnListener;
buton.add(MyOwnListener);
- use an existing (external) listener (that generate buton
that generate
buton.add(MyOwnListener);
where MyOwnListener is a listener choosed in a list.

If a such enhancement was added, it would be nice that the user can choose
the listener in a list restricted to the listeners in the project
classpath that implement the right listener interface regarding the nature
of the event.

Best regars and many thank to add VE to Eclipse.

> Joe Winchester wrote:

> > Hi bdemeyere

> > > When adding an event on a bean, it don't seems to be possible to choose
an
> > > external listener class

> > Right now the pattern used for adding listeners is anonymous inner classes
> > that either implement the interface or extend the adapter class (if one is
> > specified in the BeanInfo).

> > Is the listener shared or unique for that Java bean ? Would you expect a
> > third radio choice of "Choose external listener" with a browser button that
> > then selected from available classes in the build path implementing the
> > listener interface and just code-gen'd something like

> > button.addActionListener(new MyOwnActionListener());

> > or would it be
> > private MyOwnActionListener myOwnActionListener;
> > ....
> > button.addActionListener(myOwnActionListener);
> > ....
> > text.addActionListener(myOwnActionListener);

> > Best regards,

> > Joe

Re: Choose an external listener [message #11400 is a reply to message #11219]

Tue, 16 December 2003 15:15

Eclipse User

Hi bdemeyere,

> If the two patterns you propose are valid, my first choice go to use an
> unique listener (in a manner to bundle all the listener methods of one
> bean).
> Perhaps the choices could be like :
> - add a new (external) listener
> that generate
> private MyOwnListener;
> buton.add(MyOwnListener);
> - use an existing (external) listener (that generate buton
> that generate
> buton.add(MyOwnListener);
> where MyOwnListener is a listener choosed in a list.
>
> If a such enhancement was added, it would be nice that the user can choose
> the listener in a list restricted to the listeners in the project
> classpath that implement the right listener interface regarding the nature
> of the event.

I like this idea - to advance it further could you please enter a bugzilla feature
request against the VE feature. That way it can be discussed further and you can
track its progress.

Best regards,

Joe Winchester

Re: Choose an external listener [message #574639 is a reply to message #11053]

Tue, 16 December 2003 05:01

Eclipse User