Didn't they do away with GPU mode this past year? I think you need to use Stage3D…
On Mar 20, 2013, at 6:15 PM, jude wrote: > On Tue, Mar 19, 2013 at 8:08 PM, Om <bigosma...@gmail.com> wrote: >> >> >> Please go on with the rambling :-) Its nice to know that others are >> thinking about things I am thinking as well - and that I am crazy! >> >> BTW, I have a nice little carefully crafted XSLT that converts a basic FXG >> node with just the Rect element to SVG. I am planning on tackling the >> 'fill' element next. Once I have a decently working XSLT that simply >> converts an FXG skin that can be directly rendered on a browser, I will >> start posting my work for others to look at at hopefully, contribute. >> > > Cool. :) I was reading a post yesterday about the massive performance > improvements by rasterizing the vectors and then moving them to the GPU, > http://goo.gl/WXkmA. I haven't seen this approach before and it may not > have been possible before but with Stage 3d, Starling and WebGL it now is a > choice. And if that works then we may be able to apply it to the Flex SDK > and even HTML output (it renders at difference sizing so as you zoom in or > out it maintains fidelity - I think). > > Someone mentioned in the comments on a recent post that if we replaced > DisplayObject type with IDisplayObject we could use our own renderers. We > could then have in our Flex applications something like a > stageRenderer:IRenderer property / interface. > > Really, if we get this to work and apps run as silky smooth as games do > then it will put Flex / AIR on the map for apps.
