Surely sendmail reeled when thusly spake Geert Bevin: > > 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.
I see you've come down in favor of OpenLaszlo: http://rifers.org/blogs/gbevin/2005/9/15/whats_next_for_ria You mention that you'd take a Swing client-side app any day. Have you ever examined Thinlet? I've played around with it, and it's actually quite nice. It can run in a wide variety of browser JVM's -- if I'm not mistaken, it can for example run in Firefox as it is configured at time of download. The event model is dead simple (threads? what's a thread?) and the widget collection is quite sufficient. And it's JAVA not some horrible Javascript mess ;-) Mapping Rife Elements to Thinlet widgets would be excellente. And doable. My 0,02$ (currently 18/11 eurocents). fred -- F.Baube * "Happy songs never made me happy. Georgetown/MSFS/1988 * A lot of sad songs have." email fbaube#welho.com * -- Mira Aroyo, Ladytron gsm +358 41 536 8192 * wmd 60°11'10.8"N 24°57'36.9"E _______________________________________________ Rife-users mailing list [email protected] http://www.uwyn.com/mailman/listinfo/rife-users
