RE: hit testing and retained graphics

Hi Cameron,

Flash uses retained-mode graphics. But I would add that, in the cases where the issue of accessibility arises, canvas objects are effectively retained: that is to say, they represent objects which are at some point abstracted from strictly a set of vectors. While this doesn't represent the majority of canvas applications to date, the logical conclusion of anything related to drawing pixels on a screen is that frameworks will be built around certain use cases, and that necessarily means that APIs will emerge that make the difference between the modes irrelevant. Bespin is the most obvious example of this emergence. Some developers will inevitably build programmatic objects that occasionally stop to draw new pixels on the screen. Some of them may even have good reason to (say, the fact that the browser in Android 2.x supports canvas but not SVG). For this use case, what Rich has proposed would certainly fit the bill.

-
m

-----Original Message-----
From: Cameron McCormack [mailto:cam@mcc.id.au] 
Sent: Wednesday, June 29, 2011 4:40 PM
To: Matt May
Cc: Silvia Pfeiffer; Richard Schwerdtfeger; Charles McCathieNevile; Charles Pritchard; Cynthia Shelly; david.bolter@gmail.com; Frank.olivier@microsoft.com; Tab Atkins Jr.; Mike@w3.org; public-canvas-api@w3.org; public-html@w3.org; public-html-a11y@w3.org
Subject: Re: hit testing and retained graphics

I am not familiar with Flash programming.  When you talk about shapes
being drawn on the Flash stage (or canvas), is that a retained mode or
immediate mode API?  If it’s an immediate mode API, would you be able to
compare it to the proposal being made here?

-- 
Cameron McCormack ≝ http://mcc.id.au/

Received on Thursday, 30 June 2011 00:58:32 UTC