incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Wasilewski <>
Subject Re: [FalconJS] concepts
Date Wed, 28 Nov 2012 20:31:30 GMT
Good point, I will try to add HaXe output to this test as well. But as 
far as I can tell.
It was the best JS output out there but had some fundamental issues with 
namespaces represented by object chain. I was playing around it a while ago.


On 11/28/2012 8:26 PM, Markus Gritsch wrote:
> Hi everyone,
> Maybe someone can clarify the difference between haxe`s - as3-2-js output target and
falcon-js. Both are producing js code. Haxe supports a collection of multiple output formats,
too. Maybe the solution everyone is talking about is already out there - have???
> Thanks for your input
> On Nov 28, 2012, at 9:04 PM, Alex Harui wrote:
>> On 11/28/12 12:01 PM, "Daniel Wasilewski" <> wrote:
>>> Ok will try again by changing a subject because you seems to moved away
>>> from original topic, and I don't want to interrupt :)
>>> So far I have a test to compare very simple model of prototypal
>>> inheritance and proposed module pattern that seems to be out of falconJS
>>> compiler little syntactic sugar.
>>> I have minimised this source a bit, there was few more additional fields
>>> that I guess something is depends on but even striping it out:
>>> If you go to the revision 2 of this test, there will be different
>>> comparison.
>>> Speed of accession of those objects.
>>> However I would like to improve it, because adobe.js implementation
>>> doesn't seems to call super as the classic does.
>>> So it might be not relevant test right now. Does anybody know how to
>>> call super from there?
>> It looks like in adobe.js around line 61 it tests to see if the super class
>> has the function and creates a _super function you can call.
>> -- 
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.

View raw message