[Moo] mootools and google closure compiler

[noiv]

mootools (core+more+clientcide) behaves quite nice with the javascript
optimizer at
http://closure-compiler.appspot.com/home

Only pattern like for (var i = 2; i--; i){} lead to ignorable
warnings. The compiler runs in the cloud on google's app engine
framework accepting POSTs using curl or local (http://closure-
compiler.googlecode.com/files/compiler-latest.zip) and fits perfectly
in a scripted, automated process.

I could reduce overall loading time and size by more than 30% with
simple optimisation. Still re-writing code for the advanced
optimisation, though.

Just for the early adapters.

--noiv

[anutron]

yep. we've been discussing it in the dev group. it's interesting stuff.

On Fri, Nov 6, 2009 at 10:31 AM, noiv <[hidden email]> wrote:

mootools (core+more+clientcide) behaves quite nice with the javascript
optimizer at
http://closure-compiler.appspot.com/home

Only pattern like for (var i = 2; i--; i){} lead to ignorable
warnings. The compiler runs in the cloud on google's app engine
framework accepting POSTs using curl or local (http://closure-
compiler.googlecode.com/files/compiler-latest.zip) and fits perfectly
in a scripted, automated process.

I could reduce overall loading time and size by more than 30% with
simple optimisation. Still re-writing code for the advanced
optimisation, though.

Just for the early adapters.

--noiv

[samdev]

I dont see point in FOR third statement:

for (var i = 2; i--; i){}

I'd rather do:

for( var i = 2; --i; ) {...}

On Nov 6, 2009, at 12:31 PM, noiv wrote:

>
> mootools (core+more+clientcide) behaves quite nice with the javascript
> optimizer at
> http://closure-compiler.appspot.com/home
>
> Only pattern like for (var i = 2; i--; i){} lead to ignorable
> warnings. The compiler runs in the cloud on google's app engine
> framework accepting POSTs using curl or local (http://closure-
> compiler.googlecode.com/files/compiler-latest.zip) and fits perfectly
> in a scripted, automated process.
>
> I could reduce overall loading time and size by more than 30% with
> simple optimisation. Still re-writing code for the advanced
> optimisation, though.
>
> Just for the early adapters.
>
> --noiv

[Jan Kassens]

Some problem was the reason for the statement at the end. I think it  
was Dean Edward’s packer, but I cant really remember.


Jan

On 06.11.2009, at 20:04, samdev wrote:

>
> I dont see point in FOR third statement:
>
> for (var i = 2; i--; i){}
>
> I'd rather do:
>
> for( var i = 2; --i; ) {...}
>
> On Nov 6, 2009, at 12:31 PM, noiv wrote:
>
>>
>> mootools (core+more+clientcide) behaves quite nice with the  
>> javascript
>> optimizer at
>> http://closure-compiler.appspot.com/home
>>
>> Only pattern like for (var i = 2; i--; i){} lead to ignorable
>> warnings. The compiler runs in the cloud on google's app engine
>> framework accepting POSTs using curl or local (http://closure-
>> compiler.googlecode.com/files/compiler-latest.zip) and fits perfectly
>> in a scripted, automated process.
>>
>> I could reduce overall loading time and size by more than 30% with
>> simple optimisation. Still re-writing code for the advanced
>> optimisation, though.
>>
>> Just for the early adapters.
>>
>> --noiv
>