Re: svn: /web/php/branches/PROTOTYPE_2010/ css/structure.css css/theme.css index.html js/common.js js/jquery.autocomplete.pack.js
js/search-index-en.js
| From: | Paul Dragoonis | Date: | Wed, 30 Dec 2009 12:09:08 +0000 |
| Subject: | Re: svn: /web/php/branches/PROTOTYPE_2010/ css/structure.css css/theme.css index.html js/common.js js/jquery.autocomplete.pack.js js/search-index-en.js |
||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-6870@lists.php.net to get a copy of this message | ||
Hi Stew.
Does that mean we're giving up on the Description (coming from XHR) or
continuing with it?
Just making sure before i spend ages implementing it.
Cheers.
Paul Dragoonis.
On Wed, Dec 30, 2009 at 6:13 AM, Stewart Lord <stewey@ambitious.ca> wrote:
> Indeed.
>> I think those need to be done with a XHR to the backend, with a local
>> cache store (checking that one first obviously).
>> The annoying part there is that lookup is gonna take few milliseconds
>> (if it didn't hit the user client cache) before the descriptions show
>> up..
>>
>
>
> Agreed, and it adds a lot of complexity to the implementation. Looking at
> how autocomplete is most commonly done (Google, Hulu, Youtube, etc...) it
> just has the top matches in a simple menu. I'd be inclined to stick with
> this for now.
>
> Lots of other stuff to do anyway :)
>
> Stew
>