Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Status and future outlook of the JSDT debugger


2017-01-23 15:02 GMT+01:00 Victor V. Rubezhny <vrubezhn@xxxxxxxxxx>:
Angelo,

sorry, unfortunately I found that your answers were moved to junk folder.

No problem Victor! Glad you can retry my patch. Don't hesitate to recontact me if you have some troubles.
Anyway many thanks for your help. A lot of users are waiting for TypeScript debugging. Hope Neon 3 or Oxygen will provide teh JSDT sourcemap debugging.
 

I'll try your contribution with typescript.java https://github.com/angelozerr/typescript.java/wiki/Installation-Update-Site.

Thanks,
Victor


On 01/22/2017 05:28 PM, Angelo zerr wrote:


2017-01-22 17:04 GMT+01:00 Gorkem Ercan <gorkem.ercan@xxxxxxxxx>:



On Sat, Jan 21, 2017 at 9:00 AM, Angelo zerr <angelo.zerr@xxxxxxxxx> 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?

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.markov@xxxxxxxxx>:
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@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
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
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
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
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Back to the top