Artur Adib
Artur Adib
By popular request. That seems to be the first thing that people want to know...
Basically it'd be nice to do many-to-one bindings like: ``` controller:{ 'click button#save1, click button#save2': function(){} } ``` A simple implementation without much code restructuring is to parse the controller...
Someone claims to have a working IE8 shim for `Object.watch()`: http://stackoverflow.com/questions/1029241/javascript-object-watch-for-all-browsers Not sure if that works on IE7... probably not. Anyway, if that's an acceptable solution, we can get rid...
Feature is deprecated. See e.g. setter in `.model.set()` and factory function. This might require cleaning up unit tests.
So that two Agility objects essentially share the same model. This enables multiple views per model.
These were suggested by @clyfe: - don't use Object.create, it's 95% slower than constructors http://jsperf.com/object-create-vs-crockford-vs-jorge-vs-constructor/21 - prefer plain old for(i=0; i
Some RESTful servers don't necessarily follow our conventions (e.g. body contains JSON object with id variable `id`, etc), so it might be useful to allow the user to manipulate that...
Backbone uses an argument to `.fetch()` to specify page: http://documentcloud.github.com/backbone/#Collection-fetch Should we do the same?
Don't pollute the `` with orphan `` tags!
Right now keyboard events return Qt's key codes. We should use browser codes. See this (scroll to the bottom): - http://unixpapa.com/js/key.html **NOTE**: This will require updating most `examples/`