Skip to content

Commit

Permalink
Initial functioning commit for QP 0.5.0
Browse files Browse the repository at this point in the history
  • Loading branch information
MichaelSNelson committed Feb 2, 2024
1 parent 1e6d460 commit 2c2e524
Show file tree
Hide file tree
Showing 16 changed files with 2,032 additions and 26 deletions.
42 changes: 42 additions & 0 deletions .github/workflows/gradle.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# This workflow uses actions that are not certified by GitHub.
# They are provided by a third-party and are governed by
# separate terms of service, privacy policy, and support
# documentation.
# This workflow will build a Java project with Gradle and cache/restore any dependencies to improve the workflow execution time
# For more information see: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-java-with-gradle

name: Java CI with Gradle

on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
workflow_dispatch:

permissions:
contents: read

jobs:
build:

runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v3
- name: Set up JDK 17 # TODO: check Java version
uses: actions/setup-java@v3
with:
java-version: '17'
distribution: 'temurin'
- name: Validate Gradle wrapper
uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b
- name: Build with Gradle
uses: gradle/gradle-build-action@67421db6bd0bf253fb4bd25b31ebb98943c375e1
with:
arguments: build
- uses: actions/upload-artifact@v3
with:
name: jar
path: build/libs
retention-days: 7
33 changes: 33 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
name: Make draft release

on:
push:
tags: ["v*"]
workflow_dispatch:

jobs:
release:
permissions:
contents: write
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Define version env variable
run: |
echo "VERSION=$(echo ${{ github.ref_name }} | sed -r 's/v([0-9]+\.[0-9]+\.?[0-9]?)/\1/'" >> $GITHUB_ENV
- name: Set up JDK 17
uses: actions/setup-java@v3
with:
java-version: '17'
distribution: 'temurin'
- name: Validate Gradle wrapper
uses: gradle/wrapper-validation-action@v1.1.0
- name: Build with Gradle
uses: gradle/gradle-build-action@v2.7.1
with:
arguments: build -Pversion=$VERSION
- name: Release
env:
GH_TOKEN: ${{ github.token }}
run: gh release create --draft ${{ github.ref_name }} --title ${{ github.ref_name }} build/libs/*
65 changes: 41 additions & 24 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,24 +1,41 @@
# Compiled class file
*.class

# Log file
*.log

# BlueJ files
*.ctxt

# Mobile Tools for Java (J2ME)
.mtj.tmp/

# Package Files #
*.jar
*.war
*.nar
*.ear
*.zip
*.tar.gz
*.rar

# virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
hs_err_pid*
replay_pid*
# Javadocs
docs/

# Maven
deploy/
target/
log/

# IntelliJ
.idea/
*.iml
out/

# Gradle
# Use local properties (e.g. to set a specific JDK)
gradle.properties
build/
.gradle/
gradle.properties

# Eclipse
.settings/
.project
.classpath

# VSCode
.vscode/

# Mac
.DS_Store

# Java
hs_err*.log

# Other
*.tmp
*.bak
*.swp
*~.nib
*thumbs.db
bin/
117 changes: 115 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,115 @@
# basic-stitching
Based on QuPath extension template - for basic tiling with no overlap resolution
# QuPath extension template

This repo contains a template and instructions to help create a new extension for [QuPath](https://qupath.github.io).

It already contains two minimal extensions, so the first task is to make sure that they work.
Then, it's a matter of customizing the code to make it more useful.

> There are two extensions to show that you can use either Java or Groovy.
## Build the extension

Building the extension with Gradle should be pretty easy - you don't even need to install Gradle separately, because the
[Gradle Wrapper](https://docs.gradle.org/current/userguide/gradle_wrapper.html) will take care of that.

Open a command prompt, navigate to where the code lives, and use
```bash
gradlew build
```

The built extension should be found inside `build/libs`.
You can drag this onto QuPath to install it.
You'll be prompted to create a user directory if you don't already have one.

The minimal extension here doesn't do much, but it should at least install a new command under the 'Extensions' menu in
QuPath.

> In case your extension contains external dependencies beyond what QuPath already includes, you can create a
> [single jar file](https://imperceptiblethoughts.com/shadow/introduction/#benefits-of-shadow) that bundles these along
> with your extension by using
> ```bash
> gradlew shadowJar
> ```
> If you don't do that, you'll need to drag *all* the extra dependences onto QuPath to install them as well.
## Set up in an IDE (optional)
During development, things are likely to be much easier if you work within an IDE.
QuPath itself is developed using IntelliJ, and you can import the extension template there.
However, for development and testing, it can help to import QuPath *and* the extension and have them in your IDE side-by-side.
In IntelliJ, you can do this in a few steps:
* Get QuPath's source code, as described at https://qupath.readthedocs.io/en/0.4/docs/reference/building.html
* Store your extension code in a directory *beside* QuPath's code. So it should be located next to the `qupath` code directory.
* Import QuPath into IntelliJ as a Gradle project (you don't need to import the extension yet!)
* See https://www.jetbrains.com/help/idea/work-with-gradle-projects.html
* Within `qupath/settings.gradle` add the line `includeFlat 'your-extension-code-directory'` (updating the code directory as needed)
* Refresh the Gradle project in IntelliJ, and your extension code should appear
* Create a [Run configuration](https://www.jetbrains.com/help/idea/run-debug-configuration.html) in IntelliJ to launch QuPath. An example of how that looks is shown below:
<img src="qupath-intellij.png" alt="QuPath run configuration in IntelliJ" width="428" />
Now when you run QuPath from IntelliJ, your extension should (hopefully) be found - there's no need to add it by drag & drop.
## Customize the extension
There are a few fixed steps to customizing the extension, and then the main creative part where you add your own code.
### Update `settings.gradle`
Open `settings.gradle` and check the comment lines flagged with `\\TODO`.
These point you towards parts you may well need to change.
### Update `build.gradle`
Open `build.gradle` and follow a similar process to with `settings.gradle`, to update the bits flagged with `\\TODO`.
### Create the extension Java or Groovy file(s)
For the extension to work, you need to create at least one file that extends `qupath.lib.gui.extensions.QuPathExtension`.
There are two examples in the template, in two languages:
* **Java:** `qupath.ext.template.DemoExtension.java`.
* **Groovy:** `qupath.ext.template.DemoGroovyExtension.java`.
You can pick the one that corresponds to the language you want to use, and delete the other.
Then take your chosen file and rename it, edit it, move it to another package... basically, make it your own.
> Please **don't neglect this step!**
> If you do, there's a chance of multiple extensions being created with the same class names... and causing confusion later.
### Update the `META-INF/services` file
For QuPath to *find* the extension later, the full class name needs to be available in `resources/META-INFO/services/qupath.lib.gui.extensions.QuPathExtensions`.
So remember to edit that file to include the class name that you actually used for your extension.
### Specify your license
Add a license file to your GitHub repo so that others know what they can and can't do with your extension.
This should be compatible with QuPath's license -- see https://github.com/qupath/qupath
### Replace this readme
Don't forget to replace the contents of this readme with your own!
## Getting help
For questions about QuPath and/or creating new extensions, please use the forum at https://forum.image.sc/tag/qupath
------
## License
This is just a template, you're free to use it however you like.
You can treat the contents of *this repository only* as being under [the Unlicense](https://unlicense.org) (except for the Gradle wrapper, which has its own license included).
If you use it to create a new QuPath extension, I'd strongly encourage you to select a suitable open-source license for the extension.
Note that *QuPath itself* is available under the GPL, so you do have to abide by those terms: see https://github.com/qupath/qupath for more.
Loading

0 comments on commit 2c2e524

Please sign in to comment.