-
Notifications
You must be signed in to change notification settings - Fork 47
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
Extend the "Web Application" Debug Configuration with an option to run an SDBG (or other) debug session automatically #48
Comments
Great idea! |
#124 - This will get uploaded to the snapshot later tonight.
Would this work? |
I may need to add something about the browser implementation. Anyway this will get uploaded tonight to the snapshot repo. |
Good to hear that you are picking up the idea. |
I didn't want to use the existing wiring I didn't believe it had all the properties I needed to configure the menus properly and I didn't want to break the existing one as of yet. |
OK but I think you cannot get-by without IDebugLaunch, because besides displaying these items in the menu, you need to be capable of launching a debugger once the user has selected it in the menu. That's exactly what IDebugLaunch is doing anyway isn't it? Currently the IDebugLaunch's extension point, com.google.gdt.eclipse.core.debugLauncher only has two properties:
<extension
point="com.google.gdt.eclipse.core.debugLauncher">
<extensions
class="com.github.sdbg.integration.jdt.ChromeDebugLaunch"
label="SDBG Chrome JS Debugger">
</extensions>
</extension> Note that the label is part of the extension point and not a property on the IDebugLaunch interface itself (which is good!). How about we enrich the above extension point with additional - possibly optional - properties that you need for the menu? (Even though I'm not yet sure what they would be?) |
Gotcha. I see what you're saying. I put the label in the class, figuring it might be generated. The other extension point wasn't wired up correctly as of yet but I can revisit it and fix it. I may have to rewrite some of the core to get it done. I was hoping to take a shortcut, but you're right. :) Well anyway, I'm off with the family today. I might get some time tonight, but I'd say I'll aim to get this done thursday. |
Ah, yeah I see it clearly now. Ugh, yeah, that should be an easy fix later. |
Turns out the extension IDebugLauncher was what I did sometime ago and I completely glitched when I came back to look at this. My mistake, I've returned it to its previous operation. Funny how that happens to me now in then. :) |
With the IDebugLaunch infrastructure in place, I think this won't be too difficult...
I think the "GWT" tab in the Web Application Debug Configuration can be extended as follows (ASCII art mockup follows):
|=== Debugging =============================|
| [x] Launch a debugging session |
| [ (a combo listing all IDebugLaunch contributions>) |
The text was updated successfully, but these errors were encountered: