Advanced URL Catalog.1.21 serial key or number

manicapital.com gives structure to web applications by providing models with key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing API over a RESTful JSON interface.

The project is hosted on GitHub, and the annotated source code is available, as well as an online test suite, an example application, a list of tutorials and a long list of real-world projects that use Backbone. Backbone is available for use under the MIT software license.

You can report bugs and discuss features on the GitHub issues page, or add pages to the wiki.

Backbone is an open-source component of DocumentCloud.

Downloads & Dependencies (Right-click, and use "Save As")

Backbone's only hard dependency is manicapital.com( >= ). For RESTful persistence and DOM manipulation with manicapital.com, include jQuery ( >= ). (Mimics of the Underscore and jQuery APIs, such as Lodash and Zepto, will also tend to work, with varying degrees of compatibility.)

Getting Started

When working on a web application that involves a lot of JavaScript, one of the first things you learn is to stop tying your data to the DOM. It's all too easy to create JavaScript applications that end up as tangled piles of jQuery selectors and callbacks, all trying frantically to keep data in sync between the HTML UI, your JavaScript logic, and the database on your server. For rich client-side applications, a more structured approach is often helpful.

With Backbone, you represent your data as Models, which can be created, validated, destroyed, and saved to the server. Whenever a UI action causes an attribute of a model to change, the model triggers a "change" event; all the Views that display the model's state can be notified of the change, so that they are able to respond accordingly, re-rendering themselves with the new information. In a finished Backbone app, you don't have to write the glue code that looks into the DOM to find an element with a specific id, and update the HTML manually — when the model changes, the views simply update themselves.

Philosophically, Backbone is an attempt to discover the minimal set of data-structuring (models and collections) and user interface (views and URLs) primitives that are generally useful when building web applications with JavaScript. In an ecosystem where overarching, decides-everything-for-you frameworks are commonplace, and many libraries require your site to be reorganized to suit their look, feel, and default behavior — Backbone should continue to be a tool that gives you the freedom to design the full experience of your web application.

If you're new here, and aren't yet quite sure what Backbone is for, start by browsing the list of Backbone-based projects.

Many of the code examples in this documentation are runnable, because Backbone is included on this page. Click the play button to execute them.

Models and Views

The single most important thing that Backbone can help you with is keeping your business logic separate from your user interface. When the two are entangled, change is hard; when logic doesn't depend on UI, your interface becomes easier to work with.

A Model manages an internal table of data attributes, and triggers events when any of its data is modified. Models handle syncing data with a persistence layer — usually a REST API with a backing database. Design your models as the atomic reusable objects containing all of the helpful functions for manipulating their particular bit of data. Models should be able to be passed around throughout your app, and used anywhere that bit of data is needed.

A View is an atomic chunk of user interface. It often renders the data from a specific model, or number of models — but views can also be data-less chunks of UI that stand alone. Models should be generally unaware of views. Instead, views listen to the model events, and react or re-render themselves appropriately.

Collections

A Collection helps you deal with a group of related models, handling the loading and saving of new models to the server and providing helper functions for performing aggregations or computations against a list of models. Aside from their own events, collections also proxy through all of the events that occur to models within them, allowing you to listen in one place for any change that might happen to any model in the collection.

API Integration

Backbone is pre-configured to sync with a RESTful API. Simply create a new Collection with the of your resource endpoint:

The Collection and Model components together form a direct mapping of REST resources using the following methods:

When fetching raw JSON data from an API, a Collection will automatically populate itself with data formatted as an array, while a Model will automatically populate itself with data formatted as an object:

However, it's fairly common to encounter APIs that return data in a different format than what Backbone expects. For example, consider fetching a Collection from an API that returns the real data array wrapped in metadata:

In the above example data, a Collection should populate using the array rather than the root object structure. This difference is easily reconciled using a method that returns (or transforms) the desired portion of API data:

View Rendering

Each View manages the rendering and user interaction within its own DOM element. If you're strict about not allowing views to reach outside of themselves, it helps keep your interface flexible — allowing views to be rendered in isolation in any place where they might be needed.

