I'm trying to figure out how to postpone the default controller binding and only apply it from within the directive, once the specific animation (custom - not the angularjs one) has been performed on the DOM element with the content. The fiddle to what I'm trying to accomplish is here, although it does replace the content right away - before the sliding animation has completed: http://jsfiddle.net/scabro/hHy7s/27/
I need to be able to postpone the $scope binding until the page container has completed sliding / animated up, then replace the content with the data from within the controller and once this has been done, slide back down.
Here's what I currently have:
HTML:
<div id="wrapper" ng-app="myApp">
<div page-animate>
<p>
<a class="btn btn-primary" href="#/" ng-click="slidePage()">Home</a>
<a class="btn btn-info" href="#/users" ng-click="slidePage()">Users</a>
<a class="btn btn-success" href="#/pages" ng-click="slidePage()">Pages</a>
</p>
<div id="relativeContainer">
<div id="content" ng-view=""></div>
</div>
</div>
</div>
CSS:
#wrapper {
text-align:center;
padding:30px 0;
}
#relativeContainer {
text-align:left;
position: relative;
width: 500px;
height: 800px;
min-height: 800px;
margin: 0 auto;
overflow: hidden;
}
#content {
position: absolute;
top: 0;
left: 0;
}
JS:
var myApp = angular.module('myApp', []);
myApp.directive('pageAnimate', function() {
return {
restrict: 'A',
scope: { },
link: function (scope, elem, attrs) {
scope.slidePage = function() {
var thisContainer = $('#content');
var thisHeight = thisContainer.outerHeight();
thisContainer.animate({ top : '-' + thisHeight + 'px'}, { duration : 300, complete : function() {
thisContainer.css({ top : '-999999em' });
var thisNewHeight = thisContainer.outerHeight();
$('#relativeContainer').animate({ height : thisNewHeight + 'px' }, { duration : 200, complete : function() {
thisContainer.css({ top : '-' + thisNewHeight + 'px' }).animate({ top : 0 }, { duration : 300 });
}});
}});
};
}
}
});
myApp.config(function($routeProvider) {
$routeProvider
.when('/',
{
controller: 'HomeController',
template: '<h1>{{ heading }}</h1><p>{{ content }}</p>'
}
)
.when('/users',
{
controller: 'UserController',
template: '<h1>{{ heading }}</h1><p>{{ content }}</p>'
}
)
.when('/pages',
{
controller: 'PageController',
template: '<h1>{{ heading }}</h1><p>{{ content }}</p>'
}
)
.otherwise(
{
redirectTo: '/'
}
)
});
myApp.controller('HomeController', function($scope) {
$scope.heading = 'Home page';
$scope.content = 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Donec quam felis, ultricies nec, pellentesque eu, pretium quis, sem. Nulla consequat massa quis enim. Donec pede justo, fringilla vel, aliquet nec, vulputate';
});
myApp.controller('UserController', function($scope) {
$scope.heading = 'Users';
$scope.content = 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Aenean commodo ligula eget dolor. Aenean massa. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus.';
});
myApp.controller('PageController', function($scope) {
$scope.heading = 'Pages';
$scope.content = 'Lorem ipsum dolor sit amet, consectetuer adipiscing elit.';
});
First of all, some minimal changes to get what you have working. You need to prevent the default event from navigating the page (that's why it changes before the navigation completes), and you need to do the navigation manually after the first animation has finished. So one way is to pass the event and url into
slidePage
:and
slidePage
itself becomes:That code should work as you want, but I don't think it quite follows the angular philosophy.
Instead what I think you should do is add a
slidePage
directive directly so the links are<a href='#/pages' slide-page>
. That directive has access to the attributes (so it can pick up the href), and can bind aclick
handler directly onto the anchor element. I would also remove the hard-wiring of the#content
element by tagging the element to be animated with another directive. However the same basic principle applies: stop the event propagating, do the first animation and then update the location before doing the second animation.