[javascript] fix #736185: add_onload / jQuery.bind() vs. jQuery.one() This patch introduces a new 'server-response' event and deprecates the 'ajax-loaded' event. - 'server-response' is triggered by postAjaxLoad() (instead of 'ajax-loaded'). - 'server-response' is also triggered on document.ready(). - The add_onload() method binds the javascript code the 'server-response' event whether or not it's an ajax request, thus removing the need of the jsoncall hackish parameter. The binding is done with jQuery.one() instead of jQuery.bind(). - The javascript callbacks will be passed two extra parameters : a boolean to indicate if it's an ajax request or not, the DOM node (result of the HTTP query). As javascript is what it is, callbacks can safely ignore those two parameters if they don't need them. Backward compatibility is maintained by triggerring an 'ajax-loaded' event when a 'server-response' is emitted.

[system]
adapter=native
# database driver (postgres or sqlite)
db-driver=sqlite
# database host
db-host=
# database name
db-name=tmpdb
# database user
db-user=admin
# database password
db-password=gingkow
# database encoding
db-encoding=utf8

[admin]
login = admin
password = gingkow

[ldapuser]
adapter=ldapuser
# ldap host
host=ldap1
# base DN to lookup for usres
user-base-dn=ou=People,dc=logilab,dc=fr
# user search scope
user-scope=ONELEVEL
# classes of user
user-classes=top,posixAccount
# attribute used as login on authentication
user-login-attr=uid
# name of a group in which ldap users will be by default
user-default-group=users
# map from ldap user attributes to cubicweb attributes
user-attrs-map=gecos:email,uid:login