Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Apr 24, 2015
  1. @jasonLaster

    Merge pull request #2521 from MeoMix/patch-2

    jasonLaster authored
    Removing small typo (?)
  2. @jasonLaster

    Merge pull request #2523 from MeoMix/patch-3

    jasonLaster authored
    grammar fix
  3. @MeoMix

    grammar fix

    MeoMix authored
  4. @MeoMix

    Removing small typo (?)

    MeoMix authored
    The word 'Views' was existing as its own bullet point.
Commits on Apr 17, 2015
  1. @jasonLaster

    Merge pull request #2504 from fay-jai/fixDocTypo

    jasonLaster authored
    Remove new keyword in front of childEvents example
  2. Remove new keyword in front of childEvents example

    Willson Mock authored
Commits on Apr 11, 2015
  1. @jasonLaster

    Merge pull request #2480 from paulfalgout/docs/deprecate-module

    jasonLaster authored
    Deprecate Marionette.Module
  2. @scottaj @paulfalgout

    Fix code style error that is failing build.

    scottaj authored paulfalgout committed
Commits on Apr 10, 2015
  1. @paulfalgout

    Deprecate Marionette.Module

    paulfalgout authored
    And link to the shim
Commits on Mar 30, 2015
  1. @jasonLaster

    Merge pull request #2465 from fay-jai/doc

    jasonLaster authored
    Fix typo in
  2. Fix typo in

    Willson Mock authored
Commits on Mar 24, 2015
  1. @jasonLaster

    Merge pull request #2447 from JustBlackBird/clean_bower_package

    jasonLaster authored
    Remove unneeded files from bower package
  2. @JustBlackBird
Commits on Mar 19, 2015
  1. @jasonLaster

    Merge pull request #2433 from Morantron/master

    jasonLaster authored
    fyx tipo in regionManager docs
  2. @Morantron
Commits on Mar 16, 2015
  1. @samccone
  2. @jasonLaster

    Merge pull request #2423 from thenickcox/behavior_docs

    jasonLaster authored
    Improve grammar, style, and consistency in the `Behavior` docs.
  3. @caseycs


    caseycs authored
  4. @thenickcox

    Improve grammar, style, and consistency in the `Behavior` docs.

    thenickcox authored
    This commit makes relatively minor grammatical and stylitic changes
    to improve the clarity of the `Behavior` docs. In addition, for the
    sake of consistency, the singular forms of both `Behavior` and
    `View` have been wrapped in backticks (`<code>` tags in the compiled
    HTML) to match what seemed to be the preference based on the rest of
    the document. Further, the established practice seemed to have been
    to capitalize both "Behaviors" and "Views", but not to wrap them
    in `<code>` tags, so this fixes a few stragglers in that regard.
  5. @samccone

    Merge pull request #2421 from kahwee/patch-1

    samccone authored
    Make Travis start build faster with Docker
Commits on Mar 15, 2015
  1. @kahwee
Commits on Mar 10, 2015
  1. @jasonLaster

    Merge pull request #2409 from barretts/master

    jasonLaster authored
    normalize documentation, change Backbone.Marionette to Marionette
  2. @barretts
Commits on Mar 1, 2015
  1. @samccone

    Bump and build v2.4.1

    samccone authored
  2. @scott-w @samccone

    Improve internal documentation linking

    scott-w authored samccone committed
    Fixes #2380
  3. @ahumphreys87 @samccone

    add jscs

    ahumphreys87 authored samccone committed
  4. @ahumphreys87 @samccone
  5. @samccone

    Ignore tmp directory

    samccone authored
    Generated during the build process, no need to publish this.
Commits on Feb 24, 2015
  1. @jasonLaster

    Merge pull request #2365 from benmccormick/master

    jasonLaster authored
    Improve Behavior documentation
  2. Improve Behavior documentation

    Ben McCormick authored
    Two main goals
    1. Make it clear that View life cycle functions are available on
    2. Improve grammar/consistency of docs when referencing Views and
    Specifically the docs had alternated between `behavior`, `view`, Behavior, View, and behavior, view
    to refer to Behaviors and Views.
    In addition to some spelling/grammar stuff, I attempted to fix this by following the convention that:
    `View` and `Behavior` refer to the Marionette.View and Marionette.Behavior classes
    View and Behavior refer to a View or Behavior class (possibly a subclass of `View` or `Behavior`)
    view and behavior refer to instances of a View or Behavior class.
Commits on Feb 23, 2015
  1. @samccone

    Bump and build v2.4.0

    samccone authored
  2. @samccone

    Improve mixin of view ui hash to behaviors

    Ben McCormick authored samccone committed
    This commit makes the view ui hash available consistently in
    Behaviors, making it available in callbacks as well as the
    events and triggers hashes.  There is also some refactoring to simplify
    and centralize how the views ui hash is mixed into the Behaviors
    reducing duplication
  3. @samccone

    Validate yaml as part of the tests.

    samccone authored
    Previosuly jsdoccer was silently failing
    when validating the yaml. This makes it so our build will fail if
    someone pushed invalid json.
  4. @jfairbank @samccone

    Clean up collection view docs

    jfairbank authored samccone committed
  5. @jasonLaster @samccone

    Add region events for layout children views

    jasonLaster authored samccone committed
    Region events are one of the most common requets we've received:
    events in a layout like you can listen for child events in a collection
      onChildViewSubmit: function(childView, successMsg) {},
      onChildViewFail: function(childView, failMsg) {}
    The first is share a radio channel,
    the second is share a common eventable object (think model). Messaging
    through a channel can be ugly because it encourages an explosion of
    channels that can be hard to keep track of. Think lots of little wires
    through the app. Messaging through a shared eventable object, is ugly
    because it's a source of indirection that's unexpected. It's not obvious
    that the model is being used in this way.
    Event Bubbling:
    This is not event bubbling where an event will go all the way up the
    view tree. I do not want to rule that out, as it might be nice, but
    there are more design considerations there.
    When we introduced the `_parent` reference, we discussed that there was
    support for getting nested children for proxying events, but there was
    no support for getting ancestor views for proxying events and other
    internal utilities. We now have support for this, but will obviously
    discourage end users from tapping into the power. With great power
Something went wrong with that request. Please try again.