Yeah, thats supposed form a stable API for a few years. Autocomplete is high on our priority list, so... if you want to help, help with fixing bugs in other jQuery UI components, as that gives us the time to work on new stuff. A list of open blockers and criticals is here: http://dev.jqueryui.com/query?status=accepted&status=assigned&status=new&status=reopened&group=component&max=250&order=priority&priority=blocker&priority=critical&col=id&col=summary&col=owner&col=type&col=priority&col=version&milestone=1.8&report=16
Jörn On Wed, Jul 8, 2009 at 6:48 AM, Andrew McHarg<[email protected]> wrote: > Looks great! The changes to the data model are nice also. The current one is > slightly > confusing. Let me know if you need help or patches. I have a version of 1.0.2 hacked to allow for something > similar to the 'source' but it appears that this proposal is more ambitious. > On Tue, Jul 7, 2009 at 5:30 PM, Jörn Zaefferer > <[email protected]> wrote: >> >> Thats planned for the jQuery UI autocomplete widget: >> http://wiki.jqueryui.com/Autocomplete >> >> Take a look at the proposals for the source (and related parse) >> options. See any shortcomings there? >> >> Jörn >> >> On Tue, Jul 7, 2009 at 10:19 PM, Andrew McHarg<[email protected]> wrote: >> > >> > It would be nice if the autocomplete plugin accepted a function that >> > retrieved the data on behalf of the plugin instead of being stuck with >> > either static data or a relatively inflexible canned ajax request. >> > >> > $("#example").autocomplete(function (term, success, failure) { /* do >> > custom method for retrieving data */ }); >> > >> > This seems like it would be fairly easy to do. Simply making the >> > request function an option would probably suffice. I will probably >> > hack this up this afternoon and have a patch for it if anyone wants >> > it. :) >> > > >
