I'm curious as to what you guys are cooking up for Angular...It seems like it could in theory be pretty easy as angular binds to plain objects, but I'm sure there are plenty of wrinkles. Glad we have brilliant minds such as yourselves to figure this stuff out!
Just off the top of my head I'm thinking in the query promise callback you could set the array to what forEach is observing via an angular.apply() call, since we're outside of angular. Or better yet somehow integrate the promise with forEach since this is what angular uses if I remember correctly. For saving changes, I'm not sure if breeze just iterates the model or needs notifications, if its the former than that would be easier I guess. Anyway keep up the great work!
0.74.2 includes a new Todo sample (Todo-Angular) that demonstrates Angular at work with Breeze. The new sample is an “almost” exact copy of the “knockout” Todo sample and we’ll be documenting it like the original within the next few days.
Ward Bell commented
Want you all to know that we see your votes for Angular and have you very much in mind.
Chris: perhaps you could elaborate on your callback comment. Our present practice is to provide a simple array of results and have you, the developer, pour them into the observable array of your choice. A KO app would pour it into a KO observableArray; a Backbone app might pour them into a Backbone.Collection. Would you have an Angular app behave differently?
Scott: that Sanderson post on the Throne of JS was excellent; the performance benefits would redound to KO as well.
Scott St.Cyr commented
This would be awesome. Knockout is a data binding library, but the coverage of Angular's framework really complements Breeze's. We're doing the planning for a large scale CRUD project, but really see Angular as the best choice for this project.