@Alex: no, not yet checked in, I don't like to check in code that
doesn't 'compile' ;-) A couple of days more...
@Omar: no, I didn't. The original FalconJS POC and demonstration code
already have a great deal of Closure annotation in it, so I figured
the compiler was geared towards that already. A
Did you check this in? I'm not seeing any commit emails from you.
On 12/4/12 7:50 AM, "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. Bot
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
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 provi
