incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omar Gonzalez <omarg.develo...@gmail.com>
Subject Re: [FalconJS] Using Google Closure Tools
Date Tue, 04 Dec 2012 15:56:28 GMT
Did you try Uglify.js? It has about the same compression results as GCC but
runs a lot faster. There's also an Uglify 2.0 that's supposed to be even
faster than 1.x.

-omar

On Tuesday, December 4, 2012, Erik de Bruin wrote:

> Hi,
>
> After a lot of reading, trying and testing, as well as looking at the
> current code and compiler output, I think the project is best of using
> the Google Closure Tools. Both for developing and deploying FlexJS
> components and applications. I've implemented them into the FlexJS
> workflow, and provided instructions on how install and use them:
> Closure Linter,  -Compiler, -Builder and finally the -Library [1]. The
> end result of this toolchain will highly optimized and compressed JS,
> while allowing for an intermediate step (for dev/debug) that supports
> all major AS features (inheritance, interfaces, variable scope,
> constants, strong typing etc.).
>
> Not all the pieces are in place, so a little patience, please ;-)
>
> Also, as I refactored the framework "a bit", the FalconJS people can
> dig their teeth into a new output template/pattern (simpler than the
> one currently used).
>
> EdB
>
> 1: https://developers.google.com/closure/
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message