well,
we have found that query 1.3.1 is around 55kb
well it is not a big problem but why not to compress it,if we can
i have been using compressed version of 1.2.6 which is around 28kb only…(the one found in jquery site is around 53kb)
i found it in some script…
it use to work in most of the codes till now
but lately i found that i need atleast 1.3.1 to get one code work…
now is there any way to even compress that 1.3.1 minified version…?
i think it is possible as we see the compressed version of 1.2.6 version
which is like this
just part of it…
but we dont know what was it compressed with
most of the javascript compressor dont work on minified version as it is already compressed to 1 level…
thanks
We are NOT asking how the minified version that is available for the download in jquery.com compressed…
rather as i say,that 1.2.6 (we found in a script) seems to be compressed with something other because of which it was just 28kb only.
(not 53kb as 1.2.6.minified version is…)
so we are searching for that optimized compressor…
or other possibility may be some jquery expert removed unnecesary codes from 1.2.6 and then compressed it bcoz of which it has been only 28kb
ok,here you go
EDIT
it is called jquery-1.2.6.pack.js and use to work with most of the scripts till now…
EDIT: i posted whole code then when i open this page the browser crashed…may be bcoz of codes
so i think i need to find some free file host…
ok i will find one and upload that file soon
thanks
but
the compressor was effect less for minified version ,in fact it increased the size to 6okb
and i brought the original full file from jquery site and compressed it…still i could not get it less than around 54-55kb which is what jquery.com minified version is now…
Assuming you serve the js gzipped, the final amount of bytes is very similar regardless of whether you used packer, or just minified it using something like the yahoo compressor, or googles closure compiler.
packer is impressive, but realize it’s doing stuff along the same lines as what gzip does. The drawback is that the browser needs to eval() to uncompress it on every page load, whereas a browser will ungzip it once, and store it uncompressed in it’s local cache.
Testing with 1.3.2, I still get the smallest size with googles compiler + gzip.