He contacted me via email outside of the mailing list. The auto completer in scriptaculous couldn’t provide the functionality he needed. I gave him the general design of what I did way before the scriptaculous auto completer came out. He said thanks and ran I think.
Sorry you guys sort of got lost in the shuffle.
-Andrew Martinez
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jeoff Wilks
Sent: Wednesday, May 31, 2006 7:49 AM
To: [email protected]
Subject: Re: [Rails-spinoffs] throttling...
So did you ever get that working? (i.e. figure out how to display all results before anything has been typed).
On 5/23/06, Mark McCray < [EMAIL PROTECTED]> wrote:
What we have is this:
A search box:
________
Then we have a box where put in all of the results of the search goes:
**********************
* *
**********************
(The thing with the box is that, if there isn't anything inside the
search box, the results should show all available keywords. So the
search box is acting more like a filter i guess.)
Then in the box with all the search results, we want to be able to
click on a word and have it populate a multiple select box.
So whatever you click in the results box ends up in a multiselect
box. The multiselect boxes get saved on a receiving page.
The results box is really a list of metadata keywords. And the search
box really filters that stuff down. The user needs to be presented
with all options before filtering, which is different than how i've
used the ajax.autocompleter before.
I hope this makes sense.
And thanks for the help.
Mark
On May 23, 2006, at 4:01 PM, Jeremy Kitchen wrote:
> On Tuesday 23 May 2006 11:54, Mark McCray wrote:
>> Actually,
>> here's what i'm trying to do:
>>
>> I want the user to be able to type in some text in an input field and
>> i only want the ajax request to happen after the user has stopped
>> typing for 1 or two seconds. Kind of like how google suggest or
>> autocompleter works. I can't use the ajax autocompleter because we
>> have a specific requirement that makes the autocompleter not work for
>> us.
>
> and what requirement might that be? I subclassed the autocompleter
> to make it
> handle the server returning an xml document instead of a bunch of
> li tags...
>
> if you can tell us what you need the autocompleter to do, perhaps
> we can help
> you do it.
>
> the reason I ask this is because the autocompleter already has that
> throttling
> built in, so why reinvent the wheel? (although, if in the end you
> really do
> have to reinvent the wheel, just check out the autocompleter's code
> and
> you'll find a good example)
>
> -Jeremy
>
> --
> Jeremy Kitchen ++ [EMAIL PROTECTED]
>
> http://ipaction.org/ -- defend your rights to fair use
> _______________________________________________
> Rails-spinoffs mailing list
> [email protected]
> http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
