Hi Adrian

Thanks for explanation, but isn't an autocomplete something that could just
as easily be used in a swing environment?  I don't see anything about it's
behaviour that is ajax specific.  The more I think about it I see can't why
we don't just have an autocomplete element, all we'd be telling the platform
specific renderer to do is take the user input and search a list of values
for any matches then show them to the user so they can select one.

Regards
Scott

2008/6/23 Adrian Crum <[EMAIL PROTECTED]>:

> --- On Sun, 6/22/08, Scott Gray <[EMAIL PROTECTED]> wrote:
> > While we're (sort of) on the  topic of the
> > autocomplete, does anybody really
> > find the following intuitive?
> > <field name="exampleFeatureId"
> > id-name="exampleFeatureId">
> >     <text/>
> >     <on-field-event-update-area
> > event-type="change"
> > area-id="exampleFeatureId"
> > area-target="findExampleFeatures"/>
> > </field>
>
> The ajax stuff is still being developed. One thing that was suggested was
> to have an additional attribute to describe the type of server-side action:
>
> <on-field-event-update-area
>  event-type="change"
>  area-id="exampleFeatureId"
>  area-target="findExampleFeatures"
>   server-action="autocomplete"/>
>
> I can't think of a better element name. It's expressing "On a field event,
> update an area of the screen."
>
> The event type (in the HTML world) would be either change or click.
>
> The area id is the area (HTML container) to be updated when the event
> occurs.
>
> The area target is the URL called to update the area specified in area-id.
>
> The server action is a description of what type of response the server will
> put in the area.
>
> If anyone has suggestions for better names, then this is a good time to
> make them - before we get any further into Ajax development. Just keep in
> mind that the syntax shouldn't be Ajax-specific - because the widgets are
> intended to support more than one rendering format. Also keep in mind that
> more than one ajax event can be triggered by a field event.
>
> -Adrian
>
>
>
>
>

Reply via email to