On Fri, Jun 03, 2005 at 10:17:55AM +0200, Dave Neary wrote:
> Manish Singh a ?crit :
> >There are also persistent parasites that can be attached to the app.
> >This is how the png plugin stores its default settings currently. They
> >are backed by <gimpdir>/parasiterc.
> Jay pointed this out too. Thanks for the info.
> >>The main point to bear in mind is that this should be trivial for a
> >>plug-in author.
> >The most convenient way would be to handle it transparently, but I can't
> >think of a way that doesn't involve larger infastructure changes.
> It's a 3 month project, infrastructure changes are possible :)
Well, my thinking was a GimpPlugIn class, which a plugin derives from.
The class implements the basic GUI itself, and UI elements are tied
directly to PDB arguments. This sort of API shakeup is probably
something that should happen along with GEGL integration, and would
require a fair amount of discussion to nail the details down. So I
dunno if that sort of job falls in the scope of the Google thing.
> >The hard part is a simple API that handles portable data serialization.
> We have that, don't we? At least, that was my understanding of the
> gimprc objects.
IIRC, gimpconfig needs an object that implements the GimpConfig
interface, so it's not exactly *simple*.
Gimp-developer mailing list