Gets a %NULL-terminated array of strings with the authors of the plugin.
The relevant key in the plugin info file is "Authors".
Gets the copyright of the plugin.
The relevant key in the plugin info file is "Copyright".
Gets the data dir of the plugin.
The module data directory is the directory where a plugin should find its
runtime data. This is not a value read from the [structGLib.KeyFile], but
rather a value provided by the [classEngine], depending on where the plugin
file was found.
Gets the dependencies of the plugin.
The [classEngine] will always ensure that the dependencies of a plugin are
loaded when the said plugin is loaded. It means that dependencies are
loaded before the plugin, and unloaded after it. Circular dependencies of
plugins lead to undefined loading order.
The relevant key in the plugin info file is "Depends".
Gets the description of the plugin.
The description of the plugin should be a string presenting the purpose of the plugin. It will typically be presented in a plugin's about box.
The relevant key in the plugin info file is "Description".
Gets external data specified for the plugin.
External data is specified in the plugin info file prefixed with X-. For
example, if a key/value pair X-Peas=1 is specified in the key file, you
can use "Peas" for key to retrieve the value "1".
Note: that you can omit the X- prefix when retrieving the value, but not when specifying the value in the file.
The key to lookup.
Gets the help URI of the plugin.
The Help URI of a plugin will typically be presented by the plugin manager as a "Help" button linking to the URI. It can either be a HTTP URL on some website or a ghelp: URI if a Gnome help page is available for the plugin.
The relevant key in the plugin info file is "Help". Other platform-specific keys exist for platform-specific help files. Those are "Help-GNOME", "Help-Windows" and "Help-MacOS-X".
Gets the icon name of the plugin.
The icon of the plugin will be presented in the plugin manager UI. If no icon is specified, the default green puzzle icon will be used.
The relevant key in the plugin info file is "Icon".
Gets the module directory.
The module directory is the directory where the plugin file was found. This
is not a value from the [structGLib.KeyFile], but rather a value provided by the
[classEngine].
Gets the module name.
The module name will be used to find the actual plugin. The way this value will be used depends on the loader (i.e. on the language) of the plugin. This value is also used to uniquely identify a particular plugin.
The relevant key in the plugin info file is "Module".
Gets the name of the plugin.
The name of a plugin should be a nice short string to be presented in UIs.
The relevant key in the plugin info file is "Name".
Gets the version of the plugin.
The relevant key in the plugin info file is "Version".
Gets the website of the plugin.
The relevant key in the plugin info file is "Website".
Check if the plugin depends on another plugin.
The name of the plugin to check.
Check if the plugin is available.
A plugin is marked as not available when there is no loader available to
load it, or when there has been an error when trying to load it previously.
If not available then error will be set.
Check if the plugin is a builtin plugin.
A builtin plugin is a plugin which cannot be enabled or disabled by the user through a plugin manager (like PeasGtkPluginManager). Loading or unloading such plugins is the responsibility of the application alone. Most applications will usually load those plugins immediately after the initialization of the #PeasEngine.
The relevant key in the plugin info file is "Builtin".
Check if the plugin is a hidden plugin.
A hidden plugin is a plugin which cannot be seen by a user through a plugin manager (like PeasGtkPluginManager). Loading and unloading such plugins is the responsibility of the application alone or through plugins that depend on them.
The relevant key in the plugin info file is "Hidden".
Check if the plugin is loaded.
The #PeasPluginInfo structure contains only private data and should only be accessed using the provided API.