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

Add a section about vscode? #53

Open
zindy opened this issue Dec 8, 2022 · 1 comment
Open

Add a section about vscode? #53

zindy opened this issue Dec 8, 2022 · 1 comment

Comments

@zindy
Copy link
Contributor

zindy commented Dec 8, 2022

Hello,

this is something I'm working on: I've been using VSCode quite a lot to develop and debug QuPath, on Windows, Linux and more recently MacOSX.

I think I could write a section about how to do this if it helps bringing in people. I haven't been able to push to my github just quite yet, but I think this will be trivial to sort.

So:

  • where to get vscode and what Extensions are needed
  • where to download the JAVA JDK from (I use Microsoft's build)
  • Git clone, add a .vscode config
  • Initial Gradle build using the "command line arguments" button
  • Debugging QuPath, hotswapping code (I'm a very very basic user of this)
  • Git commit / Git push

If there are any expert users, I would happily accept any other useful tidbits!

Cheers,
Egor

@petebankhead
Copy link
Member

I've been asked about QuPath + VSCode before and tried unsuccessfully to set it up nicely. I'd be really keen to read your method and try it out.

I rely heavily on hotswapping in eclipse, which works fantastically - it's probably the main thing that keeps me from using something else. But setting things up in eclipse is awkward too - it'd be great to see instructions for other IDEs.

Could you post it on image.sc instead?

That way it can be online pretty much immediately and discussion can happen there. I'm apprehensive about encouraging PRs here, because discussing/reviewing them can take a lot of time and people who might have useful feedback probably won't see the work until it's merged.

Since image.sc and the docs now both use markdown, it should be relatively straightforward to transfer the content over later if needed.

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

No branches or pull requests

2 participants