If the need for GPU assistance is during scrolling and transitions, that's a different problem. Building a capability into a single framework where you can grab bitmaps from the display list, hide the display list, use the GPU to render a really slick animation, and bring the modified display list right back on top of the final results might be a better way to get the best of both worlds.
Alex, This is exactly what I'm thinking, this may be the perfect approach. Thanks for that idea. Does anyone have any input on how we can start to collaborate on the development of this idea? If anyone here uses IRC, I'm always in #actionscript on irc.efnet.org On Thu, Jan 26, 2012 at 2:57 PM, David Francis Buhler <[email protected] > wrote: > I have now seen it. > > On Thu, Jan 26, 2012 at 2:25 PM, Alex Harui <[email protected]> wrote: > > > >> -----Original Message----- > >> From: David Francis Buhler [mailto:[email protected]] > >> Sent: Thursday, January 26, 2012 11:11 AM > >> To: [email protected] > >> Subject: Re: Pushing Flex components thorough the GPU > >> > >> The only information I can find, regarding platforms for Flex and > >> Accessibility always routes me to: > >> http://www.adobe.com/accessibility/products/flex/jaws.html > >> > >> List of Accessible Flex components (this is probably out of date) > >> http://www.adobe.com/accessibility/products/flex/components.html > >> > >> Impaired users need to standardize on a platform, which is why I > >> believe the stack is narrow, and very well defined. If there's an > >> open-standard for Screen-Readers, for example, I have not seen it. > > > > See [1] > > > > [1] http://www.w3.org/WAI/intro/aria > > > > > > > > Alex Harui > > Flex SDK Developer > > Adobe Systems Inc. > > Blog: http://blogs.adobe.com/aharui > > > -- Francis Altomare,
