Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of ncannasse@motion-twin.com
 designates 91.209.175.128 as permitted sender)
Message-ID: <4F45111C.6010104@motion-twin.com>
Date: Wed, 22 Feb 2012 17:00:28 +0100
From: Nicolas Cannasse <ncannasse@motion-twin.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: flex-dev@incubator.apache.org
Subject: Re: Flex adopting haXe ?
References: <4F44C4BF.4020904@motion-twin.com>
 <4F44D30C.7010101@leichtgewicht.at>
 <CAMFKFRjckRn4Z0E5zrA7FPD5SfXwhU8Th4ng0JCaMuMTkMFRmw@mail.gmail.com>
In-Reply-To: 
 <CAMFKFRjckRn4Z0E5zrA7FPD5SfXwhU8Th4ng0JCaMuMTkMFRmw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Le 22/02/2012 13:09, Carlos Rovira a �crit :
[...]
> Now haXe has evolved great and Apache Flex could go the haXe way to be a
> real open source framework that does not depend only in Adobe's runtime.
>
> The problems behind : This way is hard, but feasible, and take into account
> that principal actors using Flex nowadays are IT departments of huge
> organizations and enterprise customers that need a viable migration path to
> all applications deployed until now.
>
> We must to take into account, that Flex is MXML and AS3 right now. People
> that wants to move from adobe flex sdk latest sdk (4.6) to apache flex,
> need a migration path that could be done with more or less pain. If we
> chage in a radical manner and adobe sdk and apache flex sdks is radicaly
> different, we could loose in the process lots of users.

Hi Carlos, long time no talk ;)

While not being myself a Flex user, I definitely understand your point 
here. Things needs to be done carefully, and you need a plan for that.

However it's not like all flex users will have to switch to haXe either. 
Rewriting Flex in haXe would allow people to use haXe, and I guess you 
would also need it to target JS/HTML5, but you could also give AS3 users 
a precompiled SWC that would work exactly the same for them as if if was 
written in AS3.

Looks like a migration plan does it ?

Best,
Nicolas