Confirmed users
523
edits
| Line 403: | Line 403: | ||
Anholt: destination tile cache sounds pretty nice to me, and with APPLE_object_purgeable use the GPU could throw things out of the cache when appropriate (rather than you having to guess). | Anholt: destination tile cache sounds pretty nice to me, and with APPLE_object_purgeable use the GPU could throw things out of the cache when appropriate (rather than you having to guess). | ||
=== Tile Cache === | |||
==== Disadvantages ==== | |||
* Memory usage is >= window size | |||
* More complicated | |||
* Need a mechanism to deal with tiles that aren't ready | |||
==== Advantages === | |||
* Easy to accelerate | |||
* Better for pixel scrolling/smooth scrolling | |||
=== Traditional Scrolling === | |||
==== Disadvantages ==== | |||
* Not so good for pixel scrolling/smooth scrolling | |||
* Scrolling speed limited by paint speed | |||
* No backing store, so we can't move things without repainting the damaged area | |||
==== Advantages ==== | |||
* Memory usage is 0 | |||
* We already do this | |||
= Comparison with other APIs = | = Comparison with other APIs = | ||