Re: [ jEdit-devel ] Suggestion for changing JARClassLoader and structure of Plugins

[Dirk M. <dmo...@gm...>]

> i'd be willing to do the DTD.

Thanks.

> though i'm open to suggestions, i have put a good few hours of thought
> into these files, so if you think there are issues of concern, chances
> are i may already have thought of them; so, let's dicuss.

Two remarks:

1) <plugin-dockables><dockable name="foo.dockable">
I think "name" should be "class" here, as in <option-pane>.
To keep things consistent, you could also make the main class in <plugin> an
attribute, and remove the <main-class> element.

2) It seems inconsistent, that some label texts are defined in the xml file,
while all the other texts needed by the plugin must be defined in a
properties file. This becomes even more complicated if you define multi-language
labels in the xml file (attribute "lang=..."), whereas in the property file you
have no means to.

I see no direct remedy for this. A solution could be, that properties may be
defined in the xml file, and there would be no need for separate properties
files:

<plugin>
  <properties>
    <property key="foo.key.label">
      <value>This is an parametrized {1} message text.</value>
      <value lang="de">Dies ist ein parametrisierter {1}
Meldungstext.</value>
    </property>
  </properties>
</plugin>

But this means a lot of typing for developers. Perhaps someone could write a
perl script to convert property files into this format.

Dirk.

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

GMX Tipp:

Machen Sie Ihr Hobby zu Geld bei unserem Partner 1&1!
http://profiseller.de/info/index.php3?ac=OM.PS.PS003K00596T0409a