Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Date: Tue, 4 Dec 2012 16:50:19 +0100
Message-ID: 
 <CAJs+wW0gyv0tk2hJP7CepLzLP-35Y=Cn+tuQ+oV2oSvHZS=o3A@mail.gmail.com>
Subject: [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

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