http://imagej.273.s1.nabble.com/installing-macro-properly-tp5023470p5023494.html
I suffer with you.
*and* a macro.
design a html-doc that can help your users.
> Wayne-
>
> Thank you for testing. I will do some work on this tomorrow.
>
> My take so far is:
>
> a) putting .jar files in plugins/myStuff, with a plugins.config file puts the plugin
> in the Plugins sub menu specified in the plugins.config file (and plugins/myStuff is irrelevant)
> b) putting foo_macro.ijm files in plugins/Macros/myStuff causes the macro to appear as Plugins>myStuff (this is probably what I want
>
> Alas, I have been using subFolders under plugins to organize the plugins for my own maintenance convenience (and using plugins.config files in each .jar file to control where the plugin appears in the menu structure). Now, it appears that the folder structure within plugins/Macros actually controls the menu structure. I suppose I can live with this - but it seems wildly inconsistent.
>
> c) the example macros, showing how to affect the menu structure with "<subMenuName>" in the macro statement is "no longer operative". This is where I went wrong in reading the documentation.
>
> d) somehow, plugins/Scripts seems to be preferred for FIJI, and (I think) I should be installing foo_macro.ijm in plugins/Scripts/subMenuName. I'll try that, too.
>
> So...tomorrow will be devoted to double checking all of this and deciding how to proceed.
>
> Thanks to all who replied (especially Wayne, whose replies have been, as usual, accurate and helpful).
>
> I'm OK with telling my colleagues how to use the plugins>Install... dialogs to put things in the right place. I'm not a fan of asking them to directly manipulate the plugins directory, esp. on machines where they may not have the appropriate privileges.
>
> I'm also mildly unhappy that the end user needs to know if the item being installed is a macro or a plugin - and different techniques are needed to achieve the same effect in the displayed menu structure.
>
> On balance, I guess I would prefer that all plugins appear in the menu structure according to where they are stored under plugins (instead of using plugins.config files) - so I'm not unhappy about how ImageJ2 does this with macros - I suppose I just wish it were all more consistent.
>
> Also - if the <submenu> notation in the macro statement no longer works, I wish that the documentation SAID this more clearly.
>
> But...it is what it is...and I remain grateful for your assistance.
>
> --
> 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>