All Versions
149
Latest Version
Avg Release Cycle
116 days
Latest Release
2034 days ago
Changelog History
Page 11
Changelog History
Page 11
-
v0.9.9 Changes
- Regions
- Added a
resetmethod to regions, which closes the open view and deletes the region's cachedel
- Added a
- Regions
-
v0.9.8 Changes
- 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
- Modules
-
v0.9.7 Changes
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
templatesetting 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 Changes
- All Marionette Views
- Fixed bug that prevented
bindTofunction and otherEventBinderfunctions from being available ininitializemethod of views
- Fixed bug that prevented
- All Marionette Views
-
v0.9.5 Changes
- Layout
- Fixed a typo / bug in default Region type used for layouts
- Layout
-
v0.9.4 Changes
BindTo -> EventBindings
- BREAKING: Renamed
Marionette.BindTotoMarionette.EventBindingsand made it a constructor function instead of an object literal
- BREAKING: Renamed
Modules
- BREAKING: Changed the API of
Module.createto be more clear and explicit aboutappparameter - BREAKING: Defer module definition until module is started
- Modules now have
addInitializermethod to add initializers - Modules can be started (run the initializers) with
startmethod - Modules are automatically started when Marionette.Application
startmethod 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
starton 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
removeRegionmethod to close / remove regions, as a counter-function to theaddRegionsmethod
- Added a
Marionette.View (all views / base view)
- Can specify a set of
uielements 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 Changes
CompositeView
- Cleaned up the method to get / cache the
itemViewContainer - Allow
itemViewContainerto be a function that return a jQuery selector string
- Cleaned up the method to get / cache the
View
rendermethods all returnthisin the standard Marionette views (the async views still return a deferred object).
-
v0.9.2 Changes
CompositeView
- Added
itemViewContainerto 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
showmethod, 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 Changes
- CollectionView and CompositeView properly close their
emptyViewinstance when an item is added to the view's collection - ๐ CollectionView and CompositeView will show their
emptyViewafter the last item has been removed from the collection
- CollectionView and CompositeView properly close their
-
v0.9.0 Changes
๐ฅ 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.jsadd-on
๐ง Split the single src/backbone.marionette.js file into multiple files for easier maintenance
Marionette.Async:
- Added
Marionette.Asyncadd-on which provides support for rendering and retrieving templates asynchronously
- Added
Marionette.View:
- BREAKING Renamed the
getTemplateSelectormethod togetTemplate - Call
unbindAllto unbind all bound events, later in the close process, so thecloseevent can be listened to
- BREAKING Renamed the
ItemView:
- BREAKING The
templateattribute no longer allows you to specify a function that returns a jQuery selector. OverridegetTemplateto do this. - BREAKING The
renderHtmlmethod has been removed from the ItemView - BREAKING Async support removed
- BREAKING The
CollectionView:
- BREAKING Async support removed
- Now supports optional
emptyViewattribute, 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
onItemAddedmethod when adding an item/item view, just prior to rendering the item view - Can now specify an
itemViewOptionsobject literal on your collection view definition, and the data will be passed to each itemView instance as part of the itemView's options - The
appendHtmlmethod 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
.ventevent 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
Regionto 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
loadTemplateandcompileTemplatetoTemplateCache.prototype - BREAKING
TemplateCache.getno longer accepts a callback method. It always returns jQuery promise
Renderer:
- BREAKING Removed the
renderHtmlmethod - Rendering a pre-compiled template function is now much easier - just override the
Renderer.rendermethod.
- 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
.ventevent aggregator hanging off them - Extracted
Marionette.Modulein 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
thisargument in a module definition function is now the module itself
Callbacks:
- BREAKING Switched the order of parameters for the
runmethod toargs, context
- BREAKING Switched the order of parameters for the
BindTo:
- The unbinding of an event now considers the
contextparameter 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