I think it's apparent that you've done a lot of work here, and your approach has merit.
Like Mike says, keeping an open discussion here, would be a good thing. Personally, I have not done much mobile work, but that will likely change in the near future. So until then I don't have much to comment on... On Jan 21, 2013, at 1:30 PM, Daniel Freeman wrote: > I've done some experiments with Stage3D accelerated Flex components, > derived from MadComponents classes. > > http://madskool.wordpress.com/2013/01/21/madcomponents3d-part5-stage3d-accelerated-flex/ > > It is my intention to port MadComponents to AS"next". I propose that these > ported MadComponents/MC3D classes might form the basis of a new Flex mobile > framework that utilises hardware GPU rendering. > > I'm aware that Thibault Imbert has proposed that a new Flex framework > should be based on Starling and Feathers. But I believe that the MC3D > approach is better suited to the next Flex mobile framework. > > MadComponents is a fully fledged framework, not just a UI framework. It > allows for versatile styling of components (without having to design > texture skins), server communication, and memory management. > > However, until we know more about AS"next", which framework approach to > choose is mostly speculation. > > So I'd like the members of this group to read my blog post, and let me know > what they think.
