incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Schmalle <>
Subject Re: [FalconJS] concepts
Date Thu, 29 Nov 2012 00:06:59 GMT


This is the exact pattern I was talking about implementing. I think  
it's so solid and you have done a great job at implementing it.

As I have said in previous posts today, The way FalconJS digests it's  
AST is through SWF visitors. You are using straight AST from your  

Folks, having Frank drop this line and the discussions going on at the  
moment, there are definitely a couple different paths that can be  
taken with producing javascript.

If I have my way we would use an implementation like Franks, the  
problem with it as it stands in Apache is there is no infrastructure  
built like Frank has built, this is why the engineers used an SWF to  
represent that infrastructure.

The problem with the current SWF/JBurg implementation is it VERY  
confusing for most developers. With Franks implementation I was able  
to understand what he was doing today within 20 minutes and could jump  
right in and start coding things. With the current FalconJS emitters  
there is no way that would happen.

So, I would love to see if we could think about a common goal to  
energize both projects and see where one could help the other. I truly  
believe now by looking at the code BEFORE this post our projects have  
the exact same goal but can do different things.


Quoting Frank Wienberg <>:

> Hi folks,
> here is another "outsider" who would like to contribute to the JS runtime
> format, if you are interested.
> I am co-founder of the Open Source project Jangaroo, and as such have been
> dealing with JavaScript-to-ActionScript-3 compilation for several years now.
> In response to Bernd Paradies blogging about FalconJS, I blogged about
> "simulating ActionScript 3 language features" extensively:
>    -
>    -
>    -
>    -
> All described solutions are actually implemented in the Jangaroo Runtime,
> which takes care of the code translated from AS3 to JS by the Jangaroo
> Compiler coming alive.
> In principle, we follow the "classic route", with the exception of how we
> simulate private members: see the first two blog posts.
> At first look the Jangaroo Runtime may seem overly complex to you, but it
> does many more things (class loading / dependency management; class
> initialization = execute static code at the right time; allow keeping
> generated JS code and source AS3 code as similar as possible; automatic
> method binding / correct "this", etc.), and the concepts described in the
> blob posts also work without these additional features.
> The Jangaroo Compiler is written in Java and has a separate code generator
> (well you obviously won't need the parser) which might be worth having a
> look at:
> If you dare to use Maven ;-), it is really easy to play around with our
> code generation: Just set up your own projects within minutes, starting
> from an example project like
> or
> .
> Greetings,
> -Frank-
> Frank Wienberg
> Software Architect & Jangaroo Evangelist
> **
> * frank@jangaroo <>.net*
> CoreMedia AG
> content | context | conversion
> Ludwig-Erhard-Str. 18
> 20459 Hamburg, Germany
> Executive Board: Gerrit Kolb (CEO), Dr. Klemens Kleiminger (CFO)
> Supervisory Board: Prof. Dr. Florian Matthes (Chairman)
> Trade Register: Amtsgericht Hamburg, HR B 76277
> --------------------------------------------------------

Michael Schmalle - Teoti Graphix, LLC

View raw message