> On Sat, Jan 21, 2017 at 4:06 AM, Ivan Markov <ivan.mar...@gmail.com> > wrote: > > > Dear all, > > > > Being the maintainer of sdbg.github.io, the recent (2015-2016) rebirth > of > > the JSDT tooling is of course something I'm interested it. > > (... and unfortunately something I've slept through). > > > > Regarding the JSDT debugging story, as far as I understand there are two > > codebases in use: > > 1) The original JSDT Debug plugins, which support only Rhino > > 2) A fork of the old Chromedevtools-Java tooling from Google (last when I > > looked at it - still in the Google Code times, it was a completely > > independent set of Eclipse plugins, is this still the case?) > > > > The following question to follow (obviously): > > Have you considered using the SDBG codebase, and if not, why not? > > Technical or legal issues? > > > > > No, we have not considered it. At least I have assumed it to be GWT only. >
That's a pity, because the SDBG core is completely GWT agnostic. If you've seen the heading of the website, it says: "...and for JavaScript with Sourcemaps in general". I mean, GWT today is in no way different than any other <language-XYZ>-to-JavaScript transpiler, like TypeScript, CofeeScript, Scala.js etc. - it just takes a bunch of source files and produces JS output + sourcemaps. The GWT specifics - as much as there are any - are isolated in an additional optional plugin (com.github.sdbg.integration.jdt). As the plugin name hints, these are for the most part not even GWT - but Eclipse JDT specific: if you transpile from Java to JavaScript, SDBG can adopt the Eclipse JDT Java breakpoints and "pretend" that these are its own breakpoints, which is very valuable when you are working in an integrated J2EE+GWT environment and do not want to think whether you need a serverside = Java JDT, or a clientside = SDBG breakpoint. BTW, when I setup for forking the Dart Tools Eclipse debugging codebase (in 2013) to implement my own debugger, I did not do it lightly. Before that, I was fiddling with the classic (Rhino) JSDT debugger infrastructure and the Chromedevtools-Java codebase for a couple of months, but the results were not encouraging: - Already then Chromedevtools-Java was dead, with its sole maintainer no longer at Google. The JSDT debugger was also stagnating, I must say. As a comparison, Dart Tools was still very much alive and kicking at that time. - The Dart Tools debugger (also using the Chrome WIP protocol) had sourcemaps support built in. So I was able to get something up and running based off their codebase in less than a month. - Last but not least, both the JSDT debugger, as well as Chromedevtools-Java had implemented their own extra layer of abstraction on top of the core Eclipse debug (IValue, IDebugTarget, etc.) model. No offense, maybe they had their reasons to do so, but in practice, when I was prototyping sourcemaps support in JSDT and Chromedevtools-Java, these abstractions had the tendency to get in my way, rather than save me work. Anyway, just my 2c. Cheers, Ivan > > > Cheers, > > Ivan > > > > > > > > > > _______________________________________________ > > 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 > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://dev.eclipse.org/mailman/private/wtp-dev/attachments/20170122/9cd406c3/attachment.html > > > > ------------------------------ > > Message: 2 > Date: Sun, 22 Jan 2017 11:04:39 -0500 > From: Gorkem Ercan <gorkem.er...@gmail.com> > To: "General discussion of project-wide or architectural issues." > <wtp-dev@eclipse.org> > Subject: Re: [wtp-dev] Status and future outlook of the JSDT debugger > Message-ID: > <CA+X37c= > tud6o4dsm+ora4s7zvyomkm8ya4d54vvnqw7e34-...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Sat, Jan 21, 2017 at 9:00 AM, Angelo zerr <angelo.z...@gmail.com> > wrote: > > > Hi Ivan, > > > > I'm very glad that you post this question because in my case I need to > > debug TypeScript (in other mean debugging with source map). > > > > So I have created a patch for JSDT Chrome debugger at > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=487465 and sourcemap code > > is based on your sdbg work. See my comment at https://bugs.eclipse.org/ > > bugs/show_bug.cgi?id=487465#c7 > > > > My patch is not perfect but I hope JSDT Team will accept it and hope guys > > like you will improve it. > > > > > I believe Victor tried to use your patch for minified JS cases and could > not get it to work. > Are you in touch with him? > > > > > Regard's Angelo > > > > 2017-01-21 10:06 GMT+01:00 Ivan Markov <ivan.mar...@gmail.com>: > > > >> Dear all, > >> > >> Being the maintainer of sdbg.github.io, the recent (2015-2016) rebirth > >> of the JSDT tooling is of course something I'm interested it. > >> (... and unfortunately something I've slept through). > >> > >> Regarding the JSDT debugging story, as far as I understand there are two > >> codebases in use: > >> 1) The original JSDT Debug plugins, which support only Rhino > >> 2) A fork of the old Chromedevtools-Java tooling from Google (last when > I > >> looked at it - still in the Google Code times, it was a completely > >> independent set of Eclipse plugins, is this still the case?) > >> > >> The following question to follow (obviously): > >> Have you considered using the SDBG codebase, and if not, why not? > >> Technical or legal issues? > >> > >> Cheers, > >> Ivan > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://dev.eclipse.org/mailman/private/wtp-dev/attachments/20170122/96e1b3c6/attachment.html > > > > ------------------------------ > > Message: 3 > Date: Sun, 22 Jan 2017 17:28:28 +0100 > From: Angelo zerr <angelo.z...@gmail.com> > To: "General discussion of project-wide or architectural issues." > <wtp-dev@eclipse.org> > Subject: Re: [wtp-dev] Status and future outlook of the JSDT debugger > Message-ID: > <CAKLdLg805njszS5i=ghB= > 6v8yczascl2qgebmhervqjvlqo...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 2017-01-22 17:04 GMT+01:00 Gorkem Ercan <gorkem.er...@gmail.com>: > > > > > > > > > On Sat, Jan 21, 2017 at 9:00 AM, Angelo zerr <angelo.z...@gmail.com> > > wrote: > > > >> Hi Ivan, > >> > >> I'm very glad that you post this question because in my case I need to > >> debug TypeScript (in other mean debugging with source map). > >> > >> So I have created a patch for JSDT Chrome debugger at > >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=487465 and sourcemap code > >> is based on your sdbg work. See my comment at > https://bugs.eclipse.org/bu > >> gs/show_bug.cgi?id=487465#c7 > >> > >> My patch is not perfect but I hope JSDT Team will accept it and hope > guys > >> like you will improve it. > >> > >> > > I believe Victor tried to use your patch for minified JS cases and could > > not get it to work. > > Are you in touch with him? > > > > Victor contacted me about that, I gave him some informattion, but I think > he is very busy with other topics. > > > > > > > >> Regard's Angelo > >> > >> 2017-01-21 10:06 GMT+01:00 Ivan Markov <ivan.mar...@gmail.com>: > >> > >>> Dear all, > >>> > >>> Being the maintainer of sdbg.github.io, the recent (2015-2016) rebirth > >>> of the JSDT tooling is of course something I'm interested it. > >>> (... and unfortunately something I've slept through). > >>> > >>> Regarding the JSDT debugging story, as far as I understand there are > two > >>> codebases in use: > >>> 1) The original JSDT Debug plugins, which support only Rhino > >>> 2) A fork of the old Chromedevtools-Java tooling from Google (last when > >>> I looked at it - still in the Google Code times, it was a completely > >>> independent set of Eclipse plugins, is this still the case?) > >>> > >>> The following question to follow (obviously): > >>> Have you considered using the SDBG codebase, and if not, why not? > >>> Technical or legal issues? > >>> > >>> Cheers, > >>> Ivan > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> 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 > >> > > > > > > _______________________________________________ > > 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 > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > https://dev.eclipse.org/mailman/private/wtp-dev/attachments/20170122/32645e93/attachment.html > > > > ------------------------------ > > _______________________________________________ > 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 > > End of wtp-dev Digest, Vol 143, Issue 16 > **************************************** >
_______________________________________________ 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
