Confirmed users
523
edits
Platform/GFX/HardwareAcceleration: Difference between revisions
→Image management
(New page: == The Plan == The current plan to hardware accelerate Gecko and Firefox is to use OpenGL. This seems like a good starting point because it's supported (to varying degrees) on all the pla...) |
|||
| Line 47: | Line 47: | ||
=== Image management === | === Image management === | ||
Similarly to text rendering, we will need to have the ability to cache images in textures in VRAM. This requires the (at the time of this writing) on-going Imagelib refactoring to support decode-on-draw and throwing away decoded data (textures), just in case we don't want to hold on to large textures. There will probably also need to be some form of tiling to make this work properly, because OpenGL implementations have a maximum texture size. | Similarly to text rendering, we will need to have the ability to cache images in textures in VRAM. This requires the (at the time of this writing) on-going Imagelib refactoring to support decode-on-draw and throwing away decoded data (textures), just in case we don't want to hold on to large textures. There will probably also need to be some form of tiling to make this work properly, because OpenGL implementations have a maximum texture size. | ||
An interesting problem we'll need to solve is how to do filtering across texture boundaries when the image is too large to fit into a single texture. | |||
=== Plugins === | === Plugins === | ||