incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Rovira <carlos.rov...@codeoscopic.com>
Subject Re: Flex 5 in haxe
Date Tue, 20 Nov 2012 20:53:10 GMT
Hi Kevin,

all depends of how things evolve but I must say that my propossal (and my
contribution if someday get materialized in code) about Haxe is base the
API in current Flex 4.x as a starting point (a draft), but modeling and
changing it as project evolve. This project is for fun, at least in its
conception, and taking into account that it will be done in spare time, I
would not try even to plan any migration or compatibility with old Flex
applications to that FlexHaxe thing. We should copy the right things and
rethink the old or bad ones. For people that wants to continue the current
path (Flex 4.x) always will be maintenance a new features/patches in that
"Flex line". Apache Flex count we members involved in such different ways,
what's very cool to get both things done. A new Flex framework should be
new and free from any ties from the pass.


2012/11/20 Kevin Newman <CaptainN@unfocus.com>

> HaXe really is more similar to AS3 than many here seem to think (it's more
> of a superset than a subset - though there are some missing features like
> namespace). Would Flex really need to start from scratch when porting to
> HaXe? Could some level of automation be utilized (there's an unfinished
> tool that could be picked up and worked on for doing just that)?
>
> The biggest problem with a change in platform has more to do legacy
> support.
>
> What do you do with all that AS3 code? If Flex is written in HaXe, and you
> still target Flash/AIR platform, you can still rely on the old AS3 compiler
> to leverage all that legacy SWC and AS3 code. HaXe in this migration path
> doesn't require dumping legacy code at all. Win/win. Flex migration could
> even be modularized, because of this. I wonder if a small proof of concept
> could be attempted - convert some core Flex components to HaXe, compile to
> SWC, and leave the rest in AS3, and see how that goes.
>
> A benefit of the switch, of course, is HaXe allows movement to many
> platforms other than ABC/Flash/AIR - including open stacks such as NME,
> Neko and HTML5.
>
> In short HaXe nets Flex a lot. Legacy code base support through Flash/AIR,
> support for completely open stack(s) for apps, and HTML5 support. This is
> the power of open source.
>
> HaXe Foundation:
> http://haxe-foundation.org/
>
> Kevin N.
>
>
> On 11/16/12 3:58 PM, Gordon Smith wrote:
>
>> The silliest of the bunch in my opinion is porting to HaXe or starting
>> from scratch.
>>
>
>


-- 
Carlos Rovira
Director de TecnologĂ­a
M: +34 607 22 60 05
F:  +34 912 35 57 77
http://www.codeoscopic.com
http://www.directwriter.es
http://www.avant2.es

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message