marionette

This is a betting game, made in backbone. I have a bounty of 100 to help me refactor it into a marionette based application. I am unsure where to start - in terms of reconfiguring the models, how to swap the views out to make them regions. I believe the steps would be to start with creating a new marionette application and router. var app = Marionette.Application.extend({ initialize: function(options) { console.log('My container:', options.container); } }); var app = new app({container: '#app'}); //router var MyRouter = Marionette.AppRouter.extend({ appRoutes: { "some/route": "someMethod" },

I would like to know if it possible to extend in some way the mechanism Marionette Layout s are based on creating a sort of stack like navigation. Marionette behaviour. Before a region show() 's a view it calls close() on the currently displayed view. close() acts as the view 's destructor, unbinding all events, rendering it useless and allowing the garbage collector to dispose of it. My scenario. Suppose I have a sort of navigation mechanism where a Layout acts as controller and first displays an ItemView called A, then a click somewhere allows to switch to ItemView B. At this point, an

I'm trying to write MarionetteJS module using Typescript. Compiled module should be added to plain javascript application using RequireJS and initialized as normal Marionette module i.e.: define( ['marionette', 'modules/sample/sample'], function (Marionette, Sample) { var sampleApp = new Backbone.Marionette.Application(); sampleApp.SampleModule = sampleApp.module("SampleModule", Sample.Sample); } My module is created, but initializer and start functions are not being called by Marionette.Appplication. This is my TypeScript class: /// <amd-dependency path="backbone" /> /// <amd-dependency path=

I have a UI controller that for simplicity you can think as a Folder Tree where you can select multiple folders with checkboxes. The selection is saved in the model and "on save" there rare also a few actions triggered. For usability reasons, we want to use two different visualizations of the same controller. The two UI controllers can in some layouts be present at the same time, in others only one at the time. It would be nice to be able to reuse the same collection instance across the 2 UI controllers. I can do this in one module pretty easily but how should I structure the code to make it

I'm new to Marionette and can't get my head around events... I have an ItemView which trigger an event, and I would like to receive this event at the application level, but when my app listen for this event, nothing happens... If the Event Aggregator is in Application and ItemView, why this code doesn't work ? : var MessageItemView = Backbone.Marionette.ItemView.extend({ template: "#messagesTPL", tagName: 'tr', className: 'messageItem', events : { 'click': 'displayMessage' }, displayMessage: function () { this.trigger('display:message'); } }); App.on('display:message', function () { console