5 ms·
BackFire: Firebase bindings for Backbone.js
- ianstormtaylor 14y agoThis is seriously awesome. We hacked together our own weird version of this while working on Socrates—can't wait to try it out on our next project.
- mikeknoop 14y agoAwesome stuff. Is there an authentication mechanism built in somewhere?
- anant 14y agoGreat question - the bindings can take a regular Firebase reference object instead of a URL as well. If you had authenticated the Firebase reference using any of the regular Firebase methods (like Simple Login), the collection will simply inherit them.
- anant 14y agoFor reference, Simple Login is a convenient way to add authentication to a Firebase app using Facebook, Twitter, Persona, Github or just plain old email/password identities. More at https://www.firebase.com/docs/security/simple-login-overview.html https://www.firebase.com/docs/security/simple-login-overview...
- jimmytttt 14y agoThe example ToDo contains: - Decrease entropy - Slam a revolving door http://firebase.github.com/backfire/ http://firebase.github.com/backfire/
- knes 14y agoAwesome, would be great to see this for Angularjs too!
- anant 14y agoThanks, AngularJS is definitely on our roadmap!
- jashkenas 14y ago@anant -- Could you talk a little bit about the bits you needed to build in order to get the Collection to synchronize with Firebase? Was it a piece of cake? Did you run into any trouble?
- anant 14y agoThe bindings simply extend the Collection object and override certain methods on it (add, remove, etc.) to do the corresponding Firebase operations. We did run into a few relatively minor issues; for example when doing a smart update to a collection, Backbone seems to trigger a remove event immediately followed by an add event for a model that hasn't changed. We still have more work to do with the bindings (we don't have a Firebase.Model object for instance), but I don't expect any major roadblocks. All in all, piece of cake!
- jashkenas 14y ago> All in all, piece of cake! Glad to hear it! > when doing a smart update to a collection, Backbone seems > to trigger a remove event immediately followed by an add > event for a model that hasn't changed. That certainly doesn't sound right -- if you've got something reproducible there, I'd encourage you to open a ticket.
- thruflo 14y agoFWIW having first contributed patches to the backbone-firebase lib, l got annoyed with it clobbering backbone.sync and rewrote a similar but slightly different binding here: https://github.com/thruflo/mobone/blob/master/firebase.coffee https://github.com/thruflo/mobone/blob/master/firebase.coffe...