v1.1 view commit logs
-
Marionette.View / All Views
- Fix for
ui
bindings to not be removed from view prototype, if unrendered view is closed - Template helpers can now be provided as a constructor function option
- Fix for
-
Layout
- Will properly attach regions if the layout's
close
method was called prior torender
- Calling
.addRegions
will correctly modify the layout instance' region list instead of the prototype's - Fixed bug that prevented default
regionType
from being used
- Will properly attach regions if the layout's
-
CompositeView
- The
itemViewContainer
can be supplied in the constructor function options
- The
-
Application
- Added
closeRegions
method to close all regions on the app instance - Added
getRegion
method to retrieve a region by name
- Added
-
AppRouter
- Added
appRoute
method to create app router handlers at runtime - Added ability to set
appRoutes
in constructor function options
- Added
-
Marionette.triggerMethod
- Calls to the
Marionette.triggerMethod
can be made on objects that do not have atrigger
method
- Calls to the
v1.0.4 view commit logs
-
ItemView
- Added needed
constructor
function back - it added lots of things and needed to be there
- Added needed
-
CompositeView
- Added explicit call to CollectionView constructor to allow for inheritance overriding
-
Layout
- Small clarification for consistency on call to ItemView constructor
v1.0.3 view commit logs
-
ItemView
- Deleted unneeded
constructor
function - it added nothing and didn't need to be there
- Deleted unneeded
-
CompositeView
- Added
index
parameter to method signature, to show that it is available - Deleted unneeded
constructor
function and removed call togetItemView
as it was causing problems and was not needed in the constructor.
- Added
-
All Views
- Fixed a bug in the entity and collection event bindings, where
stopListening
would not unbind the event handlers
- Fixed a bug in the entity and collection event bindings, where
-
Renderer / All Views
- The
Renderer.render
method will throw a more meaningful error if the supplied template is falsey
- The
-
Region
- Re-showing a closed view now works by re-rendering and re-inserting the view in to the DOM
- Region will trigger a
show
event when showing a view (updated the code to work like the docs already said) - Set the
currentView
before triggering theshow
events from the region / view
-
RegionManager
- Fixed a bug to decrement the
.length
when a region is removed
- Fixed a bug to decrement the
v1.0.2 view commit logs
-
UI Elements
- Fix bug to unbind them after the "close" event /
onClose
method, so theui
elements are available during these
- Fix bug to unbind them after the "close" event /
-
AppRouter
- Fix bug that was reversing the order of routes, causing the wrong route to be fired in many cases
v1.0.1 view commit logs
-
AMD build: Removed
require('jQuery')
as Marionette now pulledBackbone.$
asMarionette.$
. -
Fixed RegionManager to allow region types to be specified again, not just region instances.
-
NPM: Removed hard dependency on jQuery from the dependency list. This will be pulled in by other libs, or should be pulled in manually, to get the right version.
v1.0.0 view commit logs
-
RegionManager
- Created new
Marionette.RegionManager
object to manage a set of regions
- Created new
-
Region
- Region will call the
close
method on a view, or theremove
method ifclose
is not found, when closing a view - When calling the
show
method with the same view instance multiple times, subsequent calls will only re-render the view and not close / re-open it
- Region will call the
-
Application
- Now uses
Marionette.RegionManager
to manage regions
- Now uses
-
Layout
- Now uses
Marionette.RegionManager
to manage regions - Now supports dynamic add / remove of regions
- Can specify
regions
as a function that takes anoptions
argument (the view's constructor options)
- Now uses
-
CollectionView / CompositeView
- When specifying
itemViewOptions
as a function, an itemindex
argument will be passed as the second parameter - Will call the
close
orremove
method when closing a view, withclose
method taking precedence
- When specifying
-
CompositeView
- Fixed a bug that caused an error when the collection was
reset
(loaded) before the view was rendered
- Fixed a bug that caused an error when the collection was
-
All Views
- Closing a view will properly unbind
ui
elements - Closing and then re-rendering a view will re-bind the
ui
elements
- Closing a view will properly unbind
-
Functions
- Removed the
Marionette.createObject
function - it was never used by Marionette, directly
- Removed the
-
jQuery
- Replaced direct calls to
$
with newMarionette.$
, which is assigned toBackbone.$
for consistency w/ Backbone.
- Replaced direct calls to
-
Backbone.Wreqr
- Updated to v0.2.0
- Renamed
addHandler
method tosetHandler
- For more information, see the Wreqr changelog
-
Code Cleanup
- Replaced
that = this
with thecontext
param of several calls to_.each
to clean up the code - Removed an unused method from the CompositeView implementation
- Replaced
-
Build process
- Updated to Grunt v0.4.x
- Added code coverage and other analysis reports
v1.0.0-rc6 view commit logs
- CompositeView
- Corrected the timing of the "before:render" event /
onBeforeRender
callback, so that it will be called before serializing the data for the model / template
- Corrected the timing of the "before:render" event /
v1.0.0-rc5 view commit logs
- CollectionView / ItemView
- Corrected the timing on the "show" event /
onShow
callback for itemView instances that are added after the CollectionView is in the DOM
- Corrected the timing on the "show" event /
v1.0.0-rc4 view commit logs
-
EventBinder
- BREAKING: Removed
Marionette.addEventBinder
function.
- BREAKING: Removed
-
EventAggregator
- BREAKING: Removed
Marionette.EventAggregator
object. UseBackbone.Wreqr.EventAggregator
instead
- BREAKING: Removed
-
CollectionView / CompositeView
- Fixed several issues related to resetting the collection, and producing zombie "empty" views
- Fixed a bug that caused multiple emptyView instances when resetting the collection
- Forwarded events from child views are now called with
triggerMethod
, meaning they trigger the event and call the corresponding "onEventName" method
-
Modules
- Finalizers now run with the module as the
this
context
- Finalizers now run with the module as the
-
Marionette.getOption
- Fixed support for "falsey" values in an object's
options
- Fixed support for "falsey" values in an object's
-
Build process
- Fixed build process to work on case-sensitive file systems (Linux, for example)
v1.0.0-rc3 view commit logs
-
Updated Backbone v0.9.10
-
Updated jQuery to v1.9.0
- Fixed a few minor unit test issues w/ jQuery update
-
Read the upgrade guide for upgrading from v1.0.0-rc2 to v1.0.0-rc3
v1.0.0-rc3 view commit logs
-
IMPORTANT: Be sure to read the upgrade guide for upgrading from v1.0.0-rc2 to v1.0.0-rc3
-
Backbone v0.9.9
- BREAKING: Backbone v0.9.2 is no longer supported
- Backbone v0.9.9 is now supported
-
Marionette.Async
- BREAKING: Marionette.Async is no longer supported
-
Backbone.EventBinder / Marionette.EventBinder
- BREAKING: Marionette.EventBinder / Backbone.EventBinder have been removed entirely.
- Backbone.Events supercedes the older objects
- Backbone.Wreqr.EventAggregator also supercedes Marionette.EventBinder
-
EventBinder -> EventAggregator
- BREAKING: Backbone.Werqr.EventAggregator largely replaces Backbone.EventBinder
- BREAKING:
bindTo
has been replaced withlistenTo
- BREAKING:
unbindAll
has been replaced withstopListening
- BREAKING:
unbindFrom
has been removed and will not be replaced
-
Marionette.addEventBinder
- BREAKING: This function will mix in Backbone.Events to the target object if it does not exist
- BREAKING: This function will alter the
listenTo
method of the target to accept acontext
parameter as the 4th parameter of the method
-
All Views, Controller, etc
- BREAKING: Backbone.EventBinder is no longer mixed in
- BREAKING: See 'EventBinder -> EventAggregator' changes regarding method names to use for binding / unbinding events
-
CollectionView
- Added
removeChildView
to remove a specific view instance - Fixed event handler leak for child views that have been removed
- Changed the implementation for triggering the "show" event / "onShow" method call, to avoid memory leaks
- Fixed the
index
parameter for adding a model to the collection, and getting the view in to the right place
- Added
-
All Views
- BREAKING: The
initialEvents
method has been removed. Use theinitialize
method, thecollectionEvents
ormodelEvents
configuration instead. - Allow
modelEvents
andcollectionEvents
to be a function that returns a hash - Allow
ui
configuration to be a function that returns a hash modelEvents
andcollectionEvents
are now delegated / undelegated with Backbone.View's.delegateEvents
and.undelegateEvents
method calls- View
triggers
now include anargs
object withargs.view
,args.model
andargs.collection
- BREAKING: The
-
Modules
- Added alternate syntax for specifying
startWithParent
option - Fixed a bug where a module would not be started without an explicit definition for that module (#388 & #400)
- Added alternate syntax for specifying
v1.0.0-rc2 view commit logs
-
CollectionView / CompositeView
- **BREAKING: ** Changed the
item:added
event tobefore:item:added
andafter:item:added
- Fixed the
onShow
callbacks, so they can be used in theinitialize
method
- **BREAKING: ** Changed the
-
AMD build
- Fixed the AMD build by adding Backbone.BabySitter to the AMD dependency list
-
All Views
- All views (include Marionette.View) now have a "dom:refresh" and
onDomRefresh
event / method triggered
- All views (include Marionette.View) now have a "dom:refresh" and
v1.0.0-rc1 view commit logs
-
Fixed IE < 9 support w/ calls to
.apply
whenarguments
was null or undefined -
Module
- BREAKING: Renamed "initialize:before" event to "before:start", for consistency
- BREAKING: Renamed "initialize:after" event to "start", for consistency
- Triggers a "before:stop" event/method before the module is stopped
- Triggers a "stop" event/method after the module has been stopped
-
Marionette.View
- BREAKING: The
bindBackboneEntityTo
method has been removed from Marionette.View and replaced withMarionette.bindEntityEvents
function.
- BREAKING: The
-
Marionette.bindEntityEvents
- This function has been extracted from Marionette.View, and will bind an events hash to the events from an entity (model or collection), using the supplied EventBinder object (or any object with a bindTo method)
-
Marionette.EventBinder
- The context of the callback method defaults to the object w/ the
bindTo
method
- The context of the callback method defaults to the object w/ the
-
CollectionView / CompositeView
- The "item:added"/
onItemAdded
callback method are now fired after an item view has been rendered and added to it's parent collection view - The "itemview:" events - events that are forwarded from item views - can now have a custom prefix with the
itemViewEventPrefix
setting
- The "item:added"/
-
ItemView
- Added a "dom:refresh" event/callback method that fires after a view has been rendered, placed in the DOM with a Marionette.Region, and is re-rendered
-
All Views
- The
modelEvents
andcollectionEvents
can now have a function configured as the value in the{ "event:name": "value" }
configuration hash - A view that uses
bindTo
for its own "close" event will have it's close handler called correctly - Returning
false
from theonBeforeClose
method will prevent the view from being closed
- The
v1.0.0-beta6 view commit logs
-
CollectionView / CompositeView
- BREAKING: The
.children
attribute, used to store child views, is no longer an object literal. It is now an instance ofBackbone.ChildViewContainer
from Backbone.BabySitter - Updated to use Backbone.BabySitter to store and manage child views
- BREAKING: The
-
Controller
- Added a default
close
method to unbind all events on the controller instance and controller event binder - Trigger a "close"/onClose event/method when closing
- Fixed initialize method so
options
parameter is always a valid object
- Added a default
-
Modules
- Fixed an issue with grand-child modules being defined with a non-existent direct parent, and starting the top level parent directly
v1.0.0-beta5 view commit logs
- Modules
- Fixed the
startWithParent
option so that you only have to specifystartWithParent: false
once, no matter how many files the module definition is split in to
- Fixed the
v1.0.0-beta4 view commit logs
-
CollectionView / CompositeView
- BREAKING: Changed when the
itemViewOptions
gets called, in order to simplify thebuildItemView
method and make it easier to override - BREAKING: The
storeChild
method now requires an instance of the item being rendered, as well as the view that was rendered for it
- BREAKING: Changed when the
-
CompositeView / templateHelpers
- BREAKING: Fixed the
CompositeView
so thatserializeData
is no longer responsible for mixing in thetemplateHelpers
- BREAKING: Fixed the
-
Controller
- Added a very basic
Marionette.Controller
object, and basic documentation for it
- Added a very basic
-
Marionette.getOption
- Added a convience method to get an object's options either from the object directly, or from it's
this.options
, withthis.options
taking precedence - Converted use of
this.options
to useMarionette.getOption
through most of the code
- Added a convience method to get an object's options either from the object directly, or from it's
-
Marionette.createObject
- Added a convience method to create an object that inherits from another, as a wrapper / shim around
Object.create
- Added a convience method to create an object that inherits from another, as a wrapper / shim around
v1.0.0-beta3 view commit logs
- Region
- Fixed "show" method so that it includes the view instance being shown, again
v1.0.0-beta2 view commit logs
-
templateHelpers
- BREAKING: Changed when the templateHelpers is mixed in to the data for a view, so that it is no longer dependent on the
serializeData
implementation
- BREAKING: Changed when the templateHelpers is mixed in to the data for a view, so that it is no longer dependent on the
-
Region
- BREAKING: Changed "view:show" event to "show"
- BREAKING: Changed "view:closed" event to "close"
- All region events and events that the triggers from a view are now triggered via Marionette.triggerMethod.
-
Marionette.EventAggregator
- BREAKING: The
bindTo
method no longer assumes you are binding to the EventAggregator instance. You must specify the object that is triggering the event:ea.bindto(ea, "event", callback, context)
- Marionette.EventAggregator combines Backbone.Wreqr.EventAggregator with Backbone.EventBinder, allowing the event aggregator to act as it's own event binder
- BREAKING: The
-
CollectionView
- Fixed bug where adding an item to a collection would not allow the CollectionView to propagate the itemView's events
- Allow
itemViewOptions
to be specified in CollectionView constructor options
-
Application
- The events triggered from the Application object instance are now triggered with corresponding "on{EventName}" method calls
-
Backbone.EventBinder
- Updated to v0.1.0 of Backbone.EventBinder, allowing for jQuery/DOM events to be handled within the EventBinder instances /
bindTo
methods
- Updated to v0.1.0 of Backbone.EventBinder, allowing for jQuery/DOM events to be handled within the EventBinder instances /
-
AMD Wrapper
- The "core" AMD wrapper specifies Backbone.Wreqr and Backbone.EventBinder
- The "standard" AMD wrapper does not specify Backbone.Wreqr / EventBinder, as these are built in
-
Build / downloads
- The standard and AMD versions of
backbone.marionette.js
andbackbone.marionette.min.js
include all dependencies (EventBinder, Wreqr) - The "core" versions of
backbone.marionette.js
andbackbone.marionette.min.js
do not include any dependencies (EventBinder, Wreqr)
- The standard and AMD versions of
v1.0.0-beta1 view commit logs
-
Backbone.EventBinder
- BREAKING: Marionette's EventBinder has been extracted to the Backbone.EventBinder repository and plugin. You must include this file in your app, available at https://github.com/marionettejs/backbone.eventbinder
-
Backbone.Wreqr
- BREAKING: Marionette's EventAggregator has been extracted to the Backbone.Wreqr repository and plugin. You must include this file in your app, available at https://github.com/marionettejs/backbone.wreqr
-
All Views
- BREAKING:
beforeRender
method is nowonBeforeRender
- BREAKING:
beforeClose
method is nowonBeforeClose
- BREAKING: The
render
method for all Marionette views is bound to the view instance - All view events are now triggered with
triggerMethod
, calling their corresponding method on the view if it exists - All views now have an
isClosed
attribute on them, which is set totrue
when calling theclose()
method and reset tofalse
when calling therender()
method - EventBinder is now attached to the views with the
Marionette.addEventBinder
method call
- BREAKING:
-
CompositeView
- BREAKING: CompositeView will only render a model in to it's template, instead of a model or collection. It will still render the collection as itemView instances.
-
Modules
- BREAKING: Split module definitions can now receive custom args per module definition, instead of sharing / replacing them across all definitions
-
CollectionView / CompositeView
- Cleaned up the
getItemViewContainer
code, and improved the error that is thrown when the specified container element is not found - Can attach existing view instance w/ existing DOM element as child of collection view / composite view, in parent's
initialize
function - Fixed a bug where an undefined
this.options
would prevent child views from being rendered, trying to find the index of the view
- Cleaned up the
-
Layout
- Allow a Layout to be defined without
regions
, using Underscore v1.4.x
- Allow a Layout to be defined without
-
View / ItemView / CompositeView
- Removed the
serializeData
method and added directly toItemView
andCompositeView
as needed
- Removed the
-
Application
- Application regions can now be specified as a jQuery selector string, a region type, or an object literal with a selector and type:
{selector: "#foo", regionType: MyCustomRegion}
- added
.commands
as instance of Backbone.Wreqr.Commands, to facilitate command execution - added
.execute
method for direct command execution - added
.reqres
as instance of Backbone.Wreqr.RequestResponse, to facilitate request/response execution - added
.request
method for direct requesting of a response
- Application regions can now be specified as a jQuery selector string, a region type, or an object literal with a selector and type:
-
Marionette.triggerMethod
- Added
Marionette.triggerMethod
method to trigger an event and call the corresponding method. For example,view.triggetMethod("before:render")
will trigger the "before:render" event and call theonBeforeRender
method.
- Added
-
Marionette.addEventBinder
- Added
Marionette.addEventBinder
method to add all of the Backbone.Wreqr.EventBinder methods to a specified target object
- Added
-
Misc
- Added
Marionette.extend
as alias to Backbone'sextend
method for more consistent use - jQuery ($) support now works from global
$
orwindow.jQuery
- Updated to Underscore.js v1.4.1
- Updated to jQuery v1.8.2
- Added
v0.10.2 view commit logs
-
Callbacks
- Fixed a bug that caused callbacks to fire multiple times after calling
reset
- Fixed a bug that caused callbacks to fire multiple times after calling
-
Layout
- Fixed a bug that prevented the regions from being re-initialized correctly, when using
render
as a callback method for an event
- Fixed a bug that prevented the regions from being re-initialized correctly, when using
v0.10.1 view commit logs
- Modules
- Fixed a bug when defining modules in reverse order, that prevented
startWithParent
from working correctly
- Fixed a bug when defining modules in reverse order, that prevented
v0.10.0 view commit logs
-
Modules
- BREAKING: Module definition functions are executed immediately and only once, not every time you call
start
- BREAKING: Renamed
startWithApp
tostartWithParent
in module definitions - BREAKING: Sub-modules rely on the parent module to start them, by default, but can be started manually
- BREAKING: Sub-modules default to starting with their parent module start
- BREAKING: Specifying
startWithParent: false
for a sub-module will prevent the module from being started when the parent starts - BREAKING: Specifying
startWithParent: false
for a top-level module will prevent the module from being started when the parentApplication
starts - BREAKING: When starting a module, sub-modules will be started / initialized before parent modules (depth-first hierarchy traversal)
- BREAKING: When stopping a module, sub-modules will be stopped / finalized before parent modules (depth-first hierarchy traversal)
- Fixed: retrieving a module by name (
var foo = MyApp.module("Foo");
) will not change the module's definition orstartWithParent
setting
- BREAKING: Module definition functions are executed immediately and only once, not every time you call
-
CollectionView
- Allow
itemViewOptions
to be a function, which recieves theitem
as an argument
- Allow
-
Callbacks
- Added
reset
method to reset the list of callbacks and allow them to be run again, when needed
- Added
v0.9.13 view commit logs
-
CollectionView
- Fixed bug that prevented "collection:closed" event from being triggered
- Allow different item view to be rendered for each item in collection by overriding
getItemView
method
-
CompositeView
- Allow different item view to be rendered for each item in collection by overriding
getItemView
method
- Allow different item view to be rendered for each item in collection by overriding
-
Layout
- Regions are initialized before prototype constructor, or
initialize
function are called
- Regions are initialized before prototype constructor, or
-
All Views
- Adds declarative event binding for models and collections. See Marionette.View documentation for more information.
-
Build and test
- Removed all dependencies on Ruby, in favor of NodeJS and Grunt
v0.9.12 view commit logs
- Moved Marionette.Async to it's own repository
- De-linted source code
- Corrected throwing an "Exception" to throwing an "Error"
v0.9.11 view commit logs
-
JamJS Support
- Updated the
package.json
file with more detail and support for JamJS.
- Updated the
-
Layout
- Fixed a global variable leak
v0.9.10 view commit logs
- ItemView and Layout
- BREAKING: Removed the default implementation of
initialEvents
, so that a collection "reset" event won't cause the ItemView or Layout to re-render
- BREAKING: Removed the default implementation of
- Build Process
- Changed from Anvil.js to Grunt.js for the build process
v0.9.9 view commit logs
- Regions
- Added a
reset
method to regions, which closes the open view and deletes the region's cachedel
- Added a
v0.9.8 view commit logs
- Modules
- Fixed a bug that ensures modules will start and stop the correct number of times, instead of always stopping immediately after they have been stopped once
v0.9.7 view commit logs
-
Modules
- Fixed a bug to ensure modules are only started once, no matter how many definitions the module is split in to
-
View Templates
- Better support for pre-compiled templates - can specify a function as the
template
setting for a view, and the function will be run as the template, directly.
- Better support for pre-compiled templates - can specify a function as the
v0.9.6 view commit logs
- All Marionette Views
- Fixed bug that prevented
bindTo
function and otherEventBinder
functions from being available ininitialize
method of views
- Fixed bug that prevented
v0.9.5 view commit logs
- Layout
- Fixed a typo / bug in default Region type used for layouts
v0.9.4 view commit logs
-
BindTo -> EventBindings
- BREAKING: Renamed
Marionette.BindTo
toMarionette.EventBindings
and made it a constructor function instead of an object literal
- BREAKING: Renamed
-
Modules
- BREAKING: Changed the API of
Module.create
to be more clear and explicit aboutapp
parameter - BREAKING: Defer module definition until module is started
- Modules now have
addInitializer
method to add initializers - Modules can be started (run the initializers) with
start
method - Modules are automatically started when Marionette.Application
start
method is called - App.start sends options to module initializers
- Modules that are defined (or loaded from external source) afer app is started will auto-start by default
- Can specify a module is not started with the app, to prevent the module from being started when app.start is called
- Calling
start
on a module will start all of the sub-modules for that module
- BREAKING: Changed the API of
-
CollectionView/CompositeView
- Correctly handles non-existent collection and removing child item views that were added manually
- Corrected showing empty view and closing empty view when resetting collection and adding items
- Fixed bug to prevent showing the empty view more than once when rendering the collection view
-
Application
- Added a
removeRegion
method to close / remove regions, as a counter-function to theaddRegions
method
- Added a
-
Marionette.View (all views / base view)
- Can specify a set of
ui
elements that are cached jQuery selectors
- Can specify a set of
-
Layout
- An already closed layout can be re-rendered, and the regions will regenerate
- Allow a custom region type to be specified for all regions, as well as per-region instance
v0.9.3 view commit logs
-
CompositeView
- Cleaned up the method to get / cache the
itemViewContainer
- Allow
itemViewContainer
to be a function that return a jQuery selector string
- Cleaned up the method to get / cache the
-
View
render
methods all returnthis
in the standard Marionette views (the async views still return a deferred object).
v0.9.2 view commit logs
-
CompositeView
- Added
itemViewContainer
to specify which element children / itemView instances should be appended to
- Added
-
CollectionView
- Now triggers "before:render" and "render" events
-
Region
- Returns a deferred/promise from the
show
method, with Marionette.Async
- Returns a deferred/promise from the
-
Fixed bug in template cache for Marionette.Async
-
Marionette can now be installed with Volo
v0.9.1 view commit logs
- CollectionView and CompositeView properly close their
emptyView
instance when an item is added to the view's collection - CollectionView and CompositeView will show their
emptyView
after the last item has been removed from the collection
v0.9.0 view commit logs
-
BREAKING Async Support Removed From Core Marionette
- Marionette no longer supports asynchronous / deferred rendering in any view, by default
- Async / deferred rendering are now provided via
backbone.marionette.async.js
add-on
-
Split the single src/backbone.marionette.js file into multiple files for easier maintenance
-
Marionette.Async:
- Added
Marionette.Async
add-on which provides support for rendering and retrieving templates asynchronously
- Added
-
Marionette.View:
- BREAKING Renamed the
getTemplateSelector
method togetTemplate
- Call
unbindAll
to unbind all bound events, later in the close process, so theclose
event can be listened to
- BREAKING Renamed the
-
ItemView:
- BREAKING The
template
attribute no longer allows you to specify a function that returns a jQuery selector. OverridegetTemplate
to do this. - BREAKING The
renderHtml
method has been removed from the ItemView - BREAKING Async support removed
- BREAKING The
-
CollectionView:
- BREAKING Async support removed
- Now supports optional
emptyView
attribute, to specify what view to render when no items exist in the collection - Fixed a memory leak for closed item views
- ItemView is now guaranteed to have it's "onRender" and "onShow" methods called, when rendering the collection and when adding a new item to the collection / rendering the new item view
- Calls an
onItemAdded
method when adding an item/item view, just prior to rendering the item view - Can now specify an
itemViewOptions
object literal on your collection view definition, and the data will be passed to each itemView instance as part of the itemView's options - The
appendHtml
method receives a third argument of the itemView's "index" for sorted collections
-
CompositeView:
- BREAKING When a CompositeView's collection is reset, only the collection will be re-rendered. It will no longe re-render the composite's template/model, just the collection.
- BREAKING Async support removed
- (see change list for
CollectionView
)
-
Layout:
- BREAKING Regions specified within a layout are now available immediately after creating a layout instance
- BREAKING Re-rendering a layout will close all regions and reset them to the new DOM elements that were rendered
- BREAKING Layouts no longer have a
.vent
event aggregator hanging off them - BREAKING Async support removed
-
Region:
- BREAKING Removed the ability to send a second parameter to a regions' "show" method
- BREAKING Changed the implementation of
Region
to allow easier overriding of how the new view is added to the DOM - BREAKING Async support removed
-
TemplateCache:
- BREAKING Moved TemplateCache to object instances instead of single object literal
- BREAKING Moved the
loadTemplate
andcompileTemplate
toTemplateCache.prototype
- BREAKING
TemplateCache.get
no longer accepts a callback method. It always returns jQuery promise
-
Renderer:
- BREAKING Removed the
renderHtml
method - Rendering a pre-compiled template function is now much easier - just override the
Renderer.render
method.
- BREAKING Removed the
-
Modules:
- BREAKING Modules must be defined on an instance of a Marionette.Application, and cannot be defined from another module directly
- BREAKING Modules no longer allow you to return a custom module object from the module definition function
- BREAKING Modules no longer allow you to add initializers to them
- BREAKING Modules no longer have a
.vent
event aggregator hanging off them - Extracted
Marionette.Module
in to it's own constructor function to be used as modules, instead of Marionette.Application - Modules allow you to pass in any arbirary arguments, after the module definition function, and they will be supplied to the module definition function
- The
this
argument in a module definition function is now the module itself
-
Callbacks:
- BREAKING Switched the order of parameters for the
run
method toargs, context
- BREAKING Switched the order of parameters for the
-
BindTo:
- The unbinding of an event now considers the
context
parameter when unbinding, allowing multiple handers to be bound to the same event from the same object, and unbinding only one of them
- The unbinding of an event now considers the
v0.8.4 view commit logs
- Fixed: A call to
.module
will correctly pass theApplication
instance from which.module
was called, as the second parameter of the module definition function
v0.8.3 view commit logs
- Module definitions can be split across multiple files and/or multiple calls to define the module
v0.8.2 view commit logs
- Views now have the ability to define
triggers
which will convert a DOM event in to aview.trigger
event
v0.8.1 view commit logs
- Module definition functions will only be applied to the last module in the . chain
v0.8.0 view commit logs
- Added modules and sub-modules through the Application object
- An
itemView
instance 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
- The
onBefore
method of ItemView can now return a deferred object - Code cleanup for rendering methods
- Fixed issue with
unbindAll
in BindTo, that was skipping some items
- The
bindTo
method on theEventAggregator
now returns a binding configuration object - Automatic mixing in of
templateMethods
as template / view helper methods, in views that use theserializeData
function - 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
- Extracted
compileTemplate
method in TemplateCache for clarity and easier modification - ItemView will wait until
onRender
has completed before triggering other rendered events - Region now supports an
onShow
method, when defining a custom region - Moved the default
serializeData
method to the base Marionette.View - CompositeView now calls the
serializeData
method to get the model's data for the view BindTo
changes:- The
bindTo
method returns a "binding" object so that it can be unbound easily - Now has an
unbindFrom
method that will unbind a binding object
- The
- ItemView now has a
renderHtml
method that can be overriden to render the item view's data - Region now supports an
initialize
function 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
renderTemplate
method has moved from theItemView
prototype on to theRenderer
object - BREAKING: The
appendHtml
method of theCollectionView
now takescollectionView, itemView
as the arguments, instead ofel, html
- Added
Marionette.View
object, to contain a few basic parts of every Marionette view - Added
Marionette.Renderer
object, to handle template rendering - Views correctly trigger the "close" events before unbinding event subscribers
- Additional
CollectionView
changes:- Extracted
getItemView
method to retrieve theitemView
type, either fromthis.itemView
orthis.options.itemView
- Extracted
buildItemView
method to build each item's view - Renamed
removeChildView
toremoveItemView
to make the language consistent - Triggers "item:added" event after each item has been added
- Triggers "item:removed" event after an item has been removed
- Extracted
CompositeView
changes:- No longer takes a
modelView
. Now directly renders thetemplate
specified - Defaults to a recurive structure, where
itemView
is the current composite view type
- No longer takes a
- A
Region
will trigger ashow
event 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
- CollectionView and CompositeView can render without a collection
ItemView
changes- Calls a
beforeRender
andbeforeClose
method on the view, if it exists - Triggers a
item:before:render
event, just prior to rendering - Triggers a
item:before:close
anditem:closed
events, around the view'sclose
method
- Calls a
CollectionView
changes- Calls a
beforeRender
andbeforeClose
method on the view, if it exists - Triggers a
collection:before:render
event before rendering - Triggers a
collection:before:close
andcollection:closed
event, surrounding closing of the view
- Calls a
- The
CollectionView
andCompositeView
now close child views before closing itself
- BREAKING: The
CollectionView
no longer has areRender
method. Callrender
instead - BREAKING: The
TemplateCache.get
method now returns a plain string instead of a jQuery selector object - Fixed a bug with closing and then re-using a Layout with defined regions
- Fixed a potential race condition for loading / caching templates where a template would be loaded multiple times instead of just once
- Fixed the composite view so that it renders the collection correctly when the collection is "reset"
- Fixed the composite view so that it re-renders correctly
- Fixed various deferred usages to only return promises, instead of the full deferred object
-
BREAKING: Renamed
LayoutManager
toLayout
-
BREAKING: Renamed
RegionManager
toRegion
-
BREAKING: Renamed
TemplateManager
toTemplateCache
-
Layout
- BREAKING:
Layout.render
no longer returns the view itself, now returns a jQuery deferred object - The
.vent
attribute is now available in theinitializer
method - Ensures that regions select the
$el
within the Layout's$el
instead of globally on the page - Initialize the regions before the layout, allowing access to the regions in the
onRender
method of the layout - Close the Layout's regions before closing the layout itself
- BREAKING:
-
CompositeView
- BREAKING:
CompositeView.render
no longer returns the view itself, now returns a jQuery deffered object - Will only render the collection once. You can call
renderCollection
explicitly to re-render the entire collection - Will only render the model view once. You can call
renderModel
explicitly to re-render the model - Correctly close and dispose of the model view
- Triggers various events during rendering of model view and collection view
- Calls 'onRender' method of composite view, if it exists
- BREAKING:
-
ItemView
- BREAKING:
ItemView.render
no longer returns the view itself, now returns a jQuery deferred object - Optimization to only call
.toJSON
on either model or collection, not both - Trigger "item:rendered" method after rendering (in addition to calling onRender method of the view)
- BREAKING:
-
CollectionView
- BREAKING:
CollectionView.render
no longer returns the view itself, now returns a jQuery deferred object - Trigger "collection:rendered" method after rendering (in addition to calling onRender method)
- BREAKING:
-
Large updates to the readme/documentation
-
Heavy use of
jQuery.Deferred()
andjQuery.when/then
to better support asynchronous templates and rendering
- BREAKING: Renamed
CompositeRegion
toLayoutManager
- Aliased CompsiteRegion to LayoutManager for backwards compatibility
- Bug fix for correctly initializing LayoutManager with specified options in constructor
- Controller methods fired from an
AppRouter
are now called withthis
set to the controller, instead of the router - Fixed a bug in the CompositeView where the list wouldn't render when passing in a populated collection
- BREAKING: Extraced
CompositeView
out of the collection view - Added
CompositeView
for managing leaf-branch/composite model structures - Added
CompositeRegion
for managing nested views and nested region managers - Added
attachView
method toRegionManager
to attach existing view without rendering / replacing - Specify how to attach HTML to DOM in region manager's
show
method
- Don't re-render an ItemView when the view's model "change" event is triggered
- Allow
RegionManager
to be instantiated with anel
specified in the options - Change how RegionManagers are added to an Application instance, to reduce memory usage from extraneous types
- AppRouter can have it's
controller
specified directly in the router definition or in the construction function call - Extracted
Marionette.EventAggregator
out in to it's own explicit object
- CollectionView closes existing child views before re-rendering itself, when "reset" event of collection is triggered
- CollectionView now has "initialEvents" method which configures it's initial events
- ItemView now has "initialEvents" method which configures it's initial events
- CollectionView renders itself when the view's collection "reset" event is fired
- ItemView renders itself when the view's model "change" event is fired
- ItemView renders itself when the view's collection "reset" event is fired
- Fixed bug with RegionManagers trying to select element before DOM is ready, to lazy-select the element on first use of
show
- BREAKING: Removed the
setOptions
method from theCallbacks
object - Refactored
Callbacks
object to use a jQuery Deferred instead of my own code - Fixed template manager's
clear
so it properly clears a single template, when only one is specified - Refactored the
RegionManager
code to support several new features- now support returning a jQuery deferred object from a view's
render
method - now have a
close
method that you can call to close the current view - now trigger a "view:show" and "view:close" event
- correctly remove reference to previous views, allowing garbage collection of the view
- now support the
bindTo
andunbindAll
methods, for binding/unbinding region manager events
- now support returning a jQuery deferred object from a view's
- Minor fix to context of template manager callback, to fix issue w/ async template loading
- BREAKING: Rewrote the template manager to be async-template loading friendly
- BREAKING: Dropping support for Backbone v0.5.3 and below
- Added
Marionette.Callbacks
to manage a collection of callbacks in an async-friendly way - Guarantee the execution of app initializer functions, even if they are added after the app has been started.
- App triggers "start" event after initializers and initializer events
- Updated to Backbone v0.9.1
- Make region managers initialize immediately when calling
app.addRegions
- BREAKING:
view.el
forItemView
andCollectionView
is no longer a jQuery selector object. Useview.$el
instead - BREAKING:
regionManger.el
is no longer a jQuery selector object. UseregionManager.$el
instead - Updated to use Backbone v0.9.0
- Updated to use Underscore v1.3.1
- Removed default
itemView
from theCollectionView
definition CollectionView
now explicitly checks for anitemView
defined on it, and throws an error if it's not found
- Bind the context (
this
) of application initializer functions to the application object
- Added
AppRouter
, to reduce boilerplate routers down to simple configuration CollectionView
can be treated as a composite view, rendering anmodel
and acollection
of models- Now works with either jQuery, Zepto, or enter.js
ItemView
will throw an error is no template is specified
- Return
this
(the view itself) fromItemView
andCollectionView
render
method - Call
onRender
after theCollectionView
has rendered itself
- Fixed global variable leaks
- Removed declared, but unused variables
- Fixed binding events in the collection view to use
bindTo
(#6) - Updated specs for collection view
- Documentation fixes (#7)
- Added
TemplateManager
to cache templates - CollectionView binds to add/remove and updates rendering appropriately
- ItemView uses
TemplateManager
for template retrieval - ItemView and CollectionView set
this.el = $(this.el)
in constructor
- Added
ItemView
- Added
CollectionView
- Added
BindTo
- Simplified the way
extend
is pulled from Backbone
- Initial release
- Created documentation
- Generated annotated source code