Basics library for developing backbone applications
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Backbone Basics

Basics library for developing backbone applications.

This is a work in progress


Basics exports this structures:


This is what this library provides to help:

Nested data structures

To define nested structures:

var Person = Basics.Model.Extend({
  defaults: {
    name: '',
    email: ''

var Message = Basics.Model.extend({
  defaults: {
    subject: '',
    text: '',
    sender: null
  types: {
    sender: Person

var Messages = Basics.Collection.extend({
  model: Message

var Inbox = Basics.Model.extend({
  defaults: {
    owner: null,
    messages: null
  types: {
    owner: Person,
    messages: Messages

When creating them (works both passing json to the constructor and calling the service with .fetch):

// To create it with new from a JS structure or JSON, do not forget to pass the
// option `parse: true` at the end, or the subtypes wont be parsed
var inbox = new Inbox({
  owner: {
    name: 'John',
    email: ''
  messages: [{
    subject: 'Example 1',
    text: 'Text 1',
    sender: {
      name: 'John',
      email: ''
  }, {
    subject: 'Example 2',
    text: 'Text 2',
    sender: {
      name: 'John',
      email: ''
}, {
  parse: true

var ownerName = inbox.get('owner').get('name')
  , secondMessageSubject = inbox.get('messages').at(1).get('subject')

expect(secondMessageSubject).to.eql('Example 2')

If you try to create a full empty object to bind it to forms/views, then the way above wont work. You need the special option unfold: true like this:

// Previous behaviour, parse subtypes but conform the defaults (do not expand
// empty properties to its subtypes
var inbox1 = new Inbox(null, { parse: true })


// If we want the subtypes to be parsed and unfolded
var inbox2 = new Inbox(null, { parse: true, unfold: true })

var owner = inbox2.get('owner')
  , messages = inbox2.get('messages')


Mixin objects

Backbone provides for its types the extend method to create class hierarchies.

This is very convenient, but very convenient also is taking advantage of javascript and using mixins to extract functionality that is independent and common through classes but does not relate to them in a hierarchical way.

All types from basics have a mixin method that allows them to mixin with JS objects that contain variables/functions that encapsulate functionality. The mixin method is added to the types, not the instances.

You can use it like this:

 * Mixin asOneTimeModal
 * Makes a view behave as a one time modal when calling a `show` method.
 * Mixes a `show` method, when the modal is closed the view will be
 * automatically removed.
 * Mixes a `hide` method, that will hide the modal and remove the view
 * afterwards
 * It also mixes a template for the modal as `modalTemplate`
var asOneTimeModal = {
  modalTemplate: _.template(modalTemplateSource),
  events: {
    'click .modal-header .close'    : 'hide',
    'click .modal-footer .btn-close': 'hide'
  show: function() {
    var $m = this.$('.modal').modal({})
    $m.on('hidden', _.bind(this.remove, this))
  hide: function() {

 * Sample View AddPerson
 * This would be a add person view with a form, and we want it to act as
 * a modal using our mixin
var AddPersonView = Basics.View.extend({
  events: {
    'click .submitModal': 'addPersonClick'
  initialize: function(options) {
    // [...] Here goes code
  // [...] Here go methods and event handlers
  addPersonClick: function(event) {
    // [...]

var newGuy = new Person()
var addPersonForm = new AddPersonView({ model: newGuy })

// Now the add person form behaves as a modal, and that functionality can be
// reused in any type even if they are not connected // > Shows the modal on the page

The same ideas can be applied to models and collections. For example to create Pageable collections, lazy loading models, etc. There may be some basic mixins included in Basics in the future to be mixed with the basics types.


From a browserify enabled client side module

If you are developing a module or application and using browserify as a module loader, then just include backbone-basics on the package.json as a dependency, and require it normally.

From a server side node.js module

Same as above. Declare the dependency on the package.json of your module/app and require it normally.

From a browser side application that does NOT use browserify

You have to grab the file browser/backbone-basics.js or browser/backbone-basics-min.js and include it on your page after the required dependencies. It will define a global variable on the window object called Basics, that you can use then normally.


To get the dependencies do a npm install

Source is on the src folder.

Tests on the test folder.

Make actions:

  • Compile: make compile
  • Test: make test
  • Tests watcher: make test-w


At the root of the source there is a TODO file.