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: <20121217132106.58923k2gvfnegzo2@franklin.liquidweb.com>
References: 
 <CAJs+wW0MGKxmBiUps83EXp=-iEepcwzvhH1XdAAq1S+1jaRM3w@mail.gmail.com>
	<20121217132106.58923k2gvfnegzo2@franklin.liquidweb.com>
Date: Mon, 17 Dec 2012 19:36:39 +0100
Message-ID: 
 <CAJs+wW1xsRS5YCv2r379FG3KWB4HbBRPD_atkazPXe=nAc1Dcw@mail.gmail.com>
Subject: Re: [FlexJS] Testing AS -> JS translation
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

Mike,

I try to talk about FalconJx, as I believe you call your "version" of
the AS -> JS compiler when I talk about your work. I refer to FlexJS
when I talk about the project to allow the user to write in an AS
based framework (either based on Alex's approach or a new one, based
on my experiences setting this up).

Am I correct in assuming that the FalconJx compiler will take any AS
files and translate it to JS using the rules we're working on in the
Wiki? I mean, I can build a framework in AS (like Alex's, or maybe
even use Flex itself) and build a complimentary framework in JS (like
Alex did) and as long as the functionalities of these frameworks
match, the user code can be put through FalconJx and the output should
run, correct? How about MXML?

EdB


On Mon, Dec 17, 2012 at 7:21 PM, Michael Schmalle
<apache@teotigraphix.com> wrote:
> That's a bit up in the air right now I think.
>
> The way I'm writing tests is AS -> JS google closure. But I'm right in the
> middle of refactoring the emitter classes.
>
> The tests I'm writing can be run from ant or whatever, just like the Falcon
> tests. I just haven't made a build file yet.
>
> Have you looked at the source code for FalconJx and it's tests?
>
> We don't want to duplicate work but I need to write these tests first. All I
> know is, once I get these emitters refactored, the JS output is going to be
> what the closure compiler wants. So we could just write an extension in the
> assertOut() method that maybe could tests with Jasmine as well? I don't know
> I have never used Jasmine testing.
>
> PS, my days with FalconJS are numbered, I've decided it's to complicated for
> what I see a relatively simple solution for just getting plain JS, so I
> probably won't be working on that code base at all, I think Alex is doing
> something with the code.
>
> Mike
>
>
> Quoting Erik de Bruin <erik@ixsoftware.nl>:
>
>> Hi,
>>
>> I'm trying to figure out how to build tests for the AS to JS cross
>> compilation.
>>
>> Should we write AS "strings" and have a script put those through the
>> FalconJS/FalconJx compiler and compare the result with a pre-defined
>> "intermediate JS" result? If so, what would be the best tool to write
>> those tests in? Ant? Shell script? Something else?
>>
>> I'll be writing the JS tests in Jasmine (mainly because that's what I
>> know), to test the result from putting the FalconJx output through the
>> Google Closure Compiler and later on the Closure Builder.
>>
>> Preferably we would be able to integrate both test suites, so we can
>> test AS -> "final JS" in one go.
>>
>> Thoughts?
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>>
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

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