* fix(animations): change throw -> trace to avoid unnecessary app crash
Fixes major cause of crashes/bugs in production apps using animation.
* Fix fix animation throw (#1)
* chore(tests): Cleanup code snippets comments
* refactor(animations): Plat-specific cancel and play methods refactored
* feat(animation): support animating width/height properties
- width/height can be specified in any valid PercentLength form that can be parsed.
- make width/height properties be based on animatable CSS property. TODO: affectsLayout????
- add a few basic tests. Could probably use a few more?
- fix a few null pointer exceptions in PercentLength helpers
* test(ui): add animation examples to ui-tests-app
- basic height animation
- height animation in StackLayout
- fix an issue where strings were not automatically converted to PercentLength when calling directly into `View.animate`
* test(ui): cleanup and add summary/details layout example
- use height transition to cover textview content.
- when clicking on the summary view, animate the summary height up to a small header and show the text view.
- fake animating the height on the textview by very subtly animating its translateY value while shrinking the header height. This tricks your mind into think that the text view is also vertically growing, even thought it's just slightly moving up along the Y axis.
* test(ui): add animation curves test page
- verify all built-in animation curve types work as expected.
* test(ui): update animation curve example for multiple properties
- add a segmented bar that allows choosing which properties to animate using the various curves.
- interestingly, a whole bunch of properties fail with spring on iOS.
- refactor width/height animations handlers to remove duplication on iOS.
- implement proper spring animation for width/height on iOS.
* test(ui): add stress example with 100 labels animating and fps meter
- same curve/property selector as the curves example, but with 10x10 grid of items that stagger animate, and an FPS meter.
- sadly it looks like width/height animations are considerably slower than the others when you have a bunch of them. I'm not sure that's entirely surprising since they interact with the layout system.
- the better news is that even with the army example, my really old android 4 tablet manages ~30fps. On height/width animations from the curves example, the old tablet does fine with no noticeable FPS hit.
* refactor: deduplicate existing droid width/height animations
- stash to prep for replacing with LayoutTransition.
* test(animation): unit tests for extent animation and PercentLength parse
- update animation scaffold to allow specifying the parent stack layout height/width
- test basic supported units, px, %
- test basic percent length parser behaviors
* chore: cleanup cruft and remove noise from diff
- undo the import mangling that WebStorm helpfully applied
- remove .editorconfig file
- clean up in tests, remove cruft
* chore: cleanup from review
- more import changes
* chore: remove .editorconfig
recycleNativeView filed now accepts: "always" | "never" | "auto". Always will recycle the nativeView no matter if its nativeView or android proprties are accessed. Never will disable recycling. Auto will recycle it only if nativeView and android properties are not accessed.
In Angular, if the NativeScriptAnimationModule is imported in another
NgModule more than once (which shouldn't be done), the renderer is instantiated twice. This
causes animation with empty targets to be created. If such animation is
removed, the app will crash. Additional check if the target is present
will prevent this.
* disable recycling on specific button
add more thorough test for view recycling
fix memory leak with android ActionBar
improve padding reset when view is recycled
improve reset of several controls
* stopping local animations when view is recycled
fix tns-ios version in tests/package.json
* Fix isClickable on android when reusing nativeView
- Always apply animations even if it happens before the loaded event.
- Add an extra check for Android LinearInterpolator to get rid of a
curve resolution crash.
