Make your Backbone.js apps dance with a composite application architecture!
Backbone.Marionette is designed to be a lightweight and flexible library of tools that you can use when you want to. Like Backbone.js itself, you're not required to use all of Backbone.Marionette just because you want to use some of it.
Source Code And Downloads
You can download the raw source code from the "src" folder above, or grab one of the many builds from the "lib" folder.
To get the latest stable release, use these links which point to the 'master' branch's builds:
RequireJS (AMD) Builds
Marionette is unofficially available from various package management systems, such as RubyGems, Node Package Manager, Nuget, etc. These packages are maintained by the community and are not part of the core Backbone.Marionette code.
Marionette needs your support, but not everyone can offer assitance with code, bug submissions, and answering questions. If you're using Marionette and you're finding that it is saving you as much time and effort as I believe it does, then please consider financial support for the project.
Documentation And Support
The primary documentation has been moved in to a separate file apidoc.md, in order to reduce the file size and prevent rendering and formatting errors.
The Marionette Wiki
A wiki is an important aspect of a thriving community, as it provides a place for the community to contribute ideas, examples, answer frequently asked questions, and more. If you're looking for community-driven information, examples that go beyond the dry technical documentation, or want to contribute your own ideas and examples to the community, please see the wiki page.
Annotated Source Code
In addition to this readme, I've commented the source code quite heavily and run it through Docco as part of my build process. This produces a nicely formatted, annotated source code as documenation file.
You can read the annotated for all the detail of how Marionette works, and advice on which methods to override when.
Lastly, I blog about Marionette on a regular basis, at my LosTechies.com blog.
Help With Code And Questions
If you're interested in helping with code and questions, please see the issues list and stack overflow tag here:
If you have an idea to improve Marionette or want to report a bug, please use the issues list.
Compatibility And Requirements
Theses libraries are required for the use, development, testing and documentation of Backbone.Marionette.
Backbone.Marionette currently works with the following versions of these libraries:
- Backbone v0.9.2
- Underscore v1.3.3
- jQuery v1.7.2
While support for Zepto and Enderjs has been added, it is not officially tested against these libraries at this time.
Marionette has not been tested against any other versions of these libraries. You may or may not have success if you use a version other than what it listed here.
Build Tools Used
I use a number of tools to build, test and maintain Marionette, including but not limited to:
The Anvil.js project is used
to generate the builds for Backbone.Marionette. You can run the
build.sh file from a terminal, or the
build.cmd file for Windows
users, after installing anvil.
To get the test suite up and running, you need a Ruby installation with the
latest RubyGems. Install the 'bundler' gem and then run 'bundle install' from
the project's root folder. Then run
rake jasmine to run the test suite, and
load up http://localhost:8888 to see the test suite in action.
Annotated Source Code
I'm using Docco to generate the annotated source code.
- Fixed: A call to
.modulewill correctly pass the
Applicationinstance from which
.modulewas called, as the second parameter of the module definition function
- Module definitions can be split across multiple files and/or multiple calls to define the module
- Views now have the ability to define
triggerswhich will convert a DOM event in to a
- Module definition functions will only be applied to the last module in the . chain
- Added modules and sub-modules through the Application object
itemViewinstance as part of a Collection View or Composite View, will have it's events bubbled up through the parent view, prepended with "itemview:" as the event name
onBeforemethod of ItemView can now return a deferred object
- Code cleanup for rendering methods
- Fixed issue with
unbindAllin BindTo, that was skipping some items
bindTomethod on the
EventAggregatornow returns a binding configuration object
- Automatic mixing in of
templateMethodsas template / view helper methods, in views that use the
- A friendlier error message will be thrown from an appRouter if a route is configured with a method that does not exist on the controller
compileTemplatemethod in TemplateCache for clarity and easier modification
- ItemView will wait until
onRenderhas completed before triggering other rendered events
- Region now supports an
onShowmethod, when defining a custom region
- Moved the default
serializeDatamethod to the base Marionette.View
- CompositeView now calls the
serializeDatamethod to get the model's data for the view
bindTomethod returns a "binding" object so that it can be unbound easily
- Now has an
unbindFrommethod that will unbind a binding object
- ItemView now has a
renderHtmlmethod that can be overriden to render the item view's data
- Region now supports an
initializefunction when extending a region to your own object type
- CollectionView correctly defers until all children are rendered
- Underscore templates are cached as pre-compiled templates, instead of re-compiling them on every render
- Updating AMD support to also work with CommonJS / NodeJS
- Correctiong build to include header / license info for all output files
- Pass JSLint with no warnings (run w/ Anvil.js build process)
- Removed GZip release files, as they were broken anyways
- BREAKING: The
renderTemplatemethod has moved from the
ItemViewprototype on to the
- BREAKING: The
appendHtmlmethod of the
collectionView, itemViewas the arguments, instead of
Marionette.Viewobject, to contain a few basic parts of every Marionette view
Marionette.Rendererobject, to handle template rendering
- Views correctly trigger the "close" events before unbinding event subscribers
getItemViewmethod to retrieve the
itemViewtype, either from
buildItemViewmethod to build each item's view
removeItemViewto make the language consistent
- Triggers "item:added" event after each item has been added
- Triggers "item:removed" event after an item has been removed
- No longer takes a
modelView. Now directly renders the
- Defaults to a recurive structure, where
itemViewis the current composite view type
- No longer takes a
Regionwill trigger a
showevent from any view that it shows
- Added common "render" event to all the view types
- Updated to Backbone v0.9.2
- Updated to jQuery v1.7.2
- AMD / RequireJS compliant version is provided
- Now using Anvil.js for builds
For older change logs and release notes, see the changelog file.
Legal Mumbo Jumbo (MIT License)
Copyright (c) 2012 Derick Bailey, Muted Solutions, LLC
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.