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: local policy)
Message-ID: <20121115115341.890344hsdamu6jh1@www.teotigraphix.com>
Date: Thu, 15 Nov 2012 11:53:41 -0500
From: Michael Schmalle <apache@teotigraphix.com>
To: flex-dev@incubator.apache.org
Subject: Re: How to prepare Apache Flex 5 to run in the new AVM in
 Flashplayer 12?
References: <7698DA69-C4BB-4A1F-8200-ED497EB422DE@gmail.com>
 <CALorpXdb_YLVHCoW2+AxAf93t8RE-BLkRrfUGe3OGSjvU9CO7g@mail.gmail.com>
 <CAMFKFRhJ+hb0kb60Ws8hDhPbKWF66weUn0-A3buD31wf8Yk8mA@mail.gmail.com>
 <CALorpXe0FrMq9=ev_nG+Wf1Z-aBz4VBy7OKJdPk4HMx5EzeNiw@mail.gmail.com>
 <CAMFKFRj2c0ciNMPKXGqhq-RvZ6kAH1k3JXkfDNZgiN5NwoQvHw@mail.gmail.com>
 <SNT002-W14258552C8BB98BCCF86CF982520@phx.gbl>
 <CANnZrXyr+JYU6rQyEzgnmZZo_Bpo3zWEGv=ErsOv79xwJRZM5Q@mail.gmail.com>
 <CACWtOtV58XO4NYJeKQJi2t-a=VetzKZp_k7n3MpCHZ=NQUO+wg@mail.gmail.com>
 <CAEFz_vs7Jh6r4Dd7=xjvwnn4Ru=Arrt-ar_NvCkqWrFxX4weEQ@mail.gmail.com>
In-Reply-To: 
 <CAEFz_vs7Jh6r4Dd7=xjvwnn4Ru=Arrt-ar_NvCkqWrFxX4weEQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=ISO-8859-1;
 DelSp="Yes";
 format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.11)

Quoting Omar Gonzalez <omarg.developer@gmail.com>:

> On Thu, Nov 15, 2012 at 8:32 AM, Nick Tsitlakidis  
> <nickt@perfectedz.com>wrote:
>
>> Carlos is suggesting a very nice way to solve all problems. But my opinion
>> is that a total rewrite needs A LOT of time and planning and at this the
>> most active people in the list are too few to handle something like this
>> and the others (less active) are just getting their feet wet.
>>
>> I think there is a long road and community engagement to reach a level
>> where a total rewrite in another version of AS can happen.
>>
>> So the question is what happens with the current codebase while the project
>> advances to reach that level.
>>
>>
> My guess would be nothing happens to the current codebase. We keep fixing
> bugs. AVM2 isn't going anywhere. Just because there's a shiny new toy
> doesn't mean they'll break thousands if not millions of apps because they
> have a new shiny VM.
>
> -omar
>

That being said, wouldn't it be advantageous to think about APIs that  
could stand the test of major refactors and start migrating or add  
extensions to the current code base that would give developers the  
option to start moving towards the next framework?

I mean, a public API is just that, what goes on under the surface is  
for the low level developers to think about and implement.

So you have Flex 5 that starts to really use this new API that maybe  
uses some adapters to fit some popular components under the API while  
creating more modular revisions at the same time.

I think some type of simultaneous refactor is possible giving the  
amount of brains around here.

Mike

-- 
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com