Fiji is a community effort. So we are happy whenever we see new people developing Fiji!
The purpose of this tutorial is to get you started hacking on Fiji’s source code (i.e., the core Fiji plugins). If you need to develop a new plugin for ImageJ, you do not actually need Fiji’s source. Rather, see these resources:
- example-legacy-plugin project template
- Introduction into Developing Plugins tutorial
- Developing ImageJ 1.x plugins with NetBeans screencast
See also Developing Fiji in Eclipse for a tutorial specific to the Eclipse IDE.
Fiji is organized into a set of Maven projects. For convenience and speed, there is SciJava’s minimal Maven-lookalike MiniMaven to build Fiji, but it is recommended to use an Integrated Development Environment, or at least real Maven.
It is strongly recommended to write regression tests (also known as unit tests). It is easy.
At some point, you might want to debug whatever you wrote. There’s a small Debugging intro page.
When you want to propose and/or discuss changes to some source code, the preferred way is to submit a PR on GitHub.
Please have a look at the excellent How to contribute to an existing plugin or library tutorial.
A plugin wants to be used. Therefore you want to give users some information about it, and most likely also a tutorial how to use it.
If you have an account on this Wiki, you can easily create new tutorials with the Tutorial Maker.
Further reading for developers
- Overview of Fiji’s source code
- Description of ImageJ’s plugin architecture
- Tips for developers
- ImageJ1 Javadoc ZIP (for offline usage)
- ImageJ2 Javadoc ZIP (for offline usage)
- Developers HowTo
- ImageJ plugin writing tutorial
- ImageJ programming tutorials
- Uploading plugins
- Developing Fiji in Eclipse
- Project ideas
- Introduction to debugging
- Profiling Java Code
- Tips for C++ developers