Composer.js: a framework for building complex single-page applications

Re:Composer.js: a framework for building complex single-page... by krebby on Sunday January 25, 2015 @04:59PM (#8944429)

Disclosure: I work on Backbone from time to time. In the next version of Backbone we're removing the jQuery dependency from Backbone.History and making it easier to separate out from Backbone.View.

Adding support for MooTools should be as simple as overriding Backbone.ajax and a few methods from Backbone.View. There exist at least one or two projects that do this already that I know of, though I've never had a use for them myself.

[ Parent | on HN ]

Re:Composer.js: a framework for building complex single-page... by orthecreedence on Sunday January 25, 2015 @05:20PM (#8944481)

Thanks for the update! The things that Composer needs jquery/moo for are all compartmentalized into one place (called the adapter)...sounds like you guys are moving in the same direction.

I wish backbone hadn't tied itself so closely to jquery early on because I really like the project and could have seen myself building a lot on top of it (like composer's filtercollections or listcontroller), and now it seems both projects are occupying closer and closer to the same space. Who knows, this may be good though.

[ Parent | on HN ]

Re:Composer.js: a framework for building complex single-page... by krebby on Sunday January 25, 2015 @10:57PM (#8945466)

To be sure, Backbone has had "adapters" for a pretty long time. You just replace Backbone.$ and be on your way (there's a few for mootools, etc if you look hard enough). The latest changes just make this a bit easier so you can use native DOM / xhr methods if that's your particular bag of awesome.

[ Parent | on HN ]