<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY>
Hi Borys,<BR>
thanks for your answer.<BR>
that might be a way I also had in mind. Otherwise in Windows environments the config is written to the registry. I would like to avoid interferring with the registry. Whereas that would be manageable with an installer, in Linux environments one needs to manipulate the config file as you mentioned. Manipulating this file with an installer would not be as easy. Otherwise, either the config file as well as the registry entries exist only when Qgis was run first. So I have to consider this as well.<BR>
Also with Linux there could be an - unlikly - issue that somone has changed the QT-config path settings, Whereas this is not to expect.<BR>
<BR>
Anyway, I believe I need a more sophisticated way, like setting a flag while Qgis loads all the plugins. Or a workaround, like activating my plugin with one of the default plugins. Manipulating the default plugins might be the ultimo ratio, because I would neither to change this plugins (in favor of avoiding instabilities) nor risk to overwrite possible changes or updates on the users machine!<BR>
<BR>
Otherwise, does anyone know whether there is a flag or a property or any way to enable/disable plugins programmatical, let's say from another plugin?<BR>
<BR>
cheers<BR>
<BR>
Stefan<BR>
<BR>
Am Montag, den 01.03.2010, 13:57 +0100 schrieb Borys Jurgiel:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Dnia poniedziałek, 1 marca 2010 o 13:24:56 Stefan Kiefer napisał(a):
> Hi,
> thanks a lot for the immediate answers. What you all say is true for
> plugins installed from a respository, resp. with the plugin-installer.
> What I need is when I put a custom plugin (one I made by myself) to the
> qgis/python/plugins-folder. Hence, if I do that the plugin can be
> activated in the pluginmanager, but is not activated by default.
> The way is that one get an installer (in this case a selfextractable
> file) and the plugin gets copied to the plugins folder. Unfortunately
> then the user is forced to search in the pluginmanager for the new
> plugin to activate it. I need to realize this more comfortable, i.e.
> without confronting the user to open the plugin installer nor the
> manager ...
Your installer can enable the plugin in Qgis settings from outside Qgis. It's
accessible from Qt via QSettings as well as directly in the file:
~/.config/QuantumGIS/QGIS.conf
on Linux and in similar path in the windows Registry.
The only thing you need to do is to go to the PythonPlugins section
and set your_plugin_module key to true.
_______________________________________________
Qgis-developer mailing list
<A HREF="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</A>
<A HREF="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>