This post serves a dual purpose: first of all it is to announce (to anyone who hasn’t see the original announcement on my social media accounts) that the book that I’ve been writing for the past year - that has kept me from more actively working with my blog - is finally finished! Second, I’m giving away 3 copies of that very same book! That’s right, I’m holding two giveaways at once: one for Backbone.js Patterns and Best Practices and one for my very one Better Backbone Applications with MarionetteJS!
tag : MarionetteJS
For a while, I’ve been thinking about how best to handle showing modal dialog boxes for my applications while utilizing Backbone views. A lot of interesting ideas passed through my head, but none of them seemed exactly right. Then I saw a post by Derick Bailey where he described how he uses Marionette’s Regions to handle the work. His post is a bit on the old side and Regions have changed a bit since, so I decided to look into how to do it myself.
Hey everyone. I’m sorry that I’ve been neglecting you all so much. I can’t believe it’s been two months since I last posted something on here. In short, I’ve been very busy. I’ve written several articles for other blogs, and that’s actually what this post is all about. If you’re not following some of these blogs, you may have been missing out on some of my work. So here’s what I wrote in my absence from this website.
Backbone.js introduced us to a more modular way of developing today’s web applications by separating our code into semantic and reusable pieces. Backbone’s main crutch was that it offered only the bare minimum so that it was easy to learn and didn’t force you to do anything that you didn’t want to do, but we were left on our own to figure out how to handle much of the implementation details. Marionette is here to help with that.