299659ddb7e0c34ca094abe485bcd0989727fc07 |
|
07-Oct-2016 |
John Reck <jreck@google.com> |
Convert VD/AVD to FastNative Test: build & boots Change-Id: I6519ba245eca1a43fb00de36c91a05a9740c8c5f
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
335d7d174464ea3fc2d058dcff6e436df1cf0fd9 |
|
27-May-2016 |
Doris Liu <tianliu@google.com> |
Copy native tree's property when mutate vector drawable When mutating vector drawables, we need to not only copy over the VD tree structure, but also the properties of the VD tree, such as alpha. Bug: 28974071 Change-Id: If793f5f2b6e116472a1c6da0fb60d8278a78b03f
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
f8d131cc8dc4ef675b8f8fc57dcc26062d575d32 |
|
30-Apr-2016 |
Doris Liu <tianliu@google.com> |
Count native allocation for VD against Java heap There are two parts to VD's native allocation: 1) VD's internal data structure (i.e. groups, paths, etc that make up of the VD tree). This structure can change, when a VD is used to load a different drawable resource. 2) Two bitmap caches, not both of which will necessarily be allocated The size of the bitmap cache depends on canvas matrix and drawable bounds, and therefore can often change. We need to count the native allocation from the above against Java heap. Bug: 26269056 Change-Id: If833aedcf7f3efe00ea73a41ddccb1b48066ffd8
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
b35da390601e3c24e777d72daacd8dbeb4d1d9c4 |
|
12-Apr-2016 |
Doris Liu <tianliu@google.com> |
Allow leading spaces in path string (to keep behavior consistent) Bug: 28132454 Change-Id: Iee799c13a85738db3d6940aca0fe917f284fa651
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
1ee2dd2f5fb10cd0e6a4d3d368c1e24d3ec417a2 |
|
12-Apr-2016 |
Doris Liu <tianliu@google.com> |
Merge "Check whether VD tree is still valid before calling native setter" into nyc-dev
|
cdedc9a80d971c8152b6f2674c040c79cff3b8dd |
|
12-Apr-2016 |
Doris Liu <tianliu@google.com> |
Check whether VD tree is still valid before calling native setter VD tree is ref-counted in both Java and native. VD's child nodes are entirely owned by the native tree, as VD nodes in native should outlive its Java counterparts, with one exception: when there's an infinite UI animator running on VD, the animator may have weak reference to a few child nodes. In the case of hidden animator running infinitely, the child nodes would keep getting the animation pulse while the rest of the tree would have been destroyed. To prevent the setters triggered by animation from calling into native, we need to check whether the tree is still valid before going down into JNI. Bug: 28104172 Change-Id: Ie9d4bf3898c0c23e620a4747624d24b8ab779743
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
0a1a5167be26d363d4e27bdc7b816f425b7b4e66 |
|
08-Apr-2016 |
Doris Liu <tianliu@google.com> |
Improve error logging for parsing failures Bug: 27043594 Change-Id: I901b65f734c49444a78e0714e007e15e2340ab9d
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
1d8e194661085f9a18ab1b3cd12f9e19d3a86be5 |
|
03-Mar-2016 |
Doris Liu <tianliu@google.com> |
Make AVD thread safe This CL introduces staging properties to VectorDrawable, which holds properties coming from UI thread. When staging properties are changed, they are marked dirty, and the staging properties then get pushed to RenderThread at sync point. In cases where no staging property has been changed, at sync point we sync the render thread properties back to staging properties to reflect the latest render thread animation value change. Also, update Vector Drawable bitmap only when it's dirty Bug: 27343970 Bug: 27385912 Bug: 27263667 Bug: 27927674 Bug: 27774383 Change-Id: Ia864f5400a53a08dbfb284fae581fb1aac4fff87
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
dccca44ffda4836b56a21da95a046c9708ffd49c |
|
21-Mar-2016 |
sergeyv <sergeyv@google.com> |
Reland: Move text logic from jni to hwui level Initial CL: https://googleplex-android-review.git.corp.google.com/#/c/886854/ Change-Id: I9dfd85fe1d2a2c44f4360c8a29fd58d80e6f31c8
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
afbd0f1fef46ef0ddf633dfde0de724db3da1405 |
|
21-Mar-2016 |
Sergei Vasilinetc <sergeyv@google.com> |
Revert "Move text logic from jni to hwui level" This reverts commit a7f6bba1a3565c19715e878dfe7f0e01022944ff. Change-Id: If4f36f87a85411b6128fd92d391313803ccaf9dd
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
a7f6bba1a3565c19715e878dfe7f0e01022944ff |
|
16-Mar-2016 |
sergeyv <sergeyv@google.com> |
Move text logic from jni to hwui level bug:25865834 Change-Id: I2d8c9c9544afcb5ce1784f732aed3e54e0eda372
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
46591f4a2dbd785bcae2b82bb490e78208605ec8 |
|
15-Mar-2016 |
Teng-Hui Zhu <ztenghui@google.com> |
Add fillType support to VectorDrawable Default as non-zero, which is the same as SVG. b/27533958 Change-Id: Id20e6d3493bb4d2b4b65d7f6cdb13586631c40e4
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
ef062ebd20032efe697741d6c3dfd1faec54f590 |
|
05-Feb-2016 |
Doris Liu <tianliu@google.com> |
Ref count the nodes in VectorDrawable Also added API check so that for pre-N we ignore invalid VD animation, in order to avoid breaking old apps. Bug: 26975469 Bug: 26949340 Change-Id: I498539ad6a05de3d886e7dcdc8a167e78333ab11
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
766431aa57c16ece8842287a92b2e7208e3b8ac3 |
|
04-Feb-2016 |
Doris Liu <tianliu@google.com> |
Revert "Revert "VectorDrawable native rendering - Step 4 of MANY"" This reverts commit 5a11e8d0ba21624025b89ac63bbd18befa55be0e. Change-Id: I7a48b59c4f930dad65ddc8590c25a12636244ea2
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
5a11e8d0ba21624025b89ac63bbd18befa55be0e |
|
04-Feb-2016 |
Doris Liu <tianliu@google.com> |
Revert "VectorDrawable native rendering - Step 4 of MANY" b/26949340 and b/26975469, b/26975079 as well This reverts commit f276acd98457bcaabc9e79a17a736b3b484f005e. Change-Id: I4b55177daf0d289bc03604c71fd4bf579f65073a
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
f276acd98457bcaabc9e79a17a736b3b484f005e |
|
07-Jan-2016 |
Doris Liu <tianliu@google.com> |
VectorDrawable native rendering - Step 4 of MANY This CL runs VectorDrawable animation on RenderThread. The changes in this CL include: - Convert all the animators in AnimatorSet for AVD into a set of RenderNodeAnimators. - Hook up the new animators with RenderThread - Add drawOp in RecordingCanvas for drawing VD so that during the animation on RenderThread, all the property changes on VD can be reflected on the screen. TODO: - Implement reverse and reset for AVD. Change-Id: I2df1d754f2db0ad098d9c15dde4bb2bdfafc2315
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
dbee9bb342cdfaa5155b1918f90262c05e2464cb |
|
15-Dec-2015 |
Teng-Hui Zhu <ztenghui@google.com> |
Gradient for VectorDrawable's fill and stroke Add ComplexColor interface for both GradientColor and ColorStateList. Set up constant state, factory, theme attrs for GradientColor, while refactoring the ColorStateList's similar code. (Functionality in CSL should be the same). Support themeing in both the root and item level in GradientColor. For example, both startColor in <gradient> tag or color in <item> tag can have theme color. Add tests for both simple and complex cases with themeing etc. Hook up the native VectorDrawable implementation using 2 extra JNI calls for simplicity. Such calls only happen at inflate and applyTheme call. b/22564318 Change-Id: Ibdc564ddb4a7ee0133c6141c4784782f0c93ce0e
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|
4bbc2931263b232fba61807fca00e127573eff42 |
|
02-Dec-2015 |
Doris Liu <tianliu@google.com> |
VectorDrawable native rendering - Step 3 of MANY - Refactored VPathRenderer & VectorDrawableState - Moved all the VD rendering into native - Set up hooks for VD's property changes in JNI for animated VD TODO: JNI calls can be further reduced when we convert the animation in AVD to use RenderNodeAnimator, in which case animation will be driven from native and therefore most of the JNI hooks for changing VD's properties during animation will no longer be needed. Change-Id: I52021f4d7bea057b83ace54085d870dd45acae0f
/frameworks/base/core/jni/android_graphics_drawable_VectorDrawable.cpp
|