On 8/30/12 8:04 PM, "Jonathan Hart" <jonathan.h...@gmail.com> wrote:
> I think I'm beginning to recognize a larger confusion in this
> discussion which should be brought to the table. Many people consider
> AS3 to be a scripting subset of Flex, which is simply not the case.
>
> With AS3 comes the display list framework upon which Flash and Flex
> are built.. there's that problem to solve.
>
> Then, there is the intricacies of advanced display concepts that are
> part of both Flash and Flex, such as filters, animations, etc. There
> are several new problems just within that.
>
> There are also other things such as multimedia (camera, sound, local
> storage, etc). What happens there? Now you're venturing into browser
> specific territory and if it even supports that.
>
> It's simply too much ground to cover. There comes a time when one who
> is trying to make a "Cross-Compiler" (and at this point, I use that
> term as loosely as possible), has to recognize the vastness of the
> challenges, makes concessions, and refocuses their efforts on
> something that is achievable as an acceptable level of quality.
>
> So, that said, what use cases of Flex (and at the lower level, Flash)
> is FalconJS expected to cover?
I don't think that's been decided or needs to be at this moment. We will
get the code in and folks can play with it and discuss what to do next and
even take more than one approach.
>
> Determining the use cases and discussing how possible it is for
> browsers to complete that coverage is a more focused conversation. I'm
> beginning to think that FalconJS deserves its own mailing list ;)
FalconJS might get its own sub-project if it turns out there is a distinct
set of folks working on it.
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
