While webgl is really cool, getting rendering consistent between browsers is really challenging to say the least. This example renders very nicely in Chrome, but Firefox messes up the display (both of the colors and the rotation), and Safari would not even load it at all.
I think it would be really great to have a webgl output option, but I don’t think all efforts should go that way. Most web apps do not have enough complex rendering to require webgl. Classic DOM still makes a lot of sense in a lot of cases. Harbs On Nov 5, 2015, at 12:47 PM, Dev LFM <developer...@gmail.com> wrote: > I really think this is the way to go.. all efforts should be on converting > displayobjects architecture (like starling did) to stage3d (I think they > gave it to away3d), and then yes like this matrix3d to flexjs/webgl. Then > we could all work on top of Feathers to improve even more, because > stage3d/webgl is the most "native feeling" you can get. > > Does anyone knows what away3d did with the starling port? > > Well done lizhi +1 > > 2015-11-05 8:24 GMT+00:00 Harbs <harbs.li...@gmail.com>: > >> Very nice! >> >> On Nov 5, 2015, at 8:50 AM, lizhi <s...@qq.com> wrote: >> >>> >> https://github.com/matrix3d/FlashShader/blob/master/flexjs5/src/TestStage3D.as >>> >>> http://matrix3d.github.io/assets/html5/flexjswebgl >>> >>> >>> >>> -- >>> View this message in context: >> http://apache-flex-development.2333347.n4.nabble.com/a-stage3d-api-with-flexjs-tp49827.html >>> Sent from the Apache Flex Development mailing list archive at Nabble.com. >> >>
