http://imagej.273.s1.nabble.com/new-releases-LSMToolbox-4-0d-and-LSM-Reader-4-0d-tp3696349p3696352.html
entries. Drop LSM_Toolbox.jar into the plugins/Input-Output folder and
LSM Toolbox" commands in the Plugins>Input-Output submenu. Drop it
as before. In addition, single plugins distributed as ZIP archives
> Hi Gabriel,
>
> Anyway, what I do is that instead of having in the plugins.config :
>> Plugins>LSM Toolbox, "Show LSMToolbox", LSM_Toolbox("")
>>
>> I put:
>> Plugins, "Show LSMToolbox", LSM_Toolbox("")
>>
>
> As a packager of plugins, I would not want to make such a change
> because
> most naive users will just drop the file into the plugins folder
> directly
> and get a large number of new entries in the base Plugins menu. And
> inevitably someone will complain "why don't you group them in a
> subfolder"?
> :-)
>
> But at the ImageJ level, there are a couple of changes that could
> solve the
> issue:
>
> 1) If a JAR file is in the root plugins folder, and has a
> plugins.config
> specifies a submenu name, that submenu name is used as before. But if
> a JAR
> file is in a subfolder of the plugins folder, the plugins.config's
> submenu
> name (if any) is ignored and instead the name of the subfolder is
> used. That
> way, for example, users who drop LSM_Toolbox.jar into plugins directly
> get
> the plugin entries in the "LSM Toolbox" submenu, but dropping into
> plugins/Input-Output makes the plugin entries appear in the
> "Input-Output"
> submenu instead.
>
> 2) Another option would be to "page" the Plugins list. For every
> (e.g.) 50
> menu entries, a "more plugins" submenu could be added. If you had a
> ridiculous number of plugins this scheme could get very clunky -- to
> get the
> 210th plugin entry would require navigating through three "more
> plugins"
> entries first -- but it would prevent plugins from becoming
> inaccessible.
>
> Both of these schemes have the advantage that no changes are needed in
> any
> of the existing plugins' JAR bundles. I prefer option #1 -- the only
> downside is that the subfolders are currently being used to
> conceptually
> organize certain plugins (e.g., "Input-Output/QuickTime_Plugins.jar")
> that
> do not (and presumably should not) appear in that subfolder.
>
> -Curtis
>
> On Thu, May 1, 2008 at 3:49 AM, Gabriel Landini <
[hidden email]>
> wrote:
>
>> On Tuesday 29 April 2008 08:53:01 Patrick Pirrotte wrote:
>>> New releases of the LSM_Toolbox and LSM_Reader are available.
>>
>> That is a very nice. Many thanks for keep updating these.
>>
>> I have a somehow unrelated comment and not a really a criticism to
>> the LSM
>> Toolbox, but some suggestion/question about the plugins.config files
>> in
>> the
>> jars.
>>
>> I am getting a too crowded Plugins entry list and in linux, for some
>> reason
>> the submenus cannot be scrolled, while in the macs and win they can.
>>
>> One hasn't got many options:
>> * Have less plugins :-) (not really)
>>
>> * Have another level of submenus (I mentioned it to Wayne some time
>> ago,
>> but I
>> can't remember why this was not a good idea)
>>
>> * Regroup them in a smaller number of categories (what I am doing).
>> However
>> many plugins packed in jars have already a coded entry in the
>> plugins.config
>> file of the jar.
>>
>> Of course this can be edited and I have resorted to do this with some
>> jars I
>> want to keep installed without adding new entries. However, when a
>> plugin
>> is
>> updated one has to go back and edit the config file again and it
>> becomes a
>> bit tedious.
>>
>> I would like to suggest *not* adding a new entries, but suggest them
>> while
>> keeping those empty, so users can create these by adding a new folder
>> where
>> the jars can be dropped. If one drops these in an already existing
>> folder,
>> the entries would appear there.
>>
>> Ideally we could agree some categories following those in Wayne's
>> site. I
>> think it is not very useful to have a new entry which expands to just
>> a
>> further branch or 1 or 2.
>> For those interested, I read the other day that on average that the
>> theoretical minimum number of choices can be achieved using a ternary
>> tree,
>> but this is not the problem here, it is just a too large list of root
>> categories with few branches after it.
>>
>> Anyway, what I do is that instead of having in the plugins.config :
>> Plugins>LSM Toolbox, "Show LSMToolbox", LSM_Toolbox("")
>>
>> I put:
>> Plugins, "Show LSMToolbox", LSM_Toolbox("")
>>
>> Now the jar file can be dropped anywhere. If one wants to create a
>> custom
>> Plugins hierarchy, this can be don by using folder names where the
>> jars
>> are
>> put.
>>
>> Regards,
>>
>> Gabriel
>>
>