<div dir="ltr">The varMapping aspect might need some explanation: With plain JS it is not possible to capture the internal state of functions (closures, closed values). The data bindings, as well as scripts you attach to objects, however, should be serializable. This means we need to capture this state somehow. When you want converters / updaters / scripts to be real closures you can use the "varMapping" option to pass in values from the outside. The underlaying mechanism is implemented in the lively.Closure class: $world.browseCode("lively.Closure", null, "lively.lang.Closure");</div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Sep 16, 2014 at 8:33 AM, Davide Della Casa <<a href="mailto:davidedc@gmail.com" target="_blank">davidedc@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Looking at this, spec for connections: + 'spec can be: {\n' + ' removeAfterUpdate: Boolean,\n' + ' forceAttributeConnection: Boolean,\n' + ' converter: Function,\n' + ' updater: Function,\n' + ' varMapping: Object\n' + '}', converter and updater are explained in a couple of docs, that’s cool. Any insight/organic explanation about what the others (removeAfterUpdate, forceAttributeConnection, varMapping) do and in which context they are necessary/useful? Online somewhere, papers anywhere, previous email threads? If not, can anybody give a sketch in this thread? Cheers! Davide Della Casa _______________________________________________ lively-kernel mailing list <a href="mailto:lively-kernel@hpi.uni-potsdam.de">lively-kernel@hpi.uni-potsdam.de</a> <a href="http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel" target="_blank">http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel</a> </blockquote></div> </div>