It's pretty, yes. But please, I beg you, please take away this inhumane torture. Give us a more usable navigation.

How old is the person who came up with this idea anyways?!

Hi Tommy, couldn't find an email anywhere so this is the only way I could seem to talk to you.

Could you explain how, I could get the "slides" in the NotesModel into $scope to be bound to an attribute in the html? I don't understand how to get objects in the Model into $scope to be bound to ng-attributes.

Also why does NotesModel inherit from EventDispatcher?

I really like the ideas you present here, you solve complex controller interactions elegantly. It seems like you have used ReactJS before, as these Angular modules are starting to look like React components! Love the reusability in the Model and Service providers.

If would rather talk via email i'm at [email protected]

Thanks a bunch in advance,

Yin

Why you use notification but not rootScope.emit?

And the event name is the same as namespace you defined, why not just use a string directly? I tried and do not get auto complete in PHPStorm so what's the point?

Navigating from a slide to the next one and then back using a keyboard, before the slide transition animation is over results in:

• No slide transitioning in;
• Navigation stops working using Keyboard and Mouse;

How to reprocude:
Press [Left] and [Right](or [Right] and [Left]) keyboard buttons in fast succession.

Reproducable on:
Chrome, Internet Explorer 9

Minor English issue here. You are using the word "loosing" in places where I believe you mean "losing". They are indeed quite different. The former means "letting go" and is the past participle of "loose", whereas the latter means "actively missing out on" and is the past participle of "lose".

Hi there,

One thing I've been wondering is that why should your angular design pattern apply structured class and class inheritance. Could you please arrange your time to give more detail explanation on it.

Sincerely thanks,
Trung

Problem with $routeProvider add routes for HomeController:

.when('/home', {
templateUrl: 'build/views/home/index.html',
controller: 'HomeController'
})

Error:

Error: [ng:areq] http://errors.angularjs.org/1.4.7/ng/areq?p0=HomeController&p1=not%20aNaNunction%2C%20got%20undefined

The links to MagmaConf 2013 and OpenCode in the readme go to a github 404 page. Do you have the updated links?

Hello,

Great job with the design patterns, really appreciate your work.

I am having a issue when trying to remove an event listener using your EventDispatcher class. (it just returns '-1' with .indexOf in the 'removeEventListener' function.

This is my code (controller using basecontroller.extend):

defineListeners: function () {
    this._super();

this._Notifications.addEventListener(ui.controlbar.events.INTERVAL_ELPALSED, this._handleIntervalElapsed.bind(this));
}

_handleIntervalElapsed: function (event, message) {
this.$scope.currentTime = message.currentTime;
this.$scope.$apply();
},

destroy: function () {
console.log('destroy');
this._Notifications.removeEventListener(ui.controlbar.events.INTERVAL_ELPALSED, this._handleIntervalElapsed.bind(this));
}

Thanks in advance,

So as the title says, I'm trying to migrate your example to Angular 1.4.7, with little success, other then a slight change with using prototype rather then the included class.js (this shouldn't cause any issues from what I've investigated), the issue lies in controller. I already assumed that since I think angular 1.2 lazy loading controllers to the app was disabled (I may be confusing the defaulting of controllers to anonymous apps), so I thought, easy enough include the below:

angular.module('notes.Controller',
        [ 'notifications', 'notes.NotesModel', 'notes.NotesService' ])
        .controller(
            'NotesController',
            [
                    '$scope',
                    'NotesModel',
                    'Notifications',
                    '$route',
                    new notesController($scope, NotesModel, Notifications,
                            $route) ]);

And then update the app.js to include the new module.
The issue appears to be that $scope (and should i remove it all together the remaining parameters have the same error occuring) appear to be throwing:

Uncaught ReferenceError: $scope is not defined

I've looked through everything I can think of, and can't seem to figure out why this is the case. Would you be able to migrate this to the latest build for relevance purposes