Backbone remains unopinionated about the process used to render View objects and their subviews into UI: you define how your models get translated into HTML (or SVG, or Canvas, or something even more exotic). It could be as prosaic as a simple Underscore template, or as fancy as the React virtual DOM. Some basic approaches to rendering views can be found in the Backbone primer.

Routing with URLs

In rich web applications, we still want to provide linkable, bookmarkable, and shareable URLs to meaningful locations within an app. Use the Router to update the browser URL whenever the user reaches a new "place" in your app that they might want to bookmark or share. Conversely, the Router detects changes to the URL — say, pressing the "Back" button — and can tell your application exactly where you are now.

manicapital.com

Events is a module that can be mixed in to any object, giving the object the ability to bind and trigger custom named events. Events do not have to be declared before they are bound, and may take passed arguments. For example:

For example, to make a handy event dispatcher that can coordinate events among different areas of your application:

onAlias: bind
Bind a callback function to an object. The callback will be invoked whenever the event is fired. If you have a large number of different events on a page, the convention is to use colons to namespace them: , or . The event string may also be a space-delimited list of several events

Callbacks bound to the special event will be triggered when any event occurs, and are passed the name of the event as the first argument. For example, to proxy all events from one object to another:

All Backbone event methods also support an event map syntax, as an alternative to positional arguments:

To supply a context value for when the callback is invoked, pass the optional last argument: or .

offAlias: unbind
Remove a previously-bound callback function from an object. If no context is specified, all of the versions of the callback with different contexts will be removed. If no callback is specified, all callbacks for the event will be removed. If no event is specified, callbacks for all events will be removed.

Note that calling , for example, will indeed remove all events on the model — including events that Backbone uses for internal bookkeeping.

trigger
Trigger callbacks for the given event, or space-delimited list of events. Subsequent arguments to trigger will be passed along to the event callbacks.

once
Just like on, but causes the bound callback to fire only once before being removed. Handy for saying "the next time that X happens, do this". When multiple events are passed in using the space separated syntax, the event will fire once for every event you passed in, not once for a combination of all events

listenTo
Tell an object to listen to a particular event on an other object. The advantage of using this form, instead of , is that listenTo allows the object to keep track of the events, and they can be removed all at once later on. The callback will always be called with object as context.

stopListening
Tell an object to stop listening to events. Either call stopListening with no arguments to have the object remove all of its registered callbacks or be more precise by telling it to remove just the events it's listening to on a specific object, or a specific event, or just a specific callback.

listenToOnce
Just like listenTo, but causes the bound callback to fire only once before being removed.

Catalog of Events
Here's the complete list of built-in Backbone events, with arguments. You're also free to trigger your own events on Models, Collections and Views as you see fit. The object itself mixes in , and can be used to emit any global events that your application needs.

• "add" (model, collection, options) — when a model is added to a collection.
• "remove" (model, collection, options) — when a model is removed from a collection.
• "update" (collection, options) — single event triggered after any number of models have been added, removed or changed in a collection.
• "reset" (collection, options) — when the collection's entire contents have been reset.
• "sort" (collection, options) — when the collection has been re-sorted.
• "change" (model, options) — when a model's attributes have changed.
• "change:[attribute]" (model, value, options) — when a specific attribute has been updated.
• "destroy" (model, collection, options) — when a model is destroyed.
• "request" (model_or_collection, xhr, options) — when a model or collection has started a request to the server.
• "sync" (model_or_collection, response, options) — when a model or collection has been successfully synced with the server.
• "error" (model_or_collection, xhr, options) — when a model's or collection's request to the server has failed.
• "invalid" (model, error, options) — when a model's validation fails on the client.
• "route:[name]" (params) — Fired by the router when a specific route is matched.
• "route" (route, params) — Fired by the router when any route has been matched.
• "route" (router, route, params) — Fired by history when any route has been matched.
• "all" — this special event fires for any triggered event, passing the event name as the first argument followed by all trigger arguments.

Generally speaking, when calling a function that emits an event (, , and so on), if you'd like to prevent the event from being triggered, you may pass as an option. Note that this is rarely, perhaps even never, a good idea. Passing through a specific flag in the options for your event callback to look at, and choose to ignore, will usually work out better.

