flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: Entering FlexJS - FalconJX
Date Tue, 30 Apr 2013 05:18:54 GMT



On 4/29/13 5:47 PM, "Alex Harui" <aharui@adobe.com> wrote:

> 
> 
> 
> On 4/29/13 4:52 PM, "Carlos Rovira" <carlos.rovira@codeoscopic.com> wrote:
> 
>> Hi,
>> 
>> I'm entering this days FlexJS - FalconJX and trying to make some
>> contributions as I learn all the work done until date. I think there's very
>> good ideas in the AS framework like the IStrand-IBead approach or the MXML
>> data structure vs AS3 old generation. Really very cool and I see here lots
>> of fun and hope to be able to have the time and skills to make some
>> contribution along the way.
>> 
>> For the moment I shared, just few minutes ago, a createjs checkbox control
>> implementation while I'm familiarizing with all the pieces, but I would
>> love to contribute with other things like containers, layouts, or a state
>> implementation as time and skills allow.
>> 
>> Now some questions since although I'm coding and compiling I already have
>> some problems:
>> 
>> 1.- In the createjs example, the SWF compilation does not run for me. It
>> shows the folowing RTE at launch:
>> 
>> TypeError: Error #1034: Error de conversión forzada: no se puede convertir
>> flash.events::Event@1088d4f29 en org.apache.flex.events.Event.
>> 
>> 
>> is this normal?
> That sounds like a bug.  Hopefully Peter can look at in tomorrow.
>> 
More information if you want to look into it yourself.  The goal for FlexJS
is to not dispatch any flash.events.Events and other Flash low-level events.
Instead, we're wrapping all events in org.apache.flex.events.Event.  This
allows the developer to see where they import flash.events.Event in their
code and know that those areas need to change.

The AS-side in FlexJS does consume and dispatch flash.events.Event because
it has to wherever it touches the Player APIs.  It just isn't supposed to
dispatch any as documented events in the API.

So, this sort of bug happens when FlexJS dispatches a flash.events.Event
that it didn't wrap, or the player dispatched something that we didn't trap
first.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


Mime
View raw message