Debugger struggles

[Eneroth3]

I'm struggling a bit with setting up the debugger.

This repo referencing the sketchup-ruby-api-tutorials repo which in turn references the sketchup-ruby-debugger repo, creates a quite large mental stack trace. Reading each new page gets harder as you have to read it with all "calling" pages in mind to figure out what steps apply and what should be ignored. For instance, the instructions in sketchup-ruby-api-tutorials for setting up a VSCode task seems redundant in the context of sketchup-extension-vscode-project already defining tasks, and the command line argument in sketchup-ruby-debugger seems redundant when there is already a task.

Ideally the instructions for this repo should be "standalone" and not require additional instructions in turn referencing additional instructions. Even better would be if the right dll/dylib file could be fetched and placed where it is needed automatically.

Also I can't find the Debug pane in VSCode. It seems to be renamed to Run in my version, and having a different icon, or it's really a different pane.

The Task menu of VSCode is now named Terminal.

[thomthom]

Ideally the instructions for this repo should be "standalone" and not require additional instructions in turn referencing additional instructions. Even better would be if the right dll/dylib file could be fetched and placed where it is needed automatically.

This adds additional maintenance cost. Unless syncing things up can be automated I'd try to find some way to better document/explain this.

Also I can't find the Debug pane in VSCode. It seems to be renamed to Run in my version, and having a different icon, or it's really a different pane.

Yes, I think they might have updated the UI recently.

The Task menu of VSCode is now named Terminal.

Hm.. I'm not sure if those are the same... ?

[Eneroth3]

I can't remember if sketchup-ruby-api-tutorials gave me anything except the reference to sketchup-ruby-debugger. If not, maybe this repo can link directly to the download page for sketchup-ruby-debugger and omit the intermediate steps. sketchup-ruby-debugger could perhaps also have an extra level of headers for Installation and operation to make it more clear exactly what steps are relevant and what are not in this context.