As I don't have IDEA on my machine, but have used Visual Studio Code on previous projects, I gave it a go.
As far as I can tell, it works for basic development very well. The main tools are the same (JDK11&gradle).
@berry120: if you think this could complicate the development process, please veto this PR.
I offer three changes to Quelea sources, that could help someone else use vscode for development.
launch.json file for the vscode debugger. There are instructions for the debugger how to start Quelea. It can optionally start the other utilities as well (LabelChecker, USEnglishConverter, ImageChecker, ReleaseSummaryGenerator, GZMaxFileCompressor).
Documentation added to SETUP.md and some screenshots.
One mode directory added to .gitignore - all files in Quelea/bin. Not sure why it wasn't already there. Gradle adds many new files during build to Quelea/bin. Class-files were always ignored by git, so no issue with them. But it also generates PNG icons and a CSS file there (probably copies from a source folder). These files pop-up in git as new/unstaged, but I believe they shouldn't.
As I don't have IDEA on my machine, but have used Visual Studio Code on previous projects, I gave it a go. As far as I can tell, it works for basic development very well. The main tools are the same (JDK11&gradle). @berry120: if you think this could complicate the development process, please veto this PR.
I offer three changes to Quelea sources, that could help someone else use vscode for development.
launch.json
file for the vscode debugger. There are instructions for the debugger how to start Quelea. It can optionally start the other utilities as well (LabelChecker, USEnglishConverter, ImageChecker, ReleaseSummaryGenerator, GZMaxFileCompressor)..gitignore
- all files inQuelea/bin
. Not sure why it wasn't already there. Gradle adds many new files during build toQuelea/bin
. Class-files were always ignored by git, so no issue with them. But it also generates PNG icons and a CSS file there (probably copies from a source folder). These files pop-up in git as new/unstaged, but I believe they shouldn't.