[Webkit-unassigned] [Bug 44926] Multiple accelerated 2D canvases should be able to use the same GraphicsContext3D
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Aug 31 15:32:30 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=44926
--- Comment #17 from James Robinson <jamesr at chromium.org> 2010-08-31 15:32:29 PST ---
Thanks for looking through this patch. I'll do my best to address all the line-by-line comments.
The point you make about the FBO treatment is a valid one, Chris. We'll also want to generalize this in order to support multisampling. Here's what I propose to make this more general:
1.) No new functions on GraphicsContext3D
2.) CanvasFramebuffer adopts a more general interface to look something like:
create(SharedContext3D*, IntSize)
bind()
publishToPlatformLayer(PlatformLayer*)
publishToTexture(unsigned)
and not expose any specifics about what the FBO binds to. Then implementations can bind a CanvasFramebuffer to either a color texture or a RenderBuffer and deal with the details of how to expose the rendering results to either a PlatformLayer (for compositing) or a texture (to draw the rendering results in another canvas). The specifics of allocating a compositing target (texture, CALayer, etc) and doing the copy/blit/resolve will be handled by each platform.
Follow up incoming.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list