Re: new releases: LSMToolbox 4.0d and LSM_Reader 4.0d

Posted by Gabriel Landini on May 01, 2008; 8:49am
URL: http://imagej.273.s1.nabble.com/new-releases-LSMToolbox-4-0d-and-LSM-Reader-4-0d-tp3696349p3696350.html

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