/#! - Latest Comments

Re: Lightweight Relation Modeling with Backbone

Jörn — Sun, 22 Sep 2013 20:19:46 -0000

We also tried to improve relation handling between models and ended up with a backbone plugin which supports one-to-one, one-to-many and many-many relations out of the box. https://github.com/jj-studi... check it out some time.

Re: Lightweight Relation Modeling with Backbone

talfco — Mon, 20 May 2013 17:30:52 -0000

Thanks for this KISS solution. Will give it a try, lost too much time in trying to get up Backbone.Relational running.

Re: Lightweight Relation Modeling with Backbone

diurnalist — Thu, 02 May 2013 16:00:04 -0000

Thank you :)

Re: Lightweight Relation Modeling with Backbone

diurnalist — Thu, 02 May 2013 15:57:14 -0000

I deliberately kept it off the attributes hash for a few reason. One, it would conflict too much with how Backbone wants to treat items in that hash. In my view, the attributes hash should be for first-level properties of the model, and not hold submodels.

Serialization is not a problem because I overwrite toJSON to serialize the relations along with the parent model.

I accepted the (small) loss of the .get() standardization because in my mind the properties of a model and nested models are inherently two different things and mixing the metaphors seemed to muddle this fact.

Re: Lightweight Relation Modeling with Backbone

makala — Thu, 02 May 2013 15:15:49 -0000

Love it, thank you. I've been beating my head against Backbone Relational for a few months now. This is a much nicer solution, especially when your requirements are rather simple.

Re: Lightweight Relation Modeling with Backbone

mdarse — Fri, 16 Nov 2012 04:02:11 -0000

Really nice post :-) Useful.

Re: Lightweight Relation Modeling with Backbone

Michel Boudreau — Wed, 25 Jul 2012 21:37:47 -0000

Why would you have a relationship right under the model? Shouldn't that be added to the attributes of the model? If it's not there, it's not possible to serialize a model properly, or have a standard across the code of using 'get'.

Re: Lightweight Relation Modeling with Backbone

Jason Anderson — Wed, 02 May 2012 16:23:20 -0000

Not a dumb question at all! The line `relation = this[key] = new constructor();` ensures that the relation is attached directly to the model. So if you had a View that had a reference to an Album instance, inside the view you would do: `this.model.trackList` to get the reference to the TrackList.

Re: Lightweight Relation Modeling with Backbone

Libor Nenadál — Wed, 02 May 2012 15:33:10 -0000

Sorry for being dumb but how is the newly created relation model accessed? How would you get trackList instance if you have Album instance? In the View for example...

Re: Lightweight Relation Modeling with Backbone

Libor Nenadál — Tue, 01 May 2012 12:27:11 -0000

Looks promising! :-)

Re: Lightweight Relation Modeling with Backbone

Xxx — Thu, 01 Mar 2012 16:25:02 -0000

great alternative implementation of backbone-relational

Re: UI Corner: Twitter List Management

Gabriel — Sun, 15 May 2011 05:31:22 -0000

Great read. I kept thinking while reading it that the actual list use case is more closely tied to:

"Hey , I have a bunch of people that I follow and want to add them to a new list to help organize"

this makes your point entirely relevant. Great break down bro. +1

Re: Simple JS Multiton/Factory

Gabriel — Mon, 14 Mar 2011 15:46:17 -0000

You might even be able to get away with the same object, just adding a factory method onto it.

return {
instance : function(name){...},
factory : function(name){
// this is a bug in your implementation, passing in a name will set the name to
// "string"
name = typeof name === 'string' ? name : _default;
return create_instance(name);
}
}