View#remove should be a reliable method, but right now it is ignorant of any idea of there being a nested view structure. Are there memory leak issues there? I need to think about how I want to handle the shutdown of the entire view tree.
remove plucks the element from the DOM tree and calls stopListening, so presumably I should do a few things at this point:
Trigger an onDetach event down the whole tree (assuming the view was attached in the first place?)
Call stopListening down the entire tree
Note to self: right now, each view has its entire tree in a collapsed form available under _childViews, which could be utilized in situations like this.
View#removeshould be a reliable method, but right now it is ignorant of any idea of there being a nested view structure. Are there memory leak issues there? I need to think about how I want to handle the shutdown of the entire view tree.removeplucks the element from the DOM tree and callsstopListening, so presumably I should do a few things at this point:onDetachevent down the whole tree (assuming the view was attached in the first place?)stopListeningdown the entire treeNote to self: right now, each view has its entire tree in a collapsed form available under
_childViews, which could be utilized in situations like this.