Re: javascript binding in a browser

2014-09-02 Thread Ernest Allen
environment. I'll grab your latest and use that in my experiments. Thanks again for the help and the excellent work. It is fun the rediscover javascript again. -Ernie - Original Message - From: "Fraser Adams" To: proton@qpid.apache.org Sent: Monday, September 1, 2014 2:

Re: javascript binding in a browser

2014-09-01 Thread Fraser Adams
Hi again Ernie, I've just committed a few improvements. In terms of debugging if you specify cmake .. -DCMAKE_BUILD_TYPE=Debug or cmake .. -DCMAKE_BUILD_TYPE=RelWithDebInfo it will do a build with no JavaScript optimisations and no closure compiler so any JavaScript errors will be a bit more hu

Re: javascript binding in a browser

2014-08-31 Thread Fraser Adams
Re my last mail, I meant to say using the proton.js is fine BTW, the makefile actually builds it into fadams-javascript-binding/bld/proton-c/bindings/javascript which is what you'd normally get with CMake but then copies it to the node_modules directory 'cause that's generally more useful. For

Re: javascript binding in a browser

2014-08-31 Thread Fraser Adams
Hi Again Ernie, I take it back, it *was* something you've done ;-p Or rather it was something that you didn't do. If you look at the last line of the original send.js it says: tracker = messenger.put(message); But your last line below says simply: messenger.put(message); The error is simply

Re: javascript binding in a browser

2014-08-30 Thread Fraser Adams
Hi again Ernie, There's no real reason why it shouldn't work in a browser except that I haven't tried it in a while, it tends to be easier to try things out using node.js and doing some more browser tests was on my TODO list :-) The error "Uncaught TypeError: Cannot read property 'fa' of null

javascript binding in a browser

2014-08-30 Thread Ernest Allen
Hi Fraser, I'm trying to run the proton javascript bindings from within a browser. I'm getting various errors depending on the way I'm doing it and I was hoping you could shed some light on the correct approach. I have node recv.js running in a separate window. The first way I tried was just inc