* feat(split-panel): split panel support for ion-nav and ion-menu
Revert some changes
adds support split-panel support for tabs
Removes .orig
removes e2e.ts
Removes unneeded changes in menu.ts
improves stuff
* fix(split-panel): resize is called when menu wraps a ion-nav
* test(split-panel): improves split-panel/basic test
* feat(split-panel): ionChange is an ng2 @Output()
* fix(split-panel): fix tabs as side content
* fix(menu): forzedClose works as expected
* feat(split-panel): split-panel works with several menus
* chore(split-panel): renames to split-pane
* refactor(split-pane): splitPane can be injected
* fix(split-pane): it is a directive
* fix(slides): integration with split-panel
* Make gulp validate happy
Internal refactor completed in order to improve tree shaking and dead
code removal. The public API, with an exception to ion-slides, has
stayed the same. However, internally many changes were required so
bundlers could better exclude modules which should not be bundled.
Ultimately most changes resorted to removing references to `window` or
`document`, or a module that referenced one of those.
BREAKING CHANGES
ion-slides was refactored to remove the external dependencies, and
rewritten in TypeScript/ES6 modules to again improve tree shaking
abilities.
* fix(nav): controller is initialized
* fix(nav): transitioning state is a boolean not a timer
long async promises in canLeave / canEnter can lead to a false negative of isTransitioning()
It is key for the internal consistency of NavController to always know the correct state
* fix(nav): returning Promise<false> in canLeave / canEnter works as expected
* fix(nav): it is not allowed to pop all the views
I have measured the performance impact of this change, since we use the push change detector strategy, the *ngIf is only evaluated once.
Items wrapped around an element with the ListReorder directive will receive a hidden `<ion-reorder>` in their DOM, but items that are not wrapped (i.e. they CAN NOT be reordered) will not even have the `<ion-reorder>` element in their DOM.
fixes#9065
long async promises in canLeave / canEnter can lead to a false negative of isTransitioning()
It is key for the internal consistency of NavController to always know the correct state
- smoother by debouncing touch events (reduces bank)
- dynamic animation duration
- intelligent behavior based in the position, speed and direccion of the swipe (sharing logic with sliding item)
fixes#8919fixes#8958fixes#7934
NavControllerBase is the core of ionic 2 navigation. It handles all the transitions and it is complicated code to follow.
I am refactoring it to allow future developers and contributors to follow it better.
!node.parent now becomes node.isRoot()
ViewController does not remove itself from the stack, but two new auxiliar function in nav controller: _insertView() and _removeView() are used to add a view to the stack.
And so on...
All e2e and unit tests passing...
