I offer, for your scrutiny, the first version of Knockout Meteor. It
creates Knockout Observables based on queries against Meteor Collections.
When the results of those queries change, Knockout Meteor will ensure that
the associated Observables are updated.
and DOM elements using an expressive and declarative binding syntax. The
models (and hence your UI) based on incoming data, updating only that which
has changed. These are two strengths that Meteor does not currently possess.
Meteor, however, makes it incredibly easy to ferry model data back and
forth between a server and its connected clients. Knockout Meteor acts as a
bridge between these two frameworks. It lets you construct queries against
Meteor Collections that behave like Knockout Observables that update
themselves atomically and automatically when the results of those queries
I look forward to your comments, issues, opinions, and any pull requests
you come up with.