Am 27.11.2010 18:04, schrieb Frederik Ramm:
Sure, every solution has it's drawbacks. But what's the users
interest? To know which menu item is caused by which plugin, or to
intuitively find a functionality where a user expects it.
If you have just asked for something on the list, and people have told
you "install the XYZ plugin, then you can do what you want", I think it
would not be too much to ask from the user to go to the "Plugins/XYZ"
menu. Indeed this provides a clear visual clue that the XYZ plugin is
indeed installed and active.
If the plugin doesn't have/need a menu entry, this logic fails :-)
I don't think the real user interest is to make sure that a specific
pugin is installed. I think the user simply wants to use the function in
question.
If most plugin functions would be like firebug in firefox that are
completely different from other functionality a plugin menu might make
sense. But in JOSM, most plugin functions don't differ very much from
existing functions, so it makes perfect sense to place it where other
such functions exist.
Regards, ULFL
_______________________________________________
josm-dev mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/josm-dev
