Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of sebpatu.flex@gmail.com
 designates 209.85.214.47 as permitted sender)
Message-ID: <50A64FAA.3040407@gmail.com>
Date: Fri, 16 Nov 2012 15:37:30 +0100
From: =?ISO-8859-1?Q?s=E9bastien_Paturel?= <sebpatu.flex@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: flex-dev@incubator.apache.org
Subject: Re: [POLL] - Must Flex 5 be a complete rewrite or can flex code base
 be re-architecture?
References: <50A63661.9010508@gmail.com>
 <0E7CF6486AC44249B0B674C6760449B403D3D60C@mcusquanez26v.mcdsus.mcds.usmc.mil>
 <50A6458D.90106@gmail.com>
 <0E7CF6486AC44249B0B674C6760449B403D3D65F@mcusquanez26v.mcdsus.mcds.usmc.mil>
In-Reply-To: 
 <0E7CF6486AC44249B0B674C6760449B403D3D65F@mcusquanez26v.mcdsus.mcds.usmc.mil>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

If you find the magic solution fine :)
But let me doubt of such a magic solution, when i see that Adobe did 
tried this path.  When FalconJS is only prototype and far to be 
efficient. When Haxe made some changes to AS3 especially to be able to 
compile efficiently to many targets.


Le 16/11/2012 15:07, Kessler CTR Mark J a �crit :
> I would say it's possible given how it's compiled.  So having a robust compiler or different compilers for different target environments could be possible.
>
> -----Original Message-----
> From: s�bastien Paturel [mailto:sebpatu.flex@gmail.com]
> Sent: Friday, November 16, 2012 8:54
> To: flex-dev@incubator.apache.org
> Subject: Re: [POLL] - Must Flex 5 be a complete rewrite or can flex code base be re-architecture?
>
> "Having more deployed targets based on what we have currently"
> But is it possible? thats the question...
>
> Le 16/11/2012 14:50, Kessler CTR Mark J a �crit :
>> Option 2 ... +1
>>
>>      I would think the community is already based around the current framework.  Having more deployed targets based on what we have currently sounds like a way to broaden our target audience.
>>
>>      How about we continue to correct and fix the current Flex framework.  Could we start a new namespace that we could use to build up a partial new framework for a future transition to?  It just feels like rewriting everything from scratch would take a long time and would basically be a separate project.
>>
>>      I'm also envisioning the amount of work the developers using Flex will have to go through to convert to a completely new framework.
>>
>> -Mark
>>