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: Date: Thu, 24 Dec 2009 12:51:04 +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  Groups: php.webmaster 
Request: Send a blank email to php-webmaster+get-6835@lists.php.net to get a copy of this message
On Thu, Dec 24, 2009 at 07:53, Stewart Lord <stewey@ambitious.ca> wrote: > > On 23-Dec-09, at 12:30 PM, Paul Dragoonis wrote: > >> I see that you're now trying to do it client-side. I thought we were doing >> some server side stuff too. > > That was the original plan, but Hannes suggested sending the whole index to > the client and it looks to be a winning strategy. It makes the autocomplete > very snappy. We still need the site search though (docs (content), mailinglists, changelogs, ..). Y! probably have JS APIs for it though, so maybe we can skip the PHP backend entirely. Whats missing from the autocomplete is however the basic textual description of what the function/method does, so we may need to hit the backend to populate that info as that info could be quite huge. I still like the the http://ambitious.ca/php/search-1.png idea. Would be awesome if we could somehow populate some parts of it from the client side, and do xhr do populate the larger parts. -Hannes

« previous php.webmaster (#6835) next »