flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédéric THOMAS <webdoubl...@hotmail.com>
Subject Re: [FalconJx] where I'm going to be
Date Fri, 18 Jan 2013 15:20:35 GMT

Yes, that's a clear introduction of what it aims to and it was important to 
clarify that.

On the wiki page, l would like to understand little bit more, even if maybe, 
not sure, I can figure out what is a javascript target, AST walker, 
JavaScript emitter and node switch strategy, it would be nice if it would be 


-----Message d'origine----- 
From: Michael Schmalle
Sent: Friday, January 18, 2013 4:03 PM
To: dev@flex.apache.org
Subject: Re: [FalconJx] where I'm going to be


When I wrote that I was basically brainstorming and talking to myself.

Since it's in the trunk now, it does require a more laymans
explanation which I will work on.

Really, here is the Overview.

"FalconJx is being designed to be able to compile ActionScript3 source
code business logic to JavaScript business logic. At the moment, there
are no plans for the "majic bullet" compile to SWF and Browser with
the same view code."

When I say business logic, I mean, no views, no ui components, no
flash display list to javascript DOM conversations. Just business logic.

My main intention is not to "bloat" the project's definition with over
expectations like what happened in the definition of FalconJS.

I just want to be able to write OOP type strict code in AS3 and
compile it to JavaScript at the moment.


Quoting Frédéric THOMAS <webdoublefx@hotmail.com>:

> Mike,
> Q: How does it work?
> A: Basically we are utilizing the fantastic AST IASNode structure, 
> traversing the nodes and visiting them individually with an emitter.  The 
> difference here is the AST walker is a hand written  implementation that 
> can easily be maintained and optimized per  individual specs.
> I've been lost right after the word "Basically", as many people who  never 
> did anything regarding compilers but compiling, there are some  words that 
> hurts :) that's the reason why I said  "introduction/overview " meaning 
> something more basic that could  help to understand what is written on the 
> wiki page.
> -Fred
> -----Message d'origine----- From: Michael Schmalle
> Sent: Friday, January 18, 2013 3:38 PM
> To: dev@flex.apache.org
> Subject: Re: [FalconJx] where I'm going to be
> I outlined some of this a while ago;
> https://cwiki.apache.org/confluence/display/FLEX/FalconJx+Prototype
> Mike
> Quoting Frédéric THOMAS <webdoublefx@hotmail.com>:
>> Yes, you right Carol, this information is very helpful and even  more 
>> that, a good introduction/overview of how it works, what's the  AST, 
>> ..., would be also welcomed I guess.
>> -Fred
>> -----Message d'origine----- From: Carol Frampton
>> Sent: Friday, January 18, 2013 3:30 PM
>> To: dev@flex.apache.org
>> Subject: Re: [FalconJx] where I'm going to be
>> This would be good info to post somewhere on the website since I'm sure
>> Frederic isn't the only one wondering.
>> Carol
>> On 1/18/13 6 :41AM, "Erik de Bruin" <erik@ixsoftware.nl> wrote:
>>> Frederic,
>>> There are currently two JS cross compilation projects happening:
>>> FalconJS and FalconJx.
>>> FalconJS is a project started by Alex Harui. It is currently the most
>>> complete implementation and has (limited?) MXML parsing. The FalconJS
>>> compiler will take an MXML and AS project and output a valid HTML/JS
>>> application. FalconJS does depend on a custom AS framework (i.e. won't
>>> work with the Flex SDK) and corresponding JS framework. This framework
>>> goes by the name of FlexJS. Read more about it on the Wiki:
>>> https://cwiki.apache.org/confluence/display/FLEX/Alex%27s+FlexJS+Prototype
>>> FalconJx is the 'alternative' project from Michael Schmalle. It uses
>>> an alternative approach to AS3 compilation (don't ask for details, I
>>> have no clue about the innards of that code). One of it's main selling
>>> points (from my humble point of view) is that it has a very flexible
>>> architecture for outputting different flavours of JS. The status of
>>> this project is that we are working on getting complete AS3 language
>>> feature coverage in place. This means that we are working towards
>>> ~100% translation of AS into JS. I'm using the Google Closure Tools to
>>> augment standard JS to try and match the original AS language
>>> features. This is coming along nicely, but I'm sure the devil will be
>>> in the details. Read more on the 'goog' way here:
>>> https://cwiki.apache.org/confluence/display/FLEX/AS+to+JS+-+the+%27goog%27
>>> +Way
>>> FalconJx future: once we have AS (and hopefully MXML, at some point)
>>> translating into JS and have functional tests in place, the challenge
>>> will become to come up with both AS and JS framework to actually allow
>>> for application development. I'm silly enough to still cling to the
>>> idea that we'll be able to use (most of) the Flex SDK and create a
>>> compatible JS library... but I'm sure others will declare me insane
>>> for just dreaming about that :-)
>>> Have fun,
>>> EdB
>>> On Fri, Jan 18, 2013 at 12:24 PM, Fréderic Cox <coxfrederic@gmail.com>
>>> wrote:
>>>> I'm following your work with great interest, but I'm afraid as a
>>>> "regular"
>>>> AS3 developer with no background in compilers this is a bit too
>>>> technical
>>>> for me. I was wondering if you could explain in a non-technical way 
>>>> what
>>>> the status of the project is at this moment.
>>>> Questions I have:
>>>> - I have an AS3 project, what can I do with FalconJx? Will it run in 
>>>> the
>>>> browser already?
>>>> - I have a Flex project with MXML, can it run in the browser with
>>>> FalconJx
>>>> instead of Flash Player?
>>>> - Is it technically possible to write in AS3/MXML and without Flash run
>>>> the content in the browser, how does it reflect to the "pages" paradigm
>>>> (history) and the DOM?
>>>> Thanks for your hard work, just trying to understand where we are at at
>>>> this moment
>>>> Fréderic Cox
>>>> On 18/01/13 12:19, "Michael Schmalle" <apache@teotigraphix.com> wrote:
>>>>> Hey all,
>>>>> Since the project is really taking shape thanks to our great
>>>>> cooperation, I am going to focus on the nemesis I have left and that
>>>>> is finishing of the ActionScript emitter.
>>>>> This project blew up fast with Erik contributing, I didn't get a
>>>>> chance to fully finish the ActionScript impl. Yes, I might have plans
>>>>> down the road to make a read/write AS DOM and having a fully
>>>>> functional AS3 emitter is essential.
>>>>> Mike
>>>>> --
>>>>> 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
> -- 
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com

Michael Schmalle - Teoti Graphix, LLC

View raw message