On 01/15/2016 10:23 AM, Gorkem Ercan wrote:
Exactly. And just for clarification. We just moved the original chrome dev tools to JSDT with some essential changes like renamed package name spaces. There is still a lot of work to make this debugger useful for JSDT users. Some of these tasks are already in the JSDT plan (see the Gorkem's link above) but we are going to create a bunch of new specific bugzillas (I hope it will happen next week) and add the most important of them to the plan. Our goal is to integrate the debugger with JSDT editor and JS projects, introduce launch configurations for nodejs and web applications, support the latest versions of WIP protocols, fix bugs, etc. I hope when we create all bugzillas for taks/issues that we are already aware of then it will be much more easy for everybody to see what we are missing and what else we have to do.
Back to the top