Sounds great, I submitted bug58. By the “DirectLink” suggestion I meant what you are talking about, having a “parameters” binding that can provide additional information to the search listener, similar to the “parameters” binding that DirectLink has.

 

Thanks!

 

Ben

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jesse Kuhnert
Sent: Wednesday, February 15, 2006 11:24 AM
To: [email protected]
Subject: Re: [Tacos-devel] Autocompleter in a loop

 

I see your problem. If you add this to the BugReporter for tacos I can take a look at it.

I'd like to explore the js provided by http://wiki.script.aculo.us/scriptaculous/show/Ajax.Autocompleter to see if there isn't a way to enable setting a "parameters" sort of binding to the component first, so you can pass in any context you like. If that doesn't work out I can move on to other things like the DirectLink.

Does this sound good?

On 2/15/06, Ben Dotte <[EMAIL PROTECTED]> wrote:

Hi,

 

I've been using the Autocompleter with success, it's a very nice component, but I've run across a situation where I need to use it in a loop. The problem is the fields I'm looping over are no longer available when the ajax call is made to search over the list of choices for each field and the search listener itself only gives me a String to work with. I asked Howard about this (he happened to be onsite when I ran into this) and while he didn't have an immediate solution, a suggestion he had was to have the ability in Autocompleter to provide additional parameters like DirectLink, for example, to give context to the search listener for cases like this.

 

So, does anyone have any other suggestions to fix this problem or would it be possible to work Howard's solution into the Autocompleter component?

 

Thanks,

Ben

 

Reply via email to