Commit 1a593ecc authored by Jean-Yves TINEVEZ's avatar Jean-Yves TINEVEZ
Browse files


parent b00b3241
# Template maven repository for Icy plugins.
![Icy logo](static/icy_imaging_software_logo-2.png)
This repository serves as a template for your future Icy plugin. If you want to create a new Icy plugin using **maven** for dependency management, just clone this repository, and edit it to your needs. The following gives hints about what to edit and how.
## What to edit.
### The `pom.xml` file.
The `pom` for Icy plugin is fairly standard. First it inherits from `pom-icy` that specifies a few default values used throughout the Icy application.
You want to edit the first section on the plugin information:
<!-- Project Information -->
The `artefactId` will be the name of the jar file produced by the compilation of the plugin. Put a sensible name for it since this is what you will have to upload to the Icy website to distribute the plugin.
Replace the following fields by values that will be informative to an end user:
<name>A template for Icy plugins.</name>
<description>This repo serves as a template for you to implement new Icy plugins.</description>
The dependency section contains only the Icy kernel (that has all the application, GUI, etc...) and the EzPlug library for now. Add more if you need it. The version of the `icy-kernel` is defined in the parent pom, so you don't have to specify it here.
<!-- List of project's dependencies -->
<!-- The core of Icy -->
<!-- The EzPlug library, simplifies writing UI for Icy plugins. -->
We need to specify where to find the dependency, so that last section has this paragraph:
<!-- Link to third-party Maven repositories -->
<name>Icy's Nexus</name>
Just keep it as is.
### Package conventions in Icy.
By convention the Java package of Icy plugins takes the following form:
package plugins.authorname.pluginname
`authorname` should be a condensed version of your name. For instance the author Alexandre Dufour uses `adufour`. Jean-Yves Tinevez uses `tinevez` _etc_.
`pluginname` should be a condensed name of the plugin you are currently developing, unique among all the plugins you develop to avoir package name clashes with the Icy application.
For instance the classes of the demo you will find in this template repository are in the package `plugins.authorname.templateplugin`.
## Examples and documentation.
There is a pdf presentation online that gives starters as how to build an Icy plugin in Java:
The two examples in this repository are inspired by it. You will find:
- A simple plugin example, that modify an image with no UI: [the first example](src/main/java/plugins/authorname/templateplugin/
- A second example plugin that uses [EzPlug]( to build a basic UI for a plugin: [the second example](src/main/java/plugins/authorname/templateplugin/
## Credits.
The example image found in the `samples` folder is courtesy of Jakub Sedzinsky, University of Copenhagen. It is an epithelium of the neural plate of _Xenopus laevis_ visualized by utrophin-GFP.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment