WOW! WatchJS became so popular that I've been pushed to migrate it to GitHub
https://github.com/melanke/Watch.JS
Just kidding
WOW! WatchJS became so popular that I've been pushed to migrate it to GitHub
https://github.com/melanke/Watch.JS
Just kidding
It is not that obvious from the readme that watchAll
only watches for properties that were defined at the moment of call to watchAll
.
E.g.
var obj = {
attr1: 0,
};
ex3.watch(function(){
alert("Something was changed");
});
ex3.attr0 = 1; //triggers the observer; the alert is shown.
ex3.attr1 = 1; //does not trigger the observer; the alert is not shown.
@penartur it is explained in the paragraph "Chill out, no surprises, new attributes will not be considered"
This is really useful. Thanks. One question: when watching more than one properties, is there a way to see what and how it was changed? i.e.:
o.watch(["x","y","z"], function (id, oldval, newval) {
console.log( "o." + id + " changed from " + oldval + " to " + newval );
});
With the new version of Watch.JS it is possible
Here is a sample:
http://jsfiddle.net/XnbXS/1/
Read the short-full-documentation:
https://github.com/melanke/Watch.JS
EmberJS is pretty much similar to BackboneJS, isn't it?
The purpose of WatchJS is to give freedom to the developer.
"with Watch.JS you will not have to change your way to develop"
WatchJS use your objects, anyway you want to build them.
EmberJS force you to use his constructor. I dont like it