Posterous Spaces is built on Backbone.js
technology.posterous.com
Posterous Spaces is built on Backbone.js
1–10 of 12 posts
Re: Posterous Spaces is built on Backbone.js
#2http://backbonejs.org/#examples
If you're interested, email me a brief paragraph of description, and a 550px-wide screenshot of Posterous Spaces.
Edit -- Adam followed up, and I've posted it up here:
Re: Posterous Spaces is built on Backbone.js
#3I'd be glad to feature y'all in the list of example sites on the Backbone homepage: http://backbonejs.org/#examples If you're interested, email me a brief paragraph of description, and a 550px-wide screenshot of Posterous Spaces. Edit -- Adam followed up, and I've posted it up here: http://backbonejs.org/#examples-posterous
Re: Posterous Spaces is built on Backbone.js
#4I'd be glad to feature y'all in the list of example sites on the Backbone homepage: http://backbonejs.org/#examples If you're interested, email me a brief paragraph of description, and a 550px-wide screenshot of Posterous Spaces. Edit -- Adam followed up, and I've posted it up here: http://backbonejs.org/#examples-posterous
I was just going to say, this must be the biggest Backbone.js-in-production project yet. But after re-checking the example page, I'm guessing Pandora and LinkedIn's mobile site are higher notches for Backbone.
Our new Posterous Bar -- http://blog.posterous.com/introducing-the-new-posterous-bar -- was also built using a few Backbone views for those interested. We love Backbone.
Re: Posterous Spaces is built on Backbone.js
#5Re: Posterous Spaces is built on Backbone.js
#6The article itself doesn't go very deep in technical details. So I wonder how they manager there views, especially deleting unused events from models and collection, managing livecycle of views etc. Another interesting think to know is, how they handle subviews and the communication between them.
We keep our models and collections very bare. They essentially just have methods that communicate with our API and that's it.
We handle subviews by appending them in the render method. For instance, in a post list, we append each post list item in the post list's render method.
I'm sorry if that doesn't answer your question. I guess the essence of it is we append subviews in the render method. Is there anything specific about this you want to know?
Re: Posterous Spaces is built on Backbone.js
#7The article itself doesn't go very deep in technical details. So I wonder how they manager there views, especially deleting unused events from models and collection, managing livecycle of views etc. Another interesting think to know is, how they handle subviews and the communication between them.
I didn't go into much detail because I could have gone on and on forever. We keep our models and collections very bare. They essentially just have methods that communicate with our API and that's it. We handle subviews by appending them in the render method. For instance, in a post list, we append each post list item in the post list's render method. I'm sorry if that doesn't answer your question. I guess the essence…
Re: Posterous Spaces is built on Backbone.js
#8PS: I'm about to start reading the new Javascript Web Applications book by Alex MacCaw as I'm very interested in learning more client-side development. This is very new to me.
Re: Posterous Spaces is built on Backbone.js
#9Coming from server-side MVC dev, the line "Views: The meat of our business logic occurs here." was surprising. I thought the point of MVC was to decouple the logic from the views. PS: I'm about to start reading the new Javascript Web Applications book by Alex MacCaw as I'm very interested in learning more client-side development. This is very new to me.
Backbone views handle event binding and rendering, so they're more similar to Rails controllers, if anything.
Re: Posterous Spaces is built on Backbone.js
#10Earlier quoted context omitted.
I didn't go into much detail because I could have gone on and on forever. We keep our models and collections very bare. They essentially just have methods that communicate with our API and that's it. We handle subviews by appending them in the render method. For instance, in a post list, we append each post list item in the post list's render method. I'm sorry if that doesn't answer your question. I guess the essence…
Do you have any mechanism to unbind events on model/collections you've made in views/subviews, or will the bind methodes will live forever. Do you have something like a global eventbus or how your views comunicate with each other?