marionette

Is it possible to use the Handlebars.js with the Backbone.Marionette extension without reimplementing the Views render function? It seems that Marionette is relying on the convention that you use Backbone.js with underscores templating engine. But I really like the handlebar approach so I'm asking if I can the high-level-tools of Marionette with handlebars. brettjonesdev A simple way to use Handlebars with Marionette is simply to define template in each View as a pre-compiled Handlebars template function. For instance: var MyView = Backbone.Marionette.ItemView.extend({ template: Handlebars

The basic situation is this: I have a Composite View and an Item View. I construct the Composite view passing it a model and a collection. The model data is used to populate the template for the Composite view. The collection data is used to populate the Item View for the Composite View. What I want to do is this: in a template helper for the Item view I want to access the model data for the Composite View. I've got as far as accessing the view instance of the Item View. I thought that might give me a handle on the Composite View, from where I could get to its model, but it doesn't. Is there a

Marionette provides two components named Regions and Layouts . At first glance, they seem to provide similar functionality: A location on the page for my application to place subviews, plus some additional event binding fairy dust. Looking under the hood , it's fairly clear that each component is implemented in a very different way, but I'm not sure why and when I would want to use one over the other. What use cases are each component intended for? Layouts and Regions serve very different purposes: a layout is a type of view, but a region will display a view in your HTML/DOM for you. A region

Is it possible to put a view that is already rendered into a backbone marionette region without rendering it again? For example: region.show(myView); // This will call render on myView I don't want the region to render my view again. If I do: region.attachView(myView); // This won't render myView, but it also won't show it First override marionette ItemView constructor and render like this (if you want to use it in CollectionView and CompositeView override these methods of them too): var fnCons = Marionette.ItemView.prototype.constructor, fnRender = Marionette.ItemView.prototype.render;

Already a couple of hours struggle trying to solve this... Although the model gets fetched correctly and I can verify it as the view gets informed of the model's 'change' event, it just does not render. At startup, the default model data ('Test Project'), is correctly displayed in the view, but after the model is refreshed, the view is not refreshed. I tried to show a new view in the layout after model refresh but it did not change much... Any idea or opinion about this ? App.Project = function () { var Project = {}; var ProjectModel = Backbone.Model.extend({ defaults:{ id: 0, name: "Test

I have one "test.html" in that I have this contend (whole html file have this contend). <h1>First page</h1> I need to load that contend in my div having id ="contend" using Marionette .js <div id="contend"> </div> could you please tell me how I will do that ? fiddle : http://jsfiddle.net/JQu5Q/16/ $(document).ready(function(){ var ContactManager = new Marionette.Application(); ContactManager.addRegions({ mainRegion:"#contend" }) ContactManager.on("start", function(){ console.log("ContactManager has started!"); }); ContactManager.start(); // router var routers = Backbone.Router.extend({ routes:

Curious as to how people usually handle this. My strategy is to have an authorized root route and unauthorized root route. The authorized users get sent directly to my marionette.js single page application and unauthroized users get sent into a standard rails landing page with the option to login or register. It seems you could combine these all into your single page application. You could show/hide ui elements based on a class you attach to elements based on the authorization needed to see them (registered, admin, moderator, etc). You could also add some kind of "before_filter" to your router

I'm trying to capture the scroll event within a Backbone.Marionette.CompositeView, but without success. As an exercise, I'm rewriting http://www.atinux.fr/backbone-books/ using Backbone.Marionette. As you can see, when you scroll down, more books are fetched and displayed (i.e. infinite scroll). However, I'm unable to capture the scroll event on my view. Here's my (simplified) code: LibraryView = Backbone.Marionette.CompositeView.extend({ // properties, initializer, etc. events: { 'scroll': 'loadMoreBooks', 'click': 'loadMoreBooks' }, // some functions loadMoreBooks: function(){ console.log(