I’ve been trying to get a plugin in tool to work. I copied one of the plugin tools from the imagej-plugins-tools source code and did some modifications, added a new icon, changed the names, added a main section to run imageJ2. The tool loads onto the toolbar, but some of the functionality is broken for all of the tools. For example, you can’t get the configure dialog box to appear. The code also seems to run very slow. I then tried to add the plug-in to a downloaded copy of imageJ2 and it does work. It shows up as being added when I get the system information and scroll through the plugins. On top of that, NONE of the plugins in imageJ2 are actually imageJ2 plugins. They all seem to be imageJ1 plugins.
I wanted to develop the plugin (and even tackle dealing with immature overlays) because the full scope of the project needs to handle adding specialized file I/O. It needs to be a tool because we want to display statistics for the region of pixels that is under the cursor. But now I’m thinking this is too bleeding edge.
Any suggestions what I need to do to get the plugin tool to work with a downloaded copy? or do I have to build a “pure” imageJ2.
I have now tried to get an imageJ1 style of plugin to run (the overlay brush is a good starting point for what I want). I can compile and run the plugin in eclipse if I force the plugin to run by adding a main method and having the method call the plugin. But I can’t seem to get it to install in imageJ2. I then thought I would just compile and run it from imageJ2. But that gives me the dreaded AWT version 52 found and needs version 50 (java 1.6 vs. java 1.8)…which doesn’t seem to be an easy fix. At least not easy enough to distribute the plugin to engineers to use.
Any suggestions on how to get a plugin tool to work would be greatly appreciated