manicapital.com

Models are the heart of any JavaScript application, containing the interactive data as well as a large part of the logic surrounding it: conversions, validations, computed properties, and access control. You extend manicapital.com with your domain-specific methods, and Model provides a basic set of functionality for managing changes.

The following is a contrived example, but it demonstrates defining a model with a custom method, setting an attribute, and firing an event keyed to changes in that specific attribute. After running this code once, will be available in your browser's console, so you can play around with it.

extend
To create a Model class of your own, you extend manicapital.com and provide instance properties, as well as optional classProperties to be attached directly to the constructor function.

extend correctly sets up the prototype chain, so subclasses created with extend can be further extended and subclassed as far as you like.

Brief aside on : JavaScript does not provide a simple way to call super — the function of the same name defined higher on the prototype chain. If you override a core function like , or , and you want to invoke the parent object's implementation, you'll have to explicitly call it, along these lines:

preinitialize
For use with models as ES classes. If you define a preinitialize method, it will be invoked when the Model is first created, before any instantiation logic is run for the Model.

constructor / initialize
When creating an instance of a model, you can pass in the initial values of the attributes, which will be set on the model. If you define an initialize function, it will be invoked when the model is created.

In rare cases, if you're looking to get fancy, you may want to override constructor, which allows you to replace the actual constructor function for your model.

If you pass a as the options, the model gains a property that will be used to indicate which collection the model belongs to, and is used to help compute the model's url. The property is normally created automatically when you first add a model to a collection. Note that the reverse is not true, as passing this option to the constructor will not automatically add the model to the collection. Useful, sometimes.

If is passed as an option, the attributes will first be converted by parse before being set on the model.

get
Get the current value of an attribute from the model. For example:

set
Set a hash of attributes (one or many) on the model. If any of the attributes change the model's state, a event will be triggered on the model. Change events for specific attributes are also triggered, and you can bind to those as well, for example: , and . You may also pass individual keys and values.

escape
Similar to get, but returns the HTML-escaped version of a model's attribute. If you're interpolating data from the model into HTML, using escape to retrieve attributes will prevent XSS attacks.

has
Returns if the attribute is set to a non-null or non-undefined value.

unset
Remove an attribute by deleting it from the internal attributes hash. Fires a event unless is passed as an option.

clear
Removes all attributes from the model, including the attribute. Fires a event unless is passed as an option.

id
A special property of models, the id is an arbitrary string (integer id or UUID). If you set the id in the attributes hash, it will be copied onto the model as a direct property. should not be manipulated directly, it should be modified only via . Models can be retrieved by id from collections, and the id is used to generate model URLs by default.

idAttribute
A model's unique identifier is stored under the attribute. If you're directly communicating with a backend (CouchDB, MongoDB) that uses a different unique key, you may set a Model's to transparently map from that key to .

cid
A special property of models, the cid or client id is a unique identifier automatically assigned to all models when they're first created. Client ids are handy when the model has not yet been saved to the server, and does not yet have its eventual true id, but already needs to be visible in the UI.

attributes
The attributes property is the internal hash containing the model's state — usually (but not necessarily) a form of the JSON object representing the model data on the server. It's often a straightforward serialization of a row from the database, but it could also be client-side computed state.

Please use set to update the attributes instead of modifying them directly. If you'd like to retrieve and munge a copy of the model's attributes, use instead.

Due to the fact that Events accepts space separated lists of events, attribute names should not include spaces.

changed
The changed property is the internal hash containing all the attributes that have changed since its last set. Please do not update changed directly since its state is internally maintained by set. A copy of changed can be acquired from changedAttributes.

defaults
The defaults hash (or function) can be used to specify the default attributes for your model. When creating an instance of the model, any unspecified attributes will be set to their default value.

Remember that in JavaScript, objects are passed by reference, so if you include an object as a default value, it will be shared among all instances. Instead, define defaults as a function.

toJSON
Return a shallow copy of the model's attributes for JSON stringification. This can be used for persistence, serialization, or for augmentation before being sent to the server. The name of this method is a bit confusing, as it doesn't actually return a JSON string — but I'm afraid that it's the way that the JavaScript API for manicapital.comify works.

