JS debugging....I don't get it Follow
I was pretty excited to see JS debugging as one of the new features in Diana, but on attempting it, I'm rather baffled by how its supposed to work.
For one thing, it looks like it only lets me pick local .html files. In the real world, js often talks to some sort of backend, and the starting point is often things like jsp pages. I don't see how I can debug any real running application the way things are now. Am I missing something?
Ideally the run configuration would let me specify a url, and maybe I can specify some sort of configuration which says which directory on the FS corresponds to the web root on the server. It'd be great if this could interact with the 'open browser' option in running an appserver. So I could fire up my appserver, have a window show the contents of the page I'd like to test, with js debugging already functional for that page!
Please sign in to leave a comment.
I'm really excited about JS debugger too. I hope use cases covered by previous poster will be covered in later builds. But for now I cound not use JS debugger even for simple "hello world" .html file.
Hani Suleiman wrote:
We are working on it. Support for debugging of remote html files will be
"Develop with pleasure!"
what Hani mentioned is pretty true. Beside the "real environments" already discussed I would like to see the possibility to jump into a running application although no breakpoints were specified. The debugger may start (or offer starting) when time consuming or defect JS snippets are detected.
I have to point out I did not succeed to see the debugger in action at all. The JS breakpoints are ignored in my plain JS example I created. Is there any special trick or hidden feature I do not know yet? ;)