I'm hazy on what the variety of events is. HTML supports PUT
and POST, and Javascript supports purely local validation, and
Ajax can support round-trips to the server.
Did you have something else in mind ? Such as interdependencies
between widgets (if X is "Y" then disable Z) ?
Typically, each widget should be able to respond to certain events:
* "onClicked", "onEnabled", "onDisabled" for a button
* "onExpand", "onCollapse", "onSelect", ... for a tree
* "onGetItems", "onSelect" for a combobox
* etc
This is normally done with a tree of widgets (in Swing), where core
events are captured by listeners (which are for instance more
functional widgets. These widgets can then themselves support new
event types that are specific for them. This is the model that Wicket
uses. I'm not sure it makes total sense in the context of RIFE and if
the same design should be applied, which is why I'm soliciting input.
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
