Dan Becker wrote:
I think as long as they are not generated per component, then it makes
sense to put the proxy along with its binding code (e.g. atom.js with
binding-atom or binding-atom-abera, etc.)
+1
+1
It will also be useful to do the following:
- use an extension point to contribute the pieces of Javascript, the
current code with getResource won't work in an OSGi environment.
- make all proxies expose the same constructor to avoid the 'if
binding.jsonrpc' test in the implementation.widget invoker.
--
Jean-Sebastien
