Re: installing macro properly?

Posted by Herbie on Jun 10, 2020; 8:31pm
URL: http://imagej.273.s1.nabble.com/installing-macro-properly-tp5023470p5023480.html

Kenneth,

thanks for referring to my reply. As you may have realized, Fiji follows
  a slightly different scheme than ImageJ.

If you use "Plugins >> Install...", the installed macro is accessible
from "Plugins >> Macros" which is not what you want.

If you use "Plugins >> Install Plugin..." the installed macro is
accessible from the "Plugins"-menu but not from a submenu thereof.

That's how it is and it is up to you to propose altered source code
either to Wayne or the maintainers of Fiji. But, to be honest, is it
really such important?

Regards

Herbie

:::::::::::::::::::::::::::::::::::::::::::
Am 10.06.20 um 21:41 schrieb Kenneth Sloan:

> Wayne-
>
> Thanks for the prompt reply.
>
> I am using FIJI, and tried your suggestion to use Install instead of Install Plugin.
>
> That seemed to work as you described, but also (as I think you described), the plugin is not visible in any menu.
>
> Is this a limitation for FIJI?  If so, I suppose I can live with it, but I really did like keeping all of my plugins in a separate plugins/subFolder.
>
> Using Install... and putting foo_macro.ijm in plugins, the macro is installed, and works - but it still shows up at the bottom of the Plugins menu. So, it is accessible as:
>
> Plugins>foo_macro
>
> Is there any way to make it appear in the menu as:
>
> Plugins>subMenu>foo_macro?
>
> The macro is written (as demonstrated by the example macro) as:
>
> macro "<subMenu> foo_macro" { ... stuff ... }
>
> but the <subMenu> seems to have zero effect.
>
> Is this another difference between ImageJ and FIJI?
>
> Is there another mechanism I can use to create Plugins>subMenu and install macros so they appear there?
>
> I realize that this is largely cosmetic, but I'm trying to understand how this all works.  Both the location of the macro (in a separate plugins/subFolder) and the appearance on the menu (at Plugins>subMenu) are things I would *like* to do - but neither are critical.
>
> Recall that my standard practice in the past was to install .jar files containing both Java classes and a "plugins.config" file.  That's the only mechanism I currently understand for manipulating the appearance of the menu structure.  Is there particular piece of documentation (for either ImageJ or FIJI - but FIJI is what we are using) which explains this?
>
> Hmmm...would it work to package foo_macro.ijm and a plugins.config file in a .jar file and try to install *that*?  Would this work in FIJI, if the .jar file were in plugins>subFolder?  Is there some *other* recommended place to install macros so that access to them looks just like access to Java plugins?
>
> Of course, if push came to shove, I could just take the macro and rewrite it in Java.  Perhaps that would be easier, all around.
>  
> --
> Kenneth Sloan
> [hidden email]
> Vision is the art of seeing what is invisible to others.
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html