Question

I’m reading this:

http://codebrief.com/2012/01/the-top-10-javascript-mvc-frameworks-reviewed/

I’m using backbone.js. I love it, though it requires too much boilerplate. Anyway.

The author of the post seems to put great importance on UI-bindings and composed view.

I think I know the basic advantage of ui bindings, you can change small parts of the view as the model changes without re-rendering the entire view. I don’t necessarily see the point though. If your view is huge maybe you should make smaller views? I’ve seen knockoutjs’s code and it’s littered with ugly data-bind stuff. How does emberjs handle it? Is there an example?

I have no idea what he means by composed views, could someone elucidate?

Composed Views – Like all software developers, I enjoy creating modular reusable code. For this reason, when programming UI, I would
like to be able to compose views (preferably at the template layer).
This should also entail the potential for a rich view component
hierarchy. An example of this would be a reusable pagination widget.

Is there an example?

Thanks

Edit:

Would this help make something like composed Views?

https://github.com/tbranyen/backbone.layoutmanager

Answer 1

I created LayoutManager for Backbone.js because I too wanted to composite views.

http://tbranyen.github.com/backbone.layoutmanager/

Let me know if you find this approach helpful.