* 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
Call native setters once when a page is instantiated.
Fix background not being reset, Label's background is now set to background, not layer
Make the nativeView field instead of property for performance reasons
TKUnit default message change to empty string
isSet method is now instance method of Property classes
fix detaching from parent bindingContext - were using oldParent.parent instead of parent
editable-text-base.android - onTextChanged implementation commented. Does nothing.
frame - onCreateView wrapped in try/catch and shows label with exception message if any
text-base.android - should support reset of nativeView. TransformationMethod won’t be set if TextField is secure
Change some types to their string couterparts
TextField.android won’t support multilines anymore in order to work as iOS
In android when page is removed from native backstack we won’t call tearDownUI again a second time
* Change image.android to use the new image.Cahce class from widgets.
* fix npm scripts
* npm tsc will compile all so no need for npm run dev-tsc-tests
* fix tslint error
* image-tests use memory only cache.
* fix exception in image.android
* Change image-tests so that Image won't be GC immediately.
* Change cacheMode to enum
Less than 30 erros left, let's hope it still works
Added lib.*.d.ts from typescript, removed lib and dom stuff, added by hand XHR, alert etc. .d.ts-es for polyfills
Roll back some changes involved in separating UIEvent for dom and ios
Test combined dts-es will now use lib, while internally we will not to avoid UIEvent conflict with dom stuff
