Re: svn: /web/php/trunk/ include/header.inc js/common.js js/jquery.autocomplete.js js/jquery.autocomplete.pack.js styles/structure.css
styles/theme.css
| From: | Hannes Magnusson | Date: | Tue, 28 Dec 2010 18:13:21 +0000 |
| Subject: | Re: svn: /web/php/trunk/ include/header.inc js/common.js js/jquery.autocomplete.js js/jquery.autocomplete.pack.js styles/structure.css styles/theme.css |
||
| References: | 1 2 3 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-9915@lists.php.net to get a copy of this message | ||
On Tue, Dec 28, 2010 at 18:43, Stewart Lord <stewey@ambitious.ca> wrote:
> On Tue, 28 Dec 2010 10:04:52 +0100, Hannes Magnusson
> <hannes.magnusson@gmail.com> wrote:
>> This needs to be /js though.
>
> Thanks for fixing this!
>
>> And now the question is; how to generate that file?
>
> It's basically just: file_put_contents(json_encode($index)). Where index is
> an array containing elements: array('name' => <func>, 'page' =>
> <file>) for
> each ref entry in the manual. E.g.:
>
> array('name' => 'strpos', 'page' =>
> 'function.strpos.php'),
> array('name' => 'strchr', 'page' =>
> 'function.strchr.php'),
> ...
We should probably create it during manual build time then from PhD.
Then I suppose we could also create a description file.. If that won't
be huge :]
> It occurs to me that we could shrink the index file substantially by
> dropping the 'name' and 'page' keys and just adopting the convention that
> name and page are elements 0 and 1 respectively.
Thats not gonna matter once the data is .gzipped.. jQuery won't care, will it?
-Hannes