[josm-dev] Refactoring of the JOSM architecture vs. Plugins

[Dirk Stöcker]

On Mon, 18 Aug 2008, J.H. wrote:

> This boils down to the following approach:
> - Assess which plugins are considered critical.

Already done. These are the ones we update frequently.

> - Make the source code of critical plugins available in the SVN
> repository if not already there.

Contacting the plugin authors, getting and preparing the sources would be 
a good job. Send me the stuff and I check it into SVN. This would also 
result in translations of these plugins.

> - Identify plugins which might just as well be moved into the JOSM code
> base (I'm sure there's plenty of code which doesn't have to be a plugin).

Unglue is the only candidate ATM.

> - Make sure that all plugins in the repository actually compile. Move
> them into an attic area if they don't.

The build.xml divides the stuff into "compilable" and "wont compile, but 
nobody cares" :-)

> - Make it easy for refactorers to run a workspace with all the
> (critical) plugins checked out.

Already possible.

> - By the way of refactoring, clean up the code design, and create
> well-defined APIs as we go along.

It is not so easy to get well-defined API's, but I would give it a try.

> - Publish API change notes to give third-party plugin developers a
> chance of keeping up.

Nah. Everything in SVN is cared for, everything else not.

Ciao
-- 
http://www.dstoecker.eu/ (PGP key available)