Thanks Gorkem for your answer. I will waiting for your launch to implement tern debugger (and now protractor debugger works too based on tern debugger). Tern debugger are based on node launch (today tern.java provide Webclipse, Nodeclipse and Program (just for run protractor)) which start a node application.
It will be easy to implement JSDT debugger inside tern.java when your launch will be available. Regard's Angelo 2016-01-15 16:23 GMT+01:00 Gorkem Ercan <gorkem.er...@gmail.com>: > On 15 Jan 2016, at 10:11, Angelo zerr wrote: > > Hi everybody, >> >> You can also use http://download.eclipse.org/webtools/jsdt/snapshots/ , >>> >> which is the same content, also wiped out between build. >> >> Many thanks Mickael. I have tried it and IMHO I think the JSDT debugger >> must be very simple without configuring something for node >> application. Webclipse >> for instance provides a very simple use of debugger (none offense with >> JSDT >> work, I give you just some user feedback). With Webclipse you can do : >> >> * create a simple test.js and do Run as... and it run it as node >> application. JSDT debugger doesn't provide that. >> * create a simple test.js and do Debug as... and it run in debug mode a >> node application. JSDT debugger doesn't provide that (just Rhino >> JavaScript >> is available). >> >> > Correct. JSDT is missing the convenient launch configurations. They are > planned for M7 > see https://wiki.eclipse.org/JSDT/JSDT_Neon_Plan#Run.2FDebug_support_for > > > Perhaps I'm wrong, but it seems that JSDT Debugger provide only Remote >> debugger. It should be very cool if we could do Run/Debug in any JS files >> and it start a node application with debug mode and no need to start at >> hand a node server. >> >> Anyway, many thank's for your work. >> >> Regard's Angelo >> >> >> 2016-01-15 9:20 GMT+01:00 Max Rydahl Andersen <mande...@redhat.com>: >> >> Hi Piotr, >>> >>> Max, >>> >>> We're excited to hear of the interest in the JavaScript Debugger space. >>> It >>> is great for the community to have different options available and to >>> spur >>> innovation. >>> >>> Just to avoid confusion, Webclipse does not "require a special >>> installation" as it is a standard plug-in installed into Eclipse from the >>> marketplace, and as such is also consumed by MyEclipse. >>> >>> Sorry, using the word "special" gave it a bad connotation. What I should >>> have written was a *separate* install. >>> >>> >>> Beyond all these plugins being based on common fundamentals - Chrome Dev >>> Tools, Webclipse does certainly go beyond with a number of improvements >>> including a full compatibility with existing JSDT Debug Framework API and >>> with more power-ups coming for Web dev soon. >>> >>> We look forward to finding opportunities to collaborate in the future as >>> opportunities arise. >>> >>> Sounds great - full compatibility with existing JSDT Debug Framework API >>> is one of the things we want to get to too; if you are interested in >>> helping here that would be awesome. >>> >>> btw. have you looked into the chrome dev tools renamed api and see if it >>> would be something you could use or would you continue bundling/using >>> your >>> separate fork ? >>> >>> Thanks, >>> Max >>> >>> Best regards, >>> Piotr Tomiak >>> >>> Angelo, >>> >>> Myeclipse use the same tech behind the scenes. Nodeclipse does the same. >>> Just that we collaborated with Google to get the code over to eclipse so >>> everyone gets it as opposed to make it something requiring a special >>> install. >>> >>> If you make it work for the eclipse jsdt debugger I'm pretty sure the >>> same >>> or similar is what myeclipse or Nodeclipse can do for theirs. >>> >>> this is why I recommended when we talked last about this to use the jsdt >>> debugger APIs instead of any webclipse or Nodeclipse specific code. >>> >>> Whatever you do - I hope it works :) >>> >>> /max >>> http://about.me/maxandersen >>> >>> On 08 Jan 2016, at 19:12, Angelo zerr <angelo.zerr@xxxxxxxxx <mailto: >>> angelo.zerr@xxxxxxxxx>> wrote: >>> >>> Hi Gorkem, >>> >>> Many thanks for your answer! I will try to test your work. >>> >>> My main goal is to support Run/Debug protractor inside AngularJS Eclipse. >>> >>> I think I will start with Webclipse (MyEclipse debugger) and after I will >>> implement it with your debugger. >>> >>> Thank's again! >>> >>> Regard's Angelo >>> >>> 2016-01-08 19:03 GMT+01:00 Gorkem Ercan <gorkem.ercan@xxxxxxxxx <mailto: >>> gorkem.ercan@xxxxxxxxx>>: >>> >>> On 8 Jan 2016, at 12:19, Angelo zerr wrote: >>> >>> Hi all, >>> >>> I have several questions about your _javascript_ Debugger: >>> >>> * can we play with it? where can we find it? >>> >>> Gerrit contribution is ongoing in >>> https://git.eclipse.org/r/#/c/63817/ >>> >>> * is it able to debug node application? >>> >>> Yes it is.. >>> >>> I'm very interested with this _javascript_ Debugger (if it >>> can support debug >>> of node application) to : >>> >>> * add a tern debugger to debug tern plugin inside tern.java. >>> Today it's >>> possible to debug tern plugins with MyEclipse _javascript_ >>> Debugger & >>> Nodeclipse _javascript_ Debugger. I would liek to support >>> your debugger too. >>> >>> I think those are also based on the Google's chromedevtools >>> plugin, so it will probably >>> not going to be a big effort for you. >>> >>> * try to debug AngularJS Protractor tests with your debugger >>> (I have more >>> and more people who wish run/debug protractor tests). I have >>> played with >>> MyEclipse _javascript_ Debugger and I can debug protractor >>> but conf is a >>> little complex. I would like to give you ideas to easy the >>> conf of >>> protractor. >>> >>> The initial contribution comes with a generic launch >>> configuration but we >>> do plan to add more specific (and easier) launch different JS >>> applications >>> so your input is welcome. >>> >>> Many thanks for your answer. >>> >>> Have a nice WE >>> >>> Regard's Angelo >>> ______________________________ >>> _________________ >>> wtp-dev mailing list >>> wtp-dev@xxxxxxxxxxx <mailto:wtp-dev@xxxxxxxxxxx> >>> To change your delivery options, retrieve your password, or >>> unsubscribe from this list, visithttps:// >>> dev.eclipse.org/mailman/listinfo/wtp-dev >>> >>> ------------------------------ >>> >>> wtp-dev mailing list >>> wtp-dev@xxxxxxxxxxx wtp-dev@xxxxxxxxxxx >>> To change your delivery options, retrieve your password, or >>> unsubscribe from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/wtp-dev >>> ------------------------------ >>> >>> wtp-dev mailing list >>> wtp-dev@xxxxxxxxxxx wtp-dev@xxxxxxxxxxx >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/wtp-dev >>> >>> ------------------------------ >>> >>> wtp-dev mailing list >>> wtp-dev@eclipse.org >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/wtp-dev >>> >>> /max >>> http://about.me/maxandersen >>> >>> _______________________________________________ >>> wtp-dev mailing list >>> wtp-dev@eclipse.org >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/wtp-dev >>> >>> _______________________________________________ >> wtp-dev mailing list >> wtp-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/wtp-dev >> > > > -- > Gorkem > > _______________________________________________ > wtp-dev mailing list > wtp-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/wtp-dev >
_______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
