Plugin interface: Information and Version

Jasper Huijsmans jasper at moongroup.com
Tue Nov 25 12:06:16 CET 2003


Op ma 24-11-2003, om 23:09 schreef Benedikt Meurer:
> >>I'd say this method would encourage inconsistency between plugins. I'd suggest a
> >>minimal list of mandatory information (name, version number, etc) plus a buffer
> >>for flexibility.
> > 
> > Amazing, I was just going to write exactly the same thing ;-)
> > 
> > I like the list Bernhard used, so I was thinking:
> > 
> > Name
> > Version
> > Author(s)
> > Website
> > 
> > Description
> > 
> > All of which will be left out when they are NULL. I'm not sure about
> > 'Author(s)' -- that might get complicated. 'Maintainer' perhaps would be
> > better or 'Contact' with an email address?
> > 
> > What do you think?
> 
> I like the idea, but for further additions we should forsee some kind of 
> function or buffer table with a flags field indicating what kind of 
> stuff the plugin is capable to provide, so we do not need to break the 
> api as often :-)
> 

I wanted to use a struct, allowing all members to be NULL. New info can
simply be added at the end without breaking old apps:

typedef struct
{
  char *name;
  char *version;
  char *maintainer;
  char *website;
  char *description; 
}
XfcePluginInfo;

void (*fill_plugin_info)(XfcePluginInfo *info);

That should be good enough to last a while, I think.

	Jasper





More information about the Xfce4-dev mailing list