Building modular and component driven architecture in Backbone.js and Marionette.js. March 4, 2015 webadmin ⋅ Building Architecture ⋅ Jeremy Fairbank http://www.nodevember.org/speakers/jeremy-fairbank Like 0 Thanks! You've already liked this « Home Improvement Karama | TaylorMade Carpentry Services » Samsung Galaxy Note 3 Water Damage. Not Charging 7 Comments maria turzynska November 18, 2014 @ 6:13 pm Very interesting presentation. Can you give access to the source code. alamandrax December 2, 2014 @ 6:03 pm the audio is a bit annoying, but great presentation! Paulo Brito January 16, 2015 @ 9:05 pm David Newkerk January 22, 2015 @ 10:53 am Super helpful, thanks Jeremy! For anyone who’s looking for the source code, the slides are available at http://presentboldly.com/jfairbank/modular-and-component-driven-architecture-in-marionettejs … if you click the “View Files” folder icon at the bottom left, it toggles to showing the various source code used throughout the presentation. Doesn’t seem to include everything you’d need to run the examples locally, though includes more than the slides themselves. Hope this helps :) Marco Casula January 25, 2015 @ 12:44 am Thanks Jeremy, very interesting, nice approach to components and message bus well illustrated. However, I have some doubts about the use of “require” to load hbs templates (time 11:53) and the result produced by browserify. Is that the correct approach ? Jeremy Fairbank February 3, 2015 @ 5:05 pm Marco, one step I didn’t thoroughly go over was including a build step to generate the template files. Basically, I’m using a build step with gulp (or you can use grunt) to convert my .hbs files into .js files that contain the compiled template functions. Maxime Morin February 17, 2015 @ 3:58 pm Thanks! Components seems to be the missing part in our application… I’m wondering if they should interact directly with channels(for dry principle) or they should trigger events so each module using the component handle it to interact with the whole system. Examples: requesting related entities to the model so with could show extra information on demand, executing commmand of another module, etc… Thank you!