Revesiting Backbone.js View Rendering(elving.me)

9 pointsby elvingvor 13 Jahren7 comments

http://elving.me/post/45836034024/revesiting-backbone-js-view-rendering

8 comments

[deleted]vor 13 Jahren

pselbertvor 13 Jahren

There are numerous benefits to using a presenter, or at least a "renderContext" object. Most conversion, formatting, predicates, and lazy attributes won't come through with toJSON(). The performance penalty is negligible compared to the benefit of testable presenter methods, logic out of the view, etc.

Performance isn't the only thing to consider.

wpratervor 13 Jahren

I agree that putting all that logic and template vars into a template is confusing. Hard to create mocks of what the HTML should actually be structured like. Im using Jade so I can be terse and pre-compiling the templates. While in my Backbone application, I apply DOM-like rendering with Plates.js.

zimbatmvor 13 Jahren

I'm not familiar with Backbone but isn't `model.toJSON()` unnecessarily removing useful data types (like Date) that aren't available in JSON ?

papercranevor 13 Jahren

You're probably thinking of `JSON.stringify()`. `model.toJSON()` just returns a clone of the models attributes object.

zimbatmvor 13 Jahren

So `model.toJSON()` isn't supposed to return a JSON-compatible data structure ?

papercranevor 13 Jahren

It's supposed to return an object that is suitable for turning into JSON, but it won't convert any of items members. JSON.stringify relies on the toJSON functions of the members to serialize themselves.

lopatinvor 13 Jahren

Why is using 'model.toJSON()' overkill?