It's good to see more developments in this area, as I liked the management offered by projects such as SproutCore, but the stack as a whole was very heavyweight.
I did work on my own take, using some of the ideas from SproutCore, though didn't get very far in polish (http://github.com/erudites/eventful)
I've only had a brief look, but the dependency tracking looks much cleaner than other solutions I've seen for partial template redrawing.
Do Backbone and Knockout interact well, or are there conflicts in getting them to play nicely together?
There's a fair amount of overlap between them, so I'm not sure you'd want to use both. Backbone has a more integrated persistence layer, but that layer is pretty tied to the model. It wouldn't make sense to use that and use Knockout for the view. There may be some useful cross-pollination, but that should just be by both frameworks adding/changing features.
Comments
It's good to see more developments in this area, as I liked the management offered by projects such as SproutCore, but the stack as a whole was very heavyweight.
I did work on my own take, using some of the ideas from SproutCore, though didn't get very far in polish (http://github.com/erudites/eventful)
I've only had a brief look, but the dependency tracking looks much cleaner than other solutions I've seen for partial template redrawing.
Do Backbone and Knockout interact well, or are there conflicts in getting them to play nicely together?
There's a fair amount of overlap between them, so I'm not sure you'd want to use both. Backbone has a more integrated persistence layer, but that layer is pretty tied to the model. It wouldn't make sense to use that and use Knockout for the view. There may be some useful cross-pollination, but that should just be by both frameworks adding/changing features.