I agree with Anil that there may be many different types of on-field-
event-update-area
If we want to keep things simple we may just add some attributes to
the on-field-event-update-area element; for example:
<on-field-event-update-area event-type="change" area-
id="exampleFeatureId" area-target="findExampleFeatures" type="text-
server-autocomplete"/>
Just my 2 cents,
Jacopo
I'm sorry if I am saying something that is not in the c
On Jun 6, 2008, at 7:58 PM, Adrian Crum wrote:
Anil Patel wrote:
The way its implemented in this commit is very specialized use. On
change in textbox a dropdown appears and user can navigate in that
list and select a option. This is a clearly a very specialized
handling of form event and expected user Interaction. Unless
somebody looks at the implementation code its hard figure out.
I think we should add a sub element <use-server-autocomplete> and
this element can have attributes and sub elements that we may need
to pass to the Ajax.Autocompleter control of Script.Aculo.us.
That sounds good to me. My main objection to the original
implementation was the use of attributes - so an additional sub
element would be fine.
And for <on-field-event-update-area> element we should be able to
pass in name of event handler function name. Developer can use
such event listeners to implement custom stuff.
I'd have to see an example. I'm not sure what you mean here.
-Adrian
