This post will be covering something that I recently wanted to implement, but it seemed that it not so straight forward - animating ng-views when they change.
An example of such transitions you can check here http://code.angularjs.org/1.1.4/docs/api/ng.directive:ngView#animations . As you can see when you click on a link, the view is changed by making this slick slide animation. One thing that we notice is that the view is sliding only in one direction, but it will be really nice to have it both ways, based on the hierarchy of the views.
In this great post http://blog.revolunet.com/blog/2013/04/30/angularjs-animations-mobile-applications/ we can see how we can make the sliding bi-directional, and it is looking much better.
However we also want the app to respond to browser's Back and Forward button, so we have to handle route changes and switch the animation CSS class based on where we were now and where are we going, so we can have this next and previous interaction.
In AngularJS this is easy we just add a route change handler
var oldLocation = '';
$scope.$on('$routeChangeStart', function(angularEvent, next) {
console.log("routeChangeStart");
var isDownwards = true;
if (next && next.$$route) {
var newLocation = next.$$route.originalPath;
if (oldLocation !== newLocation && oldLocation.indexOf(newLocation) !== -1) {
isDownwards = false;
}
oldLocation = newLocation;
}
$scope.isDownwards = isDownwards;
And having the following set for our view
<div ng-view ng-class="{slide: true, left: isDownwards, right: !isDownwards}"></div>
We have some kind of sliding animation when we switch between views. But there is a "gotcha". When the view is changed, the old view slides to the opposite direction, say "right" and disappears, then the new view slides from the "right" direction, where we expect the old view to slide to the "left" and disappear and the new view to appear and slide from the "right". This is because both the switching of views and assigning of "isDownwards" to the model is done in the same $digest cycle, and therefore the old view, when removed, does not have the new direction class applied, and is animated to the opposite (old) direction.
So in order to fix this we have to switch the views, after the cycle in which the "isDownwards" is applied to the model. AFAIK to invoke something after the current digest cycle you can invoke $timeout and pass 0 for delay. And to delay the view switching, we can pass a resolve map to the route parameter of $routeProvider, and if any of it's dependencies return a promise, Angular will wait until this promise is resolved. So our code for this will look like:
var resolve = {
delay: function($q, $timeout) {
var delay = $q.defer();
$timeout(delay.resolve, 0, false);
return delay.promise;
}
};
angular.module('viewTransitionApp', ['ngRoute', 'ngAnimate'])
.config(function ($routeProvider) {
$routeProvider
.when('/viewA', {
templateUrl: 'viewA.html',
resolve: resolve
});
});
Having all this, we can have an application with views that when switched are animated in a given direction, and this direction is based on the current location, and the location that we are changing to. Of course this sliding animation can be changed with any other animation that makes sense to have forward and backward behavior.
The final example can be seen here:
http://maverix7.appspot.com/files/ngview/index.html
You can right click and view its source or see this gist https://gist.github.com/tgeorgiev/7667648