sync
Uses manicapital.com to persist the state of a model to the server. Can be overridden for custom behavior.

fetch
Merges the model's state with attributes fetched from the server by delegating to manicapital.com Returns a jqXHR. Useful if the model has never been populated with data, or if you'd like to ensure that you have the latest server state. Triggers a event if the server's state differs from the current attributes. accepts and callbacks in the options hash, which are both passed as arguments.

save
Save a model to your database (or alternative persistence layer), by delegating to manicapital.com Returns a jqXHR if validation is successful and otherwise. The attributes hash (as in set) should contain the attributes you'd like to change — keys that aren't mentioned won't be altered — but, a complete representation of the resource will be sent to the server. As with , you may pass individual keys and values instead of a hash. If the model has a validate method, and validation fails, the model will not be saved. If the model isNew, the save will be a (HTTP ), if the model already exists on the server, the save will be an (HTTP ).

If instead, you'd only like the changed attributes to be sent to the server, call . You'll get an HTTP request to the server with just the passed-in attributes.

Calling with new attributes will cause a event immediately, a event as the Ajax request begins to go to the server, and a event after the server has acknowledged the successful change. Pass if you'd like to wait for the server before setting the new attributes on the model.

In the following example, notice how our overridden version of receives a request the first time the model is saved and an request the second time.

save accepts and callbacks in the options hash, which will be passed the arguments . If a server-side validation fails, return a non- HTTP response code, along with an error response in text or JSON.

destroy
Destroys the model on the server by delegating an HTTP request to manicapital.com Returns a jqXHR object, or if the model isNew. Accepts and callbacks in the options hash, which will be passed . Triggers a event on the model, which will bubble up through any collections that contain it, a event as it begins the Ajax request to the server, and a event, after the server has successfully acknowledged the model's deletion. Pass if you'd like to wait for the server to respond before removing the model from the collection.

Underscore Methods (9)
Backbone proxies to manicapital.com to provide 9 object functions on manicapital.com. They aren't all documented here, but you can take a look at the Underscore documentation for the full details…

validate
This method is left undefined and you're encouraged to override it with any custom validation logic you have that can be performed in JavaScript. If the attributes are valid, don't return anything from validate; if they are invalid return an error of your choosing. It can be as simple as a string error message to be displayed, or a complete error object that describes the error programmatically.

By default checks validate before setting any attributes but you may also tell to validate the new attributes by passing as an option. The validate method receives the model attributes as well as any options passed to or , if validate returns an error, does not continue, the model attributes are not modified on the server, an event is triggered, and the property is set on the model with the value returned by this method.

events are useful for providing coarse-grained error messages at the model or collection level.

validationError
The value returned by validate during the last failed validation.

isValid
Run validate to check the model state.

The method receives the model attributes as well as any options passed to isValid, if returns an error an event is triggered, and the error is set on the model in the property.

url
Returns the relative URL where the model's resource would be located on the server. If your models are located somewhere else, override this method with the correct logic. Generates URLs of the form: by default, but you may override by specifying an explicit if the model's collection shouldn't be taken into account.

Delegates to Collection#url to generate the URL, so make sure that you have it defined, or a urlRoot property, if all models of this class share a common root URL. A model with an id of , stored in a manicapital.comtion with a of , would have this URL:

urlRoot
Specify a if you're using a model outside of a collection, to enable the default url function to generate URLs based on the model id.
Normally, you won't need to define this. Note that may also be a function.

parse
parse is called whenever a model's data is returned by the server, in fetch, and save. The function is passed the raw object, and should return the attributes hash to be set on the model. The default implementation is a no-op, simply passing through the JSON response. Override this if you need to work with a preexisting API, or better namespace your responses.

If you're working with a Rails backend that has a version prior to , you'll notice that its default implementation includes a model's attributes under a namespace. To disable this behavior for seamless Backbone integration, set:

clone
Returns a new instance of the model with identical attributes.

isNew
Has this model been saved to the server yet? If the model does not yet have an , it is considered to be new.

hasChanged
Has the model changed since its last set? If an attribute is passed, returns if that specific attribute has changed.

