For me the whole point is that flashplayer renders the same in all platforms (mobile/web/desk) and that's the beauty for me.. I'm not gonna go deep on A vs B or A over B, I just wish there was a good solution for "avoid" flash player but keep code base.. That's why I thought that using stage3d as 2d (like starling) would be a solution for this problem, it would be easier to convert from stage3d to webgl, the work to be done is to mimic spark components, like Feathers did.
There is already work done 2 years ago! http://renaun.com/blog/2013/09/cross-compiling-your-actionscript-starling-games-to-webgl-and-javascript/ Regarding mobile would avoid installing adobe air (a lot of MB's on installer) and with cordova there would be a bridge for native capabilities. We could debug on flashplayer and deploy to html/js for web/mobile/desk/UWP At the end, flashplayer is like a html5 canvas with a framework behind rendering pixels.. For me the real challenge is to create from the ground some kind of starling, or work over starling to implement know flex capabilities. But with flexjs we are doing the "same" amount of work creating components that can be transpiled to html/js. Does anyone agree? 2015-11-06 2:10 GMT+00:00 lizhi <s...@qq.com>: > it can run foxfire,and my iphone5s. > > > > -- > View this message in context: > http://apache-flex-development.2333347.n4.nabble.com/a-stage3d-api-with-flexjs-tp49827p49855.html > Sent from the Apache Flex Development mailing list archive at Nabble.com. >
