Custom parse functions are not going away, its just that the current solution, as you noted, is far from optimal. A common scenario is parsing JSON, which is also way to complex with the current API.
Jörn On Fri, Jun 27, 2008 at 10:16 PM, Felix Schwarz <[EMAIL PROTECTED]> wrote: > Hi, > > still using the autocomplete script from > http://bassistance.de/jquery-plugins/jquery-plugin-autocomplete/ > > Currently the script expects by default that the response contains the > data as "visible text|other data" with one item per line (at least this > is what I figured out from reading the source, I did not find any > documentation about this - maybe I'm wrong!). > > I have an application which returns HTML because this was the preferred > format for another autocompletion script which uses a different js > library. Now I want to make the switch to jQuery but I don't want to > change the application if not absolutely necessary. > > It was quite easy using a custom parse function by using the parse > option (again, undocumented). But for me its much easier to just > transform my data into the default format and let the default parse > function do its job. But I did not find a way to call the default parse > function so I ended up copying it. Is there another way? > > Furthermore I like to know if custom parse functions are an official > features (I did not find any documentation about them) or if they are > likely to go away in the future... > > fs > > > >
