Hi, there.
I've recently taking a look at PproxyToadlet because of issue 1823 and
while I'm fixing that I'd also remodel the plugin loading code and
interface. The current syntax of the single line labelled "Load plugin:"
is more than just a little bit confusing (and sparsely documented).
Here's what I think: We should split the "Load Plugin" section into two
parts: one for loading "official" plugins and one for loading other
plugins from arbitrary remote sources.
The first part would only require a name and a checkbox for auto-refresh
from the server on startup.
The second part would require a complete URL (and maybe the same
checkbox? If we allow users to load plugins from remote sources we can
also allow them to refresh that remote source on startup).
The name of the real plugin class is always taken from the JAR Manifest;
this is something that authors of remote plugins (are there any yet?)
and our build scripts for the "official plugins" need to take care of.
That would significantly improve the interface and encourage more users
to try out plugins. The first section could also include a current list
of "official" plugins so that users know about a couple of plugins they
could try.
Any further suggestions or comments?
David
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20071027/b5519bab/attachment.pgp>
