flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [FalconJx] where I'm going to be
Date Fri, 18 Jan 2013 18:09:09 GMT

On 1/18/13 3:24 AM, "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?
Your AS3 project uses Flash APIs for its visuals. There are folks who think
we can emulate the Flash APIs well enough to render an app in the browser
DOM, but I think that's a lot of work, which is why I have proposed and
prototyped an alternative of using parallel frameworks and require that you
have good separation of views from other logic.  See:

> - I have a Flex project with MXML, can it run in the browser with FalconJx
> instead of Flash Player?
Your Flex project not only uses Flash APIs it also uses the Flex SDK APIs.
The Flex SDK is not written in a way the easily runs in a browser without
Flash.   It might be possible to make that happens someday, but my vision is
to create a new SDK that is better designed to work in both Flash and the
browser.  It will feel like Flex but have some API and pattern differences.
My personal goal is to be able to eventually do about 80% of what Flex does
today over the next few years.

> - 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?
Even new JS-based RIAs have to deal with the pages paradigm.  Flex's
BrowserManager uses the same technique many JS-based RIAs do.  We will be
adding similar support to the ASJS framework.  At least in the early
versions, I expect that you will not do DOM manipulation directly:
everything will have to go through the new framework, so you won't be able
to do "everything", but that's generally a price you have to pay when
dealing with multiple targets.
> 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

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message