Changes between Version 5 and Version 6 of DisplayLists


Ignore:
Timestamp:
Nov 17, 2015 10:06:06 AM (7 years ago)
Author:
Jon Davis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DisplayLists

    v5 v6  
    2525* Reduces expensive traversal of the render tree for each tile
    2626* Converts some paints to pure display-list operations, such as:
    27 ** GIF animation, CSS animations, scrolling
     27 * GIF animation, CSS animations, scrolling
    2828* We can also potentially use display lists to paint off the main thread
    2929
     
    3232* Many optimizations we can fit in to our existing code as one-off optimizations, but display lists provide a common way of reasoning about these optimizations
    3333* Make WK code more efficient by eliminating useless repaints, using precomputed display lists
    34 ** Better culling (accurate extent information): we can use the display list to compute the exact bounds of what needs to be repainted, allowing us to tighten the repaint rect
    35 ** Can optimize noops out of the painting code
    36 ** Occlusion detection and clipping
    37 ** Can reorder operations for better batching
     34 * Better culling (accurate extent information): we can use the display list to compute the exact bounds of what needs to be repainted, allowing us to tighten the repaint rect
     35 * Can optimize noops out of the painting code
     36 * Occlusion detection and clipping
     37 * Can reorder operations for better batching
    3838* Reuse display lists in a single painting pass (e.g. SVG images, <use>)
    3939* Can keep display lists around between painting passes (e.g. across different tiles)
    4040* We have opportunities to cache display lists
    41 ** Text rendering: don’t have to recompute kerning, glyphs (?)
     41 * Text rendering: don’t have to recompute kerning, glyphs (?)
    4242* We can log all the painting commands that happen
    43 ** Developer tools implications: can use display list logs to tell which elements are the most costly to render, or perhaps scrub through the painting of a page
    44 ** Can also use display lists to help layout testing
     43 * Developer tools implications: can use display list logs to tell which elements are the most costly to render, or perhaps scrub through the painting of a page
     44 * Can also use display lists to help layout testing
    4545
    4646== What are the biggest challenges? ==