Note that this method, and the following change-related ones, are only useful during the course of a event.

changedAttributes
Retrieve a hash of only the model's attributes that have changed since the last set, or if there are none. Optionally, an external attributes hash can be passed in, returning the attributes in that hash which differ from the model. This can be used to figure out which portions of a view should be updated, or what calls need to be made to sync the changes to the server.

previous
During a event, this method can be used to get the previous value of a changed attribute.

previousAttributes
Return a copy of the model's previous attributes. Useful for getting a diff between versions of a model, or getting back to a valid state after an error occurs.

manicapital.comtion

Collections are ordered sets of models. You can bind events to be notified when any model in the collection has been modified, listen for and events, the collection from the server, and use a full suite of manicapital.com methods.

Any event that is triggered on a model in a collection will also be triggered on the collection directly, for convenience. This allows you to listen for changes to specific attributes in any model in a collection, for example:

extend
To create a Collection class of your own, extend manicapital.comtion, providing instance properties, as well as optional classProperties to be attached directly to the collection's constructor function.

model
Override this property to specify the model class that the collection contains. If defined, you can pass raw attributes objects (and arrays) and options to add, create, and reset, and the attributes will be converted into a model of the proper type using the provided options, if any.

A collection can also contain polymorphic models by overriding this property with a constructor that returns a model.

modelId
Override this method to return the value the collection will use to identify a model given its attributes. Useful for combining models from multiple tables with different values into a single collection.

By default returns the value of the attributes' from the collection's model class or failing that, . If your collection uses a model factory and those models have an other than you must override this method.

preinitialize
For use with collections as ES classes. If you define a preinitialize method, it will be invoked when the Collection is first created and before any instantiation logic is run for the Collection.

constructor / initialize
When creating a Collection, you may choose to pass in the initial array of models. The collection's comparator may be included as an option. Passing as the comparator option will prevent sorting. If you define an initialize function, it will be invoked when the collection is created. There are a couple of options that, if provided, are attached to the collection directly: and .
Pass for to create an empty Collection with .

models
Raw access to the JavaScript array of models inside of the collection. Usually you'll want to use , , or the Underscore methods to access model objects, but occasionally a direct reference to the array is desired.

toJSON
Return an array containing the attributes hash of each model (via toJSON) in the collection. This can be used to serialize and persist the collection as a whole. The name of this method is a bit confusing, because it conforms to JavaScript's JSON API.

sync
Uses manicapital.com to persist the state of a collection to the server. Can be overridden for custom behavior.

Underscore Methods (46)
Backbone proxies to manicapital.com to provide 46 iteration functions on manicapital.comtion. They aren't all documented here, but you can take a look at the Underscore documentation for the full details…

Most methods can take an object or string to support model-attribute-style predicates or a function that receives the model instance as an argument.

add
Add a model (or an array of models) to the collection, firing an event for each model, and an event afterwards. If a model property is defined, you may also pass raw attributes objects and options, and have them be vivified as instances of the model using the provided options. Returns the added (or preexisting, if duplicate) models. Pass to splice the model into the collection at the specified . If you're adding models to the collection that are already in the collection, they'll be ignored, unless you pass , in which case their attributes will be merged into the corresponding models, firing any appropriate events.

Note that adding the same model (a model with the same ) to a collection more than once
is a no-op.

remove
Remove a model (or an array of models) from the collection, and return them. Each model can be a Model instance, an string or a JS object, any value acceptable as the argument of . Fires a event for each model, and a single event afterwards, unless is passed. The model's index before removal is available to listeners as .

reset
Adding and removing models one at a time is all well and good, but sometimes you have so many models to change that you'd rather just update the collection in bulk. Use reset to replace a collection with a new list of models (or attribute hashes), triggering a single event on completion, and without triggering any add or remove events on any models. Returns the newly-set models. For convenience, within a event, the list of any previous models is available as .
Pass for to empty your Collection with .

Here's an example using reset to bootstrap a collection during initial page load, in a Rails application:

Calling without passing any models as arguments will empty the entire collection.

set
The set method performs a "smart" update of the collection with the passed list of models. If a model in the list isn't yet in the collection it will be added; if the model is already in the collection its attributes will be merged; and if the collection contains any models that aren't present in the list, they'll be removed. All of the appropriate , , and events are fired as this happens. Returns the touched models in the collection. If you'd like to customize the behavior, you can disable it with options: , , or .

get
Get a model from a collection, specified by an id, a cid, or by passing in a model.

at
Get a model from a collection, specified by index. Useful if your collection is sorted, and if your collection isn't sorted, at will still retrieve models in insertion order. When passed a negative index, it will retrieve the model from the back of the collection.

push
Add a model at the end of a collection. Takes the same options as add.

pop
Remove and return the last model from a collection. Takes the same options as remove.

unshift
Add a model at the beginning of a collection. Takes the same options as add.

shift
Remove and return the first model from a collection. Takes the same options as remove.

slice
Return a shallow copy of this collection's models, using the same options as native Array#slice.

length
Like an array, a Collection maintains a property, counting the number of models it contains.

comparator
By default there is no comparator for a collection. If you define a comparator, it will be used to sort the collection any time a model is added. A comparator can be defined as a sortBy (pass a function that takes a single argument), as a sort (pass a comparator function that expects two arguments), or as a string indicating the attribute to sort by.

"sortBy" comparator functions take a model and return a numeric or string value by which the model should be ordered relative to others. "sort" comparator functions take two models, and return if the first model should come before the second, if they are of the same rank and if the first model should come after. Note that Backbone depends on the arity of your comparator function to determine between the two styles, so be careful if your comparator function is bound.

Note how even though all of the chapters in this example are added backwards, they come out in the proper order:

Collections with a comparator will not automatically re-sort if you later change model attributes, so you may wish to call after changing model attributes that would affect the order.

sort
Force a collection to re-sort itself. Note that a collection with a comparator will sort itself automatically whenever a model is added. To disable sorting when adding a model, pass to . Calling sort triggers a event on the collection.

pluck
Pluck an attribute from each model in the collection. Equivalent to calling and returning a single attribute from the iterator.

where
Return an array of all the models in a collection that match the passed attributes. Useful for simple cases of .

findWhere
Just like where, but directly returns only the first model in the collection that matches the passed attributes. If no model matches returns .

url
Set the url property (or function) on a collection to reference its location on the server. Models within the collection will use url to construct URLs of their own.

parse
parse is called by Backbone whenever a collection's models are returned by the server, in fetch. The function is passed the raw object, and should return the array of model attributes to be added to the collection. The default implementation is a no-op, simply passing through the JSON response. Override this if you need to work with a preexisting API, or better namespace your responses.

clone
Returns a new instance of the collection with an identical list of models.

fetch
Fetch the default set of models for this collection from the server, setting them on the collection when they arrive. The options hash takes and callbacks which will both be passed as arguments. When the model data returns from the server, it uses set to (intelligently) merge the fetched models, unless you pass , in which case the collection will be (efficiently) reset. Delegates to manicapital.com under the covers for custom persistence strategies and returns a jqXHR. The server handler for fetch requests should return a JSON array of models.

The behavior of fetch can be customized by using the available set options. For example, to fetch a collection, getting an event for every new model, and a event for every changed existing model, without removing anything:

manicapital.com options can also be passed directly as fetch options, so to fetch a specific page of a paginated collection:

Note that fetch should not be used to populate collections on page load — all models needed at load time should already be bootstrapped in to place. fetch is intended for lazily-loading models for interfaces that are not needed immediately: for example, documents with collections of notes that may be toggled open and closed.

create
Convenience to create a new instance of a model within a collection. Equivalent to instantiating a model with a hash of attributes, saving the model to the server, and adding the model to the set after being successfully created. Returns the new model. If client-side validation failed, the model will be unsaved, with validation errors. In order for this to work, you should set the model property of the collection. The create method can accept either an attributes hash and options to be passed down during model instantiation or an existing, unsaved model object.

Creating a model will cause an immediate event to be triggered on the collection, a event as the new model is sent to the server, as well as a event, once the server has responded with the successful creation of the model. Pass if you'd like to wait for the server before adding the new model to the collection.

mixin
provides a way to enhance the base manicapital.comtion and any collections which extend it. This can be used to add generic methods (e.g. additional Underscore Methods).

manicapital.com

Web applications often provide linkable, bookmarkable, shareable URLs for important locations in the app. Until recently, hash fragments () were used to provide these permalinks, but with the arrival of the History API, it's now possible to use standard URLs (). manicapital.com provides methods for routing client-side pages, and connecting them to actions and events. For browsers which don't yet support the History API, the Router handles graceful fallback and transparent translation to the fragment version of the URL.

During page load, after your application has finished creating all of its routers, be sure to call or to route the initial URL.

extend
Get started by creating a custom router class. Define action functions that are triggered when certain URL fragments are matched, and provide a routes hash that pairs routes to actions. Note that you'll want to avoid using a leading slash in your route definitions:

routes
The routes hash maps URLs with parameters to functions on your router (or just direct function definitions, if you prefer), similar to the View's events hash. Routes can contain parameter parts, , which match a single URL component between slashes; and splat parts , which can match any number of URL components. Part of a route can be made optional by surrounding it in parentheses .

For example, a route of will match a fragment of , passing and to the action as positional arguments.

A route of will match , passing to the action.

A route of will match and , passing to the action in the first case, and passing and to the action in the second.

A nested optional route of will match , , and , passing to the action in the second case, and passing and to the action in the third.

Trailing slashes are treated as part of the URL, and (correctly) treated as a unique route when accessed. and will fire different callbacks. If you can't avoid generating both types of URLs, you can define a matcher to capture both cases.

When the visitor presses the back button, or enters a URL, and a particular route is matched, the name of the action will be fired as an event, so that other objects can listen to the router, and be notified. In the following example, visiting will fire a event from the router.

preinitialize
For use with routers as ES classes. If you define a preinitialize method, it will be invoked when the Router is first created and before any instantiation logic is run for the Router.

constructor / initialize
When creating a new router, you may pass its routes hash directly as an option, if you choose. All will also be passed to your function, if defined.

route
Manually create a route for the router, The argument may be a routing string or regular expression. Each matching capture from the route or regular expression will be passed as an argument to the callback. The argument will be triggered as a event whenever the route is matched. If the argument is omitted will be used instead. Routes added later may override previously declared routes.

navigate
Whenever you reach a point in your application that you'd like to save as a URL, call navigate in order to update the URL. If you also wish to call the route function, set the trigger option to . To update the URL without creating an entry in the browser's history, set the replace option to .

execute
This method is called internally within the router, whenever a route matches and its corresponding callback is about to be executed. Return false from execute to cancel the current transition. Override it to perform custom parsing or wrapping of your routes, for example, to parse query strings before handing them to your route callback, like so:

manicapital.comy

History serves as a global router (per frame) to handle events or , match the appropriate route, and trigger callbacks. You shouldn't ever have to create one of these yourself since already contains one.

pushState support exists on a purely opt-in basis in Backbone. Older browsers that don't support will continue to use hash-based URL fragments, and if a hash URL is visited by a -capable browser, it will be transparently upgraded to the true URL. Note that using real URLs requires your web server to be able to correctly render those pages, so back-end changes are required as well. For example, if you have a route of , your web server must be able to serve that page, if the browser visits that URL directly. For full search-engine crawlability, it's best to have the server generate the complete HTML for the page but if it's a web application, just rendering the same content you would have for the root URL, and filling in the rest with Backbone Views and JavaScript works fine.

start
When all of your Routers have been created, and all of the routes are set up properly, call to begin monitoring events, and dispatching routes. Subsequent calls to will throw an error, and is a boolean value indicating whether it has already been called.

To indicate that you'd like to use HTML5 support in your application, use . If you'd like to use , but have browsers that don't support it natively use full page refreshes instead, you can add to the options.

If your application is not being served from the root url of your domain, be sure to tell History where the root really is, as an option:

When called, if a route succeeds with a match for the current URL, returns . If no defined route matches the current URL, it returns .

If the server has already rendered the entire page, and you don't want the initial route to trigger when starting History, pass .

Because hash-based history in Internet Explorer relies on an , be sure to call only after the DOM is ready.

manicapital.com

manicapital.com is the function that Backbone calls every time it attempts to read or save a model to the server. By default, it uses to make a RESTful JSON request and returns a jqXHR. You can override it in order to use a different persistence strategy, such as WebSockets, XML transport, or Local Storage.

The method signature of manicapital.com is

• method – the CRUD method (, , , or )
• model – the model to be saved (or collection to be read)
• options – success and error callbacks, and all other jQuery request options

With the default implementation, when manicapital.com sends up a request to save a model, its attributes will be passed, serialized as JSON, and sent in the HTTP body with content-type . When returning a JSON response, send down the attributes of the model that have been changed by the server, and need to be updated on the client. When responding to a request from a collection (Collection#fetch), send down an array of model attribute objects.

Whenever a model or collection begins a sync with the server, a event is emitted. If the request completes successfully you'll get a event, and an event if not.

The sync function may be overridden globally as , or at a finer-grained level, by adding a function to a Backbone collection or to an individual model.

The default sync handler maps CRUD to REST like so:

• create → POST  
• read → GET  
• update → PUT  
• patch → PATCH  
• delete → DELETE  

As an example, a Rails 4 handler responding to an call from might look like this:

One more tip for integrating Rails versions prior to is to disable the default namespacing for calls on models by setting

ajax
If you want to use a custom AJAX function, or your endpoint doesn't support the manicapital.com API and you need to tweak things, you can do so by setting .

emulateHTTP
If you want to work with a legacy web server that doesn't support Backbone's default REST/HTTP approach, you may choose to turn on . Setting this option will fake , and

Oracle Database Standard Edition 2

On-Premise

SE2

Oracle Database Standard Edition 2 includes features necessary to develop workgroup, department-level, and Web applications.

Oracle Database Enterprise Edition

On-Premise

EE

Oracle Database Enterprise Edition provides performance, availability, scalability, and security for developing applications such as high-volume online transaction processing (OLTP) applications, query-intensive data warehouses, and demanding Internet applications.

Oracle Database Enterprise Edition can be enhanced with the purchase of Oracle Database options and Oracle management packs.

Oracle Database Enterprise Edition on Oracle Exadata Database Machine

On-Premise

EE-Exa

Oracle Database Enterprise Edition software installed on an on-premise Oracle Exadata Database Machine or an on-premise Oracle Supercluster.

Includes all of the components of Oracle Database. You can further enhance this offering with the purchase of Oracle Database options and Oracle management packs.

Oracle Database Personal Edition

On-Premise

PE

Oracle Database Personal Edition supports single-user development and deployment environments that require full compatibility with Oracle Database Standard Edition 2 and Oracle Database Enterprise Edition.

Includes all of the components that are included with Enterprise Edition, as well as all Oracle Database options, with the exception of the Oracle RAC One Node and Oracle Real Application Clusters options, which cannot be used with Personal Edition. Personal Edition is available on Linux and Windows platforms only. Oracle management packs cannot be used with Personal Edition.

Oracle Database Cloud Service Standard Edition

Cloud

DBCS SE

Includes Oracle Database Standard Edition 2 software.

Oracle Database Cloud Service Enterprise Edition

Cloud

DBCS EE

Includes Oracle Database Enterprise Edition software.

Oracle Database Cloud Service Enterprise Edition - High Performance

Cloud

DBCS EE-HP

Includes Oracle Database Enterprise Edition software plus many Oracle Database options and Oracle management packs.

Oracle Database Cloud Service Enterprise Edition - Extreme Performance

Cloud

DBCS EE-EP

Includes Oracle Database Enterprise Edition software plus all Oracle Database options and Oracle management packs that are appropriate for use in Oracle Database Cloud Service.

Oracle Database Exadata Cloud Service

Cloud

ExaCS

Includes Oracle Database Enterprise Edition software plus all Oracle Database options and Oracle management packs that are appropriate for use in Oracle Database Exadata Cloud Service.

The licensing policies for ExaCS also apply to Oracle Database Exadata Cloud at Customer.