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: <20121115120435.586321wn81x0zmhv@www.teotigraphix.com>
Date: Thu, 15 Nov 2012 12:04:35 -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>
 <20121115115341.890344hsdamu6jh1@www.teotigraphix.com>
 <CAEFz_vuq+yPRX9TkZ3JRY3g+isUxgt6fF7OxRtzccO1pgZOD-g@mail.gmail.com>
In-Reply-To: 
 <CAEFz_vuq+yPRX9TkZ3JRY3g+isUxgt6fF7OxRtzccO1pgZOD-g@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)

Well, I didn't say it but what you wrote is exactly what I would have  
said if I didn't already have my rant points for this week used up.

I wrote the previous to show I can be diplomatic. ;-)

If you search the 100's of rants from me in the archives, I have  
always been saying burn baby burn.

Sometimes the phoenix needs to rise from the ashes, there is no ashes  
yet to rise form.

Mike

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

>>
>>
>> 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
>>
>>
> While that may work, the differences so far described in AS4 and the new VM
> sound so fundamentally different from what we have in AS3/AVM2 that I don't
> actually believe this would be possible. Based on rumors not even Starling
> is compatible, and the display list will pretty much be gone.
>
> I think it would probably be a complete waste of time to do that, but of
> course I may be wrong.
>
> I think the only way forward is to start with a brand new unit test suite,
> and build a new version of the Flex framework from the ground up, the right
> way. Modular and unit tested, such that it can grow from a small baby to a
> full grown application framework as we know it today. Trying to shoehorn
> the current base so it could possibly take advantage of some features of a
> new VM seems like a waste of effort.
>
> That said, anyone here is free to do what they want really. If it turns out
> well it'll likely be voted into a release. :)
>
> -omar
>

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