I just want to say there's no need to redesign Flex framework, Spark skinning, two way bindings and Mxml interface are not only still on the cutting edge but also need more time to be really adapted, what need to change is the implementation, Flex has too many legacy code to maintain back compatibilities, if Flex can give rid of Flex 2,3 code, it will be more efficient and easy to use. -Gary
On Wed, Jul 10, 2013 at 2:02 PM, DarkStone <darkst...@163.com> wrote: > Hi Carlos, > > The benefit of enabling Stage3D for Flex would be: > > 1. Much better performance on mobile devices. > > 2. Be able to develop Real 3D Apps and Games. > > 3. Making Flex the best cross platform native app developing SDK. > > In fact you can use Stage3D directly in Flex Applications, Stage3D layers > are below the Flex Application layer. But you can not take any advantages > of Flex like MXML, Bindings, FXG, CSS etc. Cuz the current Flex is not > design for the Stage3D kind of things. > > In order to enable full support of Stage3D for Flex, it requires redesign > Flex Framework from the ground up. Cuz Stage3D is about GPU rather than > CPU, and the GPU Programming is quite different than CPU, you need to > understand and deal with vertex, mesh, shader, texture, AGAL... > > However there are still some feasible ways to enable Stage3D for Flex, > here is one I thought of: > > Redesign the Flex Framework by building it on top of the Starling > Framework, this approach can reserve most of the Flex API names, for > example UIComponent Class, FlexSprite Class etc. They are still the same > class names and package names, but they need to extends the Starling Sprite > Class instead of the original one. And of course, a simple extends Starling > Sprite Class ain't gonna work, we will have to reimplement all of the > subclasses, yes it's hell. > > Anyway, unless someone can invest a million dollars on this, I don't think > full Stage3D support for Flex will become reality in these years, although > personally I want this so bad. > > > Sent from DarkStone's iPhone > > 在 2013-7-11，0:38，Carlos Rovira <carlosrov...@apache.org> 写道： > > > Hi, > > > > from time to time people comes with the desire to see Flex running on > > Stage3D. I would want to recopile all the state of the art info about > this > > topic and see if is possible and how much work it would require. > > > > I know people like J.Campos did two attempts and get valious research > from > > that experience. There's things to get into account like accessibility. > > > > Please could people share in this thread the things they know in order to > > recopile all info? Is there some things to take into account that could > > make Stage3D not possible for Flex? Could we overpass it and make it > > possible? If it would be possible...it will brings real benefits? > > > > If some work is done in this topic, I'd propose to make focused in this > > particular thing and unlike FlexJS, here I will not try to break > > UIComponent in small parts, or break compatibility. Even if it could be > > possible to have a global flag like "enableStage3D" to make our apps run > on > > Stage3D if is true or remain in normal display layer, it could be great. > > > > Thanks in advance for any insight regarding this topic. > > > > Best > > > > Carlos > > > >
