[osmosis-dev] API 0.6 and unique keys
jochen at remote.org
Wed Feb 4 15:48:11 GMT 2009
On Tue, Feb 03, 2009 at 10:45:00AM +1100, Brett Henderson wrote:
> If I was writing a plugin for my own use I wouldn't bother with JPF
> initially because it's much easier to debug a plugin without it (or it seems
> that way at the moment). I'd use JPF if I was distributing plugins to end
> users though and it should be great for that purpose. I'm tempted to try
> separating out the pgsql tasks into a plugin to see how easy this really is.
Writing my own plugins the last days, I found the major complication was
that there were several things I needed from core not available (yet). I
added the isClosed and I changed some private methods into protected so
that I could subclass it. Ideally I would not have to touch the Osmosis
core when working on a plugin, but thats not the case.
If the plugins should really allow everybody to easily write plugins
without even looking into Osmosis details we have to take more care to
make sure that, for instance, there are accessor methods for everything
somebody might need, not just for the stuff that is currently needed in
Osmosis. But that is certainly doable.
For me the plugins are definitely a step in the right direction. Its
much easier now for me to experiment and keep my specialized code apart
from the core.
Jochen Topf jochen at remote.org http://www.remote.org/jochen/ +49-721-388298
More information about the osmosis-dev