v1.3.0 collectionView / compositeView optimizations

• CompositeView / CollectionView
  • Massive perf boost in rendering collection and composite views by using document fragments jsPerf

v1.2.3 - Bug Fixes

• CompositeView
  • Fixed bug where child views were being added before the initial render, thus raising errors.

v1.2.2 Bug Fixes

• Views
  • Move the instantiation of view options above the constructor This allows for view options to be accessed from within the initialize method for a given view
    This is needed since backbone views no longer set the view options in the constructor

V1.2.1 - Bug Fixes

• Views
  • fixed a bug so now view options are {} by default and not undefined.
  • fixed a bug where the triggers preventDefault and stopPropagation were executing in the wrong context – triggers now prevent default and stopPropagation by default once more.

v1.2.0 - Backbone upgrade and minor improvements

This release updates MarionetteJS to work with Backbone 1.1.0. To make this work, Marionette is back-filling the Backbone.View this.options for all Marionette specific view types. This is a temporary plug while the Backbone community moves toward the new version of Backbone and this breaking change in Backbone v1.1.

MarionetteJS still works with Backbone v1.0 of course. You should be able to drop this release in without any breaking changes, whether you are using Backbone v1.0 or v1.1

Additional highlights for this release include:

• Views
  • added the ability to customize the behavior of triggers preventDefault and stopPropagation
• Collection View / CompositeView
  • added the ability to specifiy getEmptyView for dynamic emptyView lookups

v1.1.0: bug fixes, consistency and options

This release is a drop-in-replacement for v1.0.x, with no breaking changes in API or behavior. If you are already using v1.0.x, it is recommended you update to v1.1 at this time.

This release is primarily pull requests and some left-over bug fixes. It contains a hand-full of new behaviors and method calls, but does this without breaking any existing API or documented behaviors. Note that there were several pull requests and bug submissions that did not make it in to this release. Some of them will need a little more digging and work before another v1.x release. Some of them would cause breaking changes in the API, and need to be pushed back to a v2.0 release, or later.

Download it from this Github repository or MarionetteJS.com.

For complete details on what changed, see the changelog for v1.1.0

Inheritance and documentation updates

This release fixes several problems with inheritance that were caused in the v1.0.3 release, and updates a bunch of documentation spots.

• ItemView
  • Added needed constructor function back - it added lots of things and needed to be there
• CompositeView
  • Added explicit call to CollectionView constructor to allow for inheritance overriding
• Layout
  • Small clarification for consistency on call to ItemView constructor

Bug Fixes

ItemView

• Deleted unneeded constructor function - it added nothing and didn't need to be there
  CompositeView
• Added index parameter to method signature, to show that it is available
• Deleted unneeded constructor function and removed call to getItemView as it was causing problems and was not needed in the constructor.

All Views

• Fixed a bug in the entity and collection event bindings, where stopListening would not unbind the event handlers

Renderer / All Views

• The Renderer.render method will throw a more meaningful error if the supplied template is falsey
  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 the show events from the region / view

RegionManager

• Fixed a bug to decrement the .length when a region is removed