Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
backbone.controller
Advanced tools
Controller for Backbone MV*
Keep controller logic separated, split your routes to controllers.
DEMO: Just Test It
Usage examples:
###Basic
var Controller = Backbone.Controller.extend({
initialize: function() {
// do init stuff
},
search: function(query, page) {
// create search model and view
}
});
var searchController = new Controller();
###Controller supports default Backbone events
var Controller = Backbone.Controller.extend({
initialize: function() {
this.model = new Backbone.Model();
this.listenTo(this.model, 'add', this._onAdd);
},
_onAdd: function(model) {
// show notification view
}
});
var catsController = new Controller();
###Controller has remove method for cleanup
Remove method should do correct remove for all controller views and models, stop listening controller events and clear state.
var Controller = Backbone.Controller.extend({
initialize: function() {
this.model = new Backbone.Model();
this.listenTo(this.model, 'add', this._onAdd);
},
_onAdd: function(model) {
// show notification view
}
});
var catsController = new Controller();
//...
catsController.remove();
Also remove method is calling automatically when user goes from one controller to another. See routing section for details.
It's little more complex than previous examples but can be used to keep all routes separately which is good idea for any size app.
var CatsController = Backbone.Controller.extend({
routes: {
'cats': 'list',
'cats/:id': 'showCat'
},
initialize: function() {
// do some init stuff
},
list: function() {
// show cats list
},
showCat: function(catId) {
// show cat view
}
});
var DogsController = Backbone.Controller.extend({
routes: {
'': 'list',
'dogs': 'list',
'dogs/:id': 'showDog'
},
initialize: function() {
// do some init stuff
},
list: function() {
// show dogs list
},
showDog: function(catId) {
// show cat view
},
remove: functin() {
// cleanup
}
});
var Application = Backbone.Router.extend({
controllers: {},
initialize: function() {
this.controllers.cats = new CatsController({router: this});
this.controllers.dogs = new DogsController({router: this});
Backbone.history.start();
}
});
The main idea - pass {router: routerInstance}
as controller option.
This allows to define controller specific routes in separated controllers.
When url changes from #dogs
/ #dogs/:id
to any route which defined in another controller, remove method is calling automatically.
This case controller should clear state, remove controller specific views and models.
var CatsController = Backbone.Controller.extend({
routes: {
'cats': 'list',
'cats/:id': 'showCat'
},
initialize: function() {
// do some init stuff
},
list: function() {
// show cats list
},
showCat: function(catId) {
// show cat view
}
});
var DogsController = Backbone.Controller.extend({
routes: {
'': 'list',
'dogs': 'list',
'dogs/:id': 'showDog'
},
initialize: function() {
// do some init stuff
},
list: function() {
// show dogs list
},
showDog: function(catId) {
// show cat view
}
});
var cats = new CatsController({router: true});
var dogs = new DogsController({router: true});
Controller automatically calls onBeforeRoute
/ onAfterRoute
functions when processing routes.
var DogsController = Backbone.Controller.extend({
routes: {
'': 'list',
'dogs': 'list'
},
initialize: function() {
// do some init stuff
},
onBeforeRoute: function(url, param1, param2, ...) {
// called before `#dogs` / `#` routes
// Set some state variables, create controller layout etc
},
onAfterRoute: function(url, param1, param2, ...) {
// called after `#dogs` / `#` routes
},
list: function() {
// show dogs list
}
});
var dogs = new DogsController({router: true});
//Cancel route
var DogsController = Backbone.Controller.extend({
routes: {
'dogs': 'list',
'dogs/:id': 'showDog'
},
initialize: function() {
// do some init stuff
},
list: function() {
// show dogs list
},
showDog: function(catId) {
// show cat view
},
onBeforeRoute : function(url) {
console.log('before route');
var deferred = Q.defer();
setTimeout(function() {
deferred.resolve('ggg');
}, 2000);
return deferred.promise;
//return false;
},
onAfterRoute : function() {
console.log('afterRoute');
}
});
var dogs = new DogsController({router : true});
Backbone.history.start();
If declarative routing has been used in project, you don't have access directly to Router instance. Backbone Controller provides Controller.navigate method as proxy for Backbone.Router.navigate method.
var DogsController = Backbone.Controller.extend({
routes: {
'dogs': 'list'
},
list: function() {
// show dogs list
// if something
this.navigate('cats/', {trigger: true});
}
});
var dogs = new DogsController({router: true});
requirejs.config({
baseUrl: 'static/',
urlArgs: 'bust=' + Date.now(),
paths: {
jquery: 'assets/js/jquery',
underscore: 'assets/js/underscore',
backbone: 'assets/js/backbone',
controller: 'assets/js/backbone.controller'
},
shim: {
backbone: {
deps: ['underscore', 'jquery'],
exports: 'Backbone'
},
controller: {
deps: ['underscore', 'backbone']
},
app: ['controller']
}
});
var Controller = require('controller');
// or require Backbone, both fine
var HomeController = Controller.extend({
...
});
<script src="assets/js/jquery.js" />
<script src="assets/js/underscore.js" />
<script src="assets/js/backbone.js" />
<script src="assets/js/backbone.controller.js" />
bower install backbone.controller
FAQs
Controller for Backbone.js applications
We found that backbone.controller demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.