right now the api bindings have been essentially generated by a little piece of elisp. there are some serious problems, where :'s have been left in method names which cause incorrect JS to be generated (coffeescript's compiler is fine with this, so there's no error.)
there are other less serious problems, though. many selectors come in pairs like:
-foo
-setFoo:
those should be converted to @instanceProperty/@staticProperty so that we get getter/setters in JS as opposed to methods.
and there are other methods that look like:
-doFooWithBarAndBaz: @nativeSelector("doFoo:withBar:andBaz:")
the method name should either be "do" or "doFoo". There is some leeway here wrt what the other methods in the class look like.
right now the api bindings have been essentially generated by a little piece of elisp. there are some serious problems, where :'s have been left in method names which cause incorrect JS to be generated (coffeescript's compiler is fine with this, so there's no error.)
there are other less serious problems, though. many selectors come in pairs like:
-foo
-setFoo:
those should be converted to @instanceProperty/@staticProperty so that we get getter/setters in JS as opposed to methods.
and there are other methods that look like:
-doFooWithBarAndBaz: @nativeSelector("doFoo:withBar:andBaz:")
the method name should either be "do" or "doFoo". There is some leeway here wrt what the other methods in the class look like.