DO NOT MERGE: feat: reusable views
PR Checklist
- [x] The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
- [x] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
- [x] You have signed the CLA.
- [x] All existing tests are passing: https://github.com/NativeScript/NativeScript/blob/master/DevelopmentWorkflow.md#running-unit-tests.
- [ ] Tests for the changes are included - https://github.com/NativeScript/NativeScript/blob/master/WritingUnitTests.md.
What is the current behavior?
Views and view trees are destroyed when removed from the view tree.
What is the new behavior?
Views can be marked as reusable and will not be destroyed when removed from view tree. Removing these nodes require the developer to do:
view.destroyNode();
// which calls
view.reusable = false;
view._tearDownUI();
For implementation details on how frameworks should deal with it, see my work in nativescript-angular: https://github.com/edusperoni/nativescript-angular/tree/reusable-views
Implements #7469.
To be defined:
What happens when a reusable view with children gets removed? The current implementation does not call _tearDownUI on children, but we should still suspendNativeUpdates down the chain (this._suspendNativeUpdates(SuspendType.UISetup);).
Maybe we should we create a new SuspendType (Detached)? Maybe this isn't even needed as the view should be unloaded by _removeViewCore which eventually calls this._suspendNativeUpdates(SuspendType.Loaded); on all children.
Possible refactoring needed (not directly related to this PR)
The current logic of _resumeNativeUpdates will call initNativeView. In most places I checked, initNativeView creates delegates that are only removed in disposeNativeView. This behavior is probably already an issue on loading/unloading views (like navigation) because of this._resumeNativeUpdates(SuspendType.Loaded);, meaning initNativeView is called multiple times during the application lifecycle, but the delegates are only cleaned up once.
During my tests with WebView, calling initNativeView did not result in a performance impact
After further working on this, SuspendType.Loaded seems to be sufficient. One of my commits had actually messed with the logic resulting in a crash (trying to re-add children to the native visual tree, which they already were added to). All child views are unloaded on parent removal.
I'll also weigh in that I believe child views should not be destroyed even when detached simply because it's already the behavior on tabviews (which soft detaches elements)
@edusperoni I'm curious what are your current thoughts on this PR? Does it still require changes?
@NathanWalker I believe this just requires some testing and maybe treatment of edge cases. For example: if the view is detached and reusable is set to false, should it run _tearDownUI? Other than that, I think it'd be good as is.
Flagging for 7.0 to test more with latest changes planned.
@edusperoni Let's update this to latest master either from a new branch or rebase.