Gecko:Layers: Difference between revisions

Jump to navigation Jump to search
Line 18: Line 18:


* Should have an efficient software fallback
* Should have an efficient software fallback
** In particular, should be able to be implemented as mostly immediate-mode, with minimal temporary buffers
* Cross-platform API
* Cross-platform API
* Don't make clients implement multiple rendering code paths
* Don't make clients implement multiple rendering code paths
Line 23: Line 24:
* Be able to use platform layer APIs (e.g. Core Animation) if we get backed into a corner with undocumented interfaces?
* Be able to use platform layer APIs (e.g. Core Animation) if we get backed into a corner with undocumented interfaces?
* Support VRAM management; we'd like to be able to discard buffers and re-render them when VRAM is full, including with fine granularity via a tile cache
* Support VRAM management; we'd like to be able to discard buffers and re-render them when VRAM is full, including with fine granularity via a tile cache
* Support subpixel-AA of text rendered onto an opaque background


= Open questions =
= Open questions =
1,295

edits

Navigation menu