Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <CCE372E5.4968F%aharui@adobe.com>
References: 
 <CAJs+wW0gyv0tk2hJP7CepLzLP-35Y=Cn+tuQ+oV2oSvHZS=o3A@mail.gmail.com>
	<CCE372E5.4968F%aharui@adobe.com>
Date: Tue, 4 Dec 2012 18:47:35 +0100
Message-ID: 
 <CAJs+wW1=GS6T4u+MDqOqgAk9D0wSF4DHq1O5utUe1n970OW70g@mail.gmail.com>
Subject: Re: [FalconJS] Using Google Closure Tools
From: Erik de Bruin <erik@ixsoftware.nl>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

@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. Also, I'm not only
setting up the Closure Compiler, but also the Linter and the Builder.
The last one is particularly interesting, as it "compliles" the ENTIRE
application (framework AND application code) into one file, resolving
dependencies, optimising the heck out of what is needed etc. That, and
the fact that with the Closure annotations you can build code that
pretty much allows for most features in AS, as long as you compile it
with GCC.

EdB


On Tue, Dec 4, 2012 at 6:29 PM, Alex Harui <aharui@adobe.com> wrote:
> Did you check this in?  I'm not seeing any commit emails from you.
>
>
> On 12/4/12 7:50 AM, "Erik de Bruin" <erik@ixsoftware.nl> 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
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl