MVC with CoffeeScript
andrzejonsoftware.blogspot.com
andrzejonsoftware.blogspot.com
As an example (following the game analogy), I have a column on the left displaying player stats, and the main game board on the right. The left column lets you do things such as editing a players details and inviting friends, and the game board lets you play the actual game. In Backbone I would have a View for the player column and a View for the game board, which themselves trigger other Views, as the 'controller' in Backbone doesn't really seem a logical fit for this. I'm guessing this is why they have now renamed it to Router.
I must be doing it wrong... are there any good examples of complicated apps built in Backbone?
> Maybe I'm just doing it wrong [...]
> are there any good examples of complicated apps built in Backbone?
class Player extends Backbone.Events
class Player
constructor: (attributes) ->
_.extend(this, Backbone.Events)
_.extend(this, attributes)From what I've seen it brings an alternative syntax without reducing any complexity. And before you say it, no, removing braces does not reduce complexity.
class Widget
render: =>
alert "Here I am!"
class Button extends Widget
var Button, Widget;
var __bind = function(fn, me){ return function(){ return fn.apply(me, arguments); }; }, __hasProp = Object.prototype.hasOwnProperty, __extends = function(child, parent) {
for (var key in parent) { if (__hasProp.call(parent, key)) child[key] = parent[key]; }
function ctor() { this.constructor = child; }
ctor.prototype = parent.prototype;
child.prototype = new ctor;
child.__super__ = parent.prototype;
return child;
};
Widget = (function() {
function Widget() {
this.render = __bind(this.render, this);
}
Widget.prototype.render = function() {
return alert("Here I am!");
};
return Widget;
})();
Button = (function() {
__extends(Button, Widget);
function Button() {
Button.__super__.constructor.apply(this, arguments);
}
return Button;
})();