On 11/28/12 11:21 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>>> Are we ready to put the framework.js in the FalconJS develop branch so
>>> we can all work on it?
>> IMO, framework.js shouldn't be in the FalconJS branch. It is as independent
>> of FalconJS as any of the AS code is independent of Falcon.
>>
>> I would refactor framework.js into separate js files so we don't step on
>> each others toes and put it somewhere else in SVN and start adding to it and
>> the .AS files. We could start by having folks just work in my whiteboard or
>> we can create a new whiteboard folder not under my name if that makes folks
>> more comfortable. I was going to branch what I have checked in for further
>> modifications so what I checked in stays running.
>
> Might I suggest a 'as2js' in the root of the repo, with branches, tags
> and trunk. In trunk (and/or branches/develop?) I would have an 'as'
> and a 'js' folder, and within each of those a 'src' and 'srcTest'...
> But that's just of the top of my head, so I'm open to suggestions ;-)
Yeah, let's sit on this until tomorrow in case we get other suggestions on
this topic.
>
>>> Another question: for your prototype you modified/bypassed parts of
>>> the SDK, it looks like. Does this mean that you envision 2 versions of
>>> the SDK, one for Flash Player deployment and one for web native
>>> deployment?
>> I'm not sure what you mean here. For this new effort, I am not using Apache
>> Flex 4.8 at all and have no plans to. This is a next-generation and a full
>> rewrite with different goals. What it has in common with Flex is MXML and
>> AS3 and many but not all APIs. The idea is that for every component you
>> write in AS, you have to create its equivalent in JS. You might be able to
>> get FalconJS to help you create parts of the JS equivalent, but the parts
>> that touch the visuals pretty much have to be written differently.
>
> This was the missing link in my understanding. We're writing a new
> SDK, fresh components on both sides of the FalconJS compiler.
Yep, IMO the current code is too hard to port to JS. It has expectations on
AS features that will be hard or expensive to implement in JS, and some
fundamental APIs like addChild need to change to better deal with the
abstraction.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
