FutureGfxWhiteboard

From MozillaWiki
Revision as of 05:45, 24 August 2005 by Pavlov (talk | contribs)
Jump to navigation Jump to search

These are roughly in the order in which they should be done, although much can be done in parallel.

Rendering performance tests

Need to create Trender performance tests for tinderboxes.

Implement Gtk2 Native Themes With Cairo

Native theme support works well on Windows.

Fix complex clipping

Clipping in cairo is busted on windows.

Complex clip areas (areas which are not the union of a set of device-pixel-aligned rectangles) do not perform well and create fringing artifacts. We can fix this by using an intermediate surface to perform clipping, but it would be better done inside cairo.

Thebes font work

Need to add the new Thebes font/text APIs. TextRun glyph caching, etc. New Windows font backend should use Uniscribe and suck less than our current font code.

Make low-end systems work well

Benchmark and optimize cairo for low-end systems, especially Windows.

Hook up Thebes printing

Switch over to use Thebes by default

Remove existing gfx

Glitz configuration whitelist

  • Implement a system for detecting hardware configurations (including OpenGL driver version and actual GPU)
  • Compile a whitelist of configurations for which Glitz is reliable and performant
  • Have Thebes use Glitz by default in those configurations

Units work

Eli Friedman has created a units patch that shouldn't land until after old-Gfx has gone. This will address various DPI and scaling issues.

Unresolved Issues

  • When do we switch Thebes on by default? Should we delay until performance is as good as today for most users?