XulAction programmation model

Hi Gerald and all the Luxor fans,

Wouldn't it be easier to handled action in a
reflective way instead of creating XulAction object
(whose purpose is just to do linking)... Since XulForm
parse all the action on startup in the xul file, this
shouldn't be such a hassle. This way handling an event
could just be the same as implementing a method, like
for example : 
public void handle_button_save_click();

This may be a more elegant way in the future to handle
the jungle of events that are thrown from everywhere
in the swing and xul framework

In fact I have run into some syntaxic problems using
the --- new XulAction(".."){ public void execute(){}};
 --- way of handling actions. Indeed, making use of
anonymous inner class definition has some points in
common with C++ multi-inheritance and I ran into some
method signature clash from method inside my XulForm
hierarchy (which can be called form the inner class)
and my XulAction hierarchy..

And anyway, I don't think that creating a XulAction
object for linking a widget to a method is not the
most intuitive way of reaching that goal. Moreover,
Luxor would reach a much broader audience if it was
somehow simpler.

Please give me some feedback ! 

Cheers,

Denis

=====
=========================
|Denis Cardon, Tranquil I.T. Systems 
|10 rue du Docteur Bouchard, 49400 Saumur
|Tel: +33(0)2.41.67.56.99
|Web: http://www.tranquil-it-systems.fr
=========================

__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/