| 42326004062d6b846c3050ad03a1e80fa9db425c |
|
29-Sep-2012 |
Chris Craik <ccraik@google.com> |
Determine maxZoomScale from bitmap/text drawing
bug:7247750
Change-Id: I8238acc2c20942ab2f42936d16a03226909aebcd
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| f762138fb2c8ec33fe3dec8e6bfd47e459f8f6c8 |
|
20-Jul-2012 |
Chris Craik <ccraik@google.com> |
SurfaceBackings are always zoomable once zoomable
Previously toggling hasText for the content of the SurfaceBacking was enough to
cause it to change scale entirely each time the value was changed. Now the
allowZoom flag is sticky to avoid unnecessary full-SurfaceBacking repaints.
Additionally, changes from allowZoom true->false will not trigger delay.
Change-Id: Ie6a13850f86d21f5a12a184c08b940aa2156ef07
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| 41a420aa58df2d7ae8c7f491e7ec4c3edc8a1ecb |
|
26-May-2012 |
Chris Craik <ccraik@google.com> |
Use newest available SurfaceBacking scale when counting texture usage
Using m_scale would mean that while zooming out, the clipped area would get
larger, but the scale would stay the same.
bug:6561401
Change-Id: I0806ecb8f565c4d227a2be2b7a27a0af6aff7b46
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| bfd7e70d96a769e5d62fb5c9148b5c810a8bef65 |
|
24-May-2012 |
Chris Craik <ccraik@google.com> |
Use Surface areas to compute tile usage
Previously we used the surface's first layer's area, which is often incorrect in
the case of significant layer merging.
bug:6545187
Change-Id: Ied3e5e3cd894b145ed905f8ba83649b3c4f3b1dd
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| 48605bf1f6bc77a1f037f23285baf7706f45d198 |
|
19-May-2012 |
Chris Craik <ccraik@google.com> |
Remove paint tile operations for stale painters
bug:6516612
also adds ClassTracker to several classes
Change-Id: I9a503084240d4935fba300a3256d266a2982dcc0
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| 377dc9f6b46a2ac0f968d9ee8d3c7916f3bf6904 |
|
18-May-2012 |
Nicolas Roard <nicolasroard@google.com> |
Fix invalidations sent to framework
bug:6479200 bug:6323847 bug:4124445
Change-Id: I1a4058ba6c69d3e285b6274d99a6eafcbf1cdc6f
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| 9e3ead124cc10fcc888a8be7df9949d3d4ba1bb7 |
|
03-May-2012 |
Teng-Hui Zhu <ztenghui@google.com> |
Unify the naming of rectangles used for draw.
The rects are referring to the same rect under different coordinates,
so we just prefix the coordinates' name to differentiate the rects.
This is pure refactor, no functional change.
bug:6338456
Change-Id: Ic072a4f5aa56a25751e0151a697c0e31bca94ef5
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| e859a34171f2a36877d95197d118d962078f8aa0 |
|
27-Apr-2012 |
John Reck <jreck@google.com> |
Rewrite PictureSet with TURBO!
This changes how partial invals are done by adding a hybrid mode.
What we used to do is generate a SkPicture for the new area. This
SkPicture would possibly be larger than the actual inval, depending
on various merge rules (more SkPictures == slower to draw a tile)
The new code rewrites PictureSet entirely, preserving many of the old rules
but cleans up the code and adds the concept of a "PrerenderedInval". This is
a partial inval that WebKit has rasterized. By having WebKit produce both
a SkPicture and a SkBitmap, we avoid needing to play back the picture and
avoid overdrawing. We take this SkBitmap, and simply update the front
textures with it. This gives us full partial invals through the entire
system without hitting any driver bugs, and with minimal copies. And while
the SkPicture may be larger than the inval, the SkBitmap that is rasterized
is not - it matches the area webkit has said is dirty.
Change-Id: Ieb7ecc9db0d4f679102fda004a43399f9b319ebc
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| e080317b90534632e8be18dc8d5e9a51554b444a |
|
18-Apr-2012 |
Chris Craik <ccraik@google.com> |
prevent double TileGrid preparation
bug:6346848
also renamed TileGrid* variables for clarity
Change-Id: Ie0e56a6e1e85db426c4944b03125248cd6a647c0
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| c884cf63d8cee0f30269e4ec7cbe2a6101fae686 |
|
12-Apr-2012 |
Chris Craik <ccraik@google.com> |
Separate prefetching TileGrid from front/back
Can now draw all available tiles while preparing new zoom level
bug:5690291
Change-Id: Ic08acc59e052d6b05d282329eed2cc526cb8f2f3
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|
| 2e510fd5b5a30f1315c272d44ae3aa4cba355498 |
|
06-Apr-2012 |
Nicolas Roard <nicolasroard@google.com> |
Reorganize platform/graphics/android
Change-Id: Idc67155cfa99784dcd931e705336bfa063ecae46
/external/webkit/Source/WebCore/platform/graphics/android/rendering/SurfaceBacking.cpp
|