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: | Stewart Lord | Date: | Wed, 29 Dec 2010 01:14:07 +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 4 | Groups: | php.webmaster |
| Request: | Send a blank email to php-webmaster+get-9917@lists.php.net to get a copy of this message | ||
On Tue, 28 Dec 2010 19:13:21 +0100, Hannes Magnusson
<hannes.magnusson@gmail.com> wrote:
> 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 :]
Sounds good!
>> 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?
You are right. Uncompressed it saves 78K, gzipped it only saves 2K.
Are you asking if jQuery will care about gzip? I don't think it will know
the difference. If we gzip it we will need to make sure we emit the correct
content encoding headers for the browser to decode it. Some browsers don't
support gzipped JS - not sure if we care to support those or not.
Stew