Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wip backend plugins #178

Open
RaymondQiu opened this issue Nov 7, 2014 · 5 comments
Open

wip backend plugins #178

RaymondQiu opened this issue Nov 7, 2014 · 5 comments
Labels

Comments

@RaymondQiu
Copy link

Hey, I saw we included the wip backend plug-ins source code in after I installed nodeclipse, I did not see those backends if I chose the webkit debug launch configuration. Am I supposed to get the wip backends from the original google chrome dev tool update site?

@paulvi
Copy link
Member

paulvi commented Nov 11, 2014

Nodeclipse has chrome dev tool 0.3.9 fixed for debugging Node.js by @tomotaro1065 .

What is wip backends ?

@ghost
Copy link

ghost commented Nov 11, 2014

https://code.google.com/p/chromedevtools/wiki/WipBackends

WIP Backends is a design artifact of WebKit Remote Debugging Protocol client implementation. It allows to have several different protocol implementations behind the single SDK interface. Technically WIP backend is a sub-library that should be used together with the main SDK library. There are several of them.

This is how Java SDK tolerates the fact that different versions of Google Chrome/Chromium simultaneously available may have incompatible protocols.

WIP Backend is currently a user-visible detail. This means that it's a user responsibility to correctly select a proper WIP Backend before attaching from debugger. Each backend is presented in Debugger UI in Debug Configurations dialog with a small declaration of compatible browser versions.

The exact set of backends change from release to release. That's why they are normally listed in release notes.

WIP Backends are deployed as a separate Eclipse feature "ChromeDevTools SDK WIP Backends".

@paulvi
Copy link
Member

paulvi commented Nov 28, 2014

Why we are talking about WipBackends ?

What is the problem that is addressed?

@hwellmann
Copy link

The WebKit Protocol Debug Configuration has a dropdown list labelled "Wip backend". The list is empty. When launching the configuration, there is an error message complaining that no Wip backend is selected.

The real question is, how do I debug a client-side JavaScript web application in Nodeclipse, or is this possible at all?

@paulvi
Copy link
Member

paulvi commented Mar 2, 2015

OK, this is continuation of http://stackoverflow.com/questions/28787462/how-to-run-and-debug-an-angularjs-application-in-eclipse

The real question is, how do I debug a client-side JavaScript web application in Nodeclipse, or is this possible at all?

Nodeclipse started as effort to support Node.js dev in Eclipse, over time it included related and helping plugins, but how to use them is out of scope.

The last time I researched about client-side JavaScript debugging was a year or two ago, now I can't really advise. Also I don't think this is related to wip backend plugins.

@ALL I am doing Android dev now, no time to research on JavaScript.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants