--
Please use prefixes: [Pony] Feature requests, [TestCase] Test cases, [Bug] if you're lazy. If you have contract work or position for FuturesJS devs, prefix [Bounty] or [Job].
-----
To post to this group, send email to futures-j...@googlegroups.com
To unsubscribe from this group, send email to
futures-javascr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/futures-javascript?hl=en
I've been using it for a few days now prototyping a new feature of my app. So far its been really great, although I'm currently trying to work out the best way to deal with model relationships (models that contain other models or collections).
I would highly recommend you try it out. Its made by DocumentCloud who makes underscore.js, is an open source project on github, has decent docs and an active irc channel, and seems to be quickly gaining traction. Its been called a lightweight alternative to sproutcore, cappicino, and javascriptmvc.
The biggest issue I have with it is that it lacks more sophisticated example apps. Its hard to determine how to go from a simple todo app with a single model type and a single collection to a full blown app with dozens of models types and collections, all of which are inter-related.
Tauren