Hacker News Reader

Comment by jeromegn | Hacker News Reader

A little backstory...

With the help of jashkenas, I created this app to test my implementation of Backbone.js for MooTools (http://github.com/jeromegn/backbone-mootools) and my localStorage adapter (http://github.com/jeromegn/Backbone.localStorage for those interested). It just so happened that jashkenas had been aching for a decent example app, so he reported it to jQuery and included it in the repository.

My own version of this demo is available here (with an extra sorting feature, and built on MooTools) http://localtodos.com/ (source: http://github.com/jeromegn/localtodos)

Hope you like it.

View on HN

Can you describe your experience with backbone? Now that you have built an app with it, do you recommend it? Or perhaps wait till it matures a little?

Since I'm no programming nor javascript wizard, I needed some help from Jeremy. I know my way around MVC since I've been doing some Ruby on Rails in my time.

My experience with more advanced Javascript is with MooTools, so I found it familiar to build Class-like objects. I rather enjoyed the experience and I'll be using it to replace the codebase for my more complex project.

The documentation is exhaustive and with that example app, annotated et al., it's even better. I also am very confident in Jeremy's skills as the project maintainer, he helped me a lot and has proven he creates great Javascript libraries.

The API seems stable enough. From Backbone 0.1.2 to 0.2, there weren't that many differences in the API, mostly nice additions.

I've already used it for my admin app as well, and in the process submitted some patches to backbone as well. It's quite nice how unobtrusive it is. I wrote a small jquery plugin that converts a form & table into fully functional crud with client & server side validation.

It looks very nice. One small UI request, you should only be able to edit one existing item at a time, so if you are currently editing one item and you double click another item, the first should be committed.

Ah, that's a good one. I'll add that.

also, while editing, if I double clicked to edit and clicked out for some reason, the changes are not committed yet.

I think the more intuitive way of doing it is adding some sort of a commit-on-click-out feature ..

Good call -- I've updated the example to close and save the todo when you blur the input field. Thanks.

Updated localtodos.com to reflect the changes + some additional styling.

I've updated the app to work that way -- nice idea. Here's the relevant change, for the curious:

http://documentcloud.github.com/backbone/docs/todos.html#sec...

Reply on news.ycombinator.com