On 11/21/12 2:19 PM, "Daniel Wasilewski" <devudes...@gmail.com> wrote:
> There was a lot of talks here about approach to be taken to bring Flex
> to the next level.
> One of them was the fact that in order to target multiple platforms you
> need to have a descent compiler to convert AST into native language.
> That requires a lot of work and effort.
We will be seeing the FalconJS code in Apache shortly. I don't know how
much work it was, but it only 40 files or so.
> Nobody here familiar with a
> scale of effort that needs to be put into such project have confidence
> it can be done in reasonable amount of time and resources due to lots of
> platform inconsistencies and the fact, that some of the platform
> specific languages and features just missing.
My goal is to avoid using things that are hard to implement in other
platforms, at least in the early versions.
>
> I took a different approach. Instead of relying on generic compiler, my
> goal is to implement a framework with a consistent set of rules, in
> native languages and platforms.
> Feel a gap in missing feature territory and encapsulate it in one place.
> On top of that very abstract scripting language can be developed as well.
For me, AS3 is the key factor. If you make folks learn a new language, it
makes their set of choices much wider.
> If I will see Flex going in that direction, leverage the best practices
> of the target platforms instead to try to be a Swiss knife, I would be
> happy to share my vision in details and contribute to the project. But
> most of all, did you consider or discussed that very option well enough?
I didn't, but I have my plan and hope to show to folks next week.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
