- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 9 Dec 2004 00:45:19 +0000 (UTC)
On Mon, 22 Nov 2004, [ISO-8859-1] Olav Junker Kj?r wrote: > > The first thing people are going to do with WF2 is to try to extend it > with new widgets, because widgets are fun. Therefore extensibility is > critical for adoption. [...] That's mostly the realm of XBL and the Web Controls spec. > ...I propose the addition of a valuechanged event. The widget could > listen to this event, and update the UI accordingly. Of course, the > widget must not call changed() as a result of this! The last bit is a > bit dangerous, since authors will confuse onchange and onvaluechanged > and cause loops - I dont have a solution for this. Maybe the widget > would have to explicitly register itself with the model, and the model > will call a valuechanged method on the widget, rather that firing an > event? One option is to have this event (valueChange) but not have an attribute for it, so you have to listen for it using DOM event listeners. We should probably do this anyway, for ATs. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 8 December 2004 16:45:19 UTC