<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I have made some publicity before for a library which handles plugin
settings.<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://3nids.github.io/qgissettingmanager/">http://3nids.github.io/qgissettingmanager/</a><br>
<br>
Basically, the idea is that it you create once the settings
somewhere in your plugin and then it handles type validation, defaut
values, etc. The most interesting part is that you have a
SettingDialog class, which automatically read/write widgets if you
name them accordingly to the settings (it handles several widgets
for all the different types of settings).<br>
<br>
This small lib is very time saving for the few plugins I have. <br>
<br>
Maybe an idea would be to translate this to a QgsPluginSetting class
which would then list all the settings to be edited in the main
plugin setting window.<br>
<br>
Cheers,<br>
<br>
Denis<br>
<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 09/05/2013 02:47 PM, Etienne
Tourigny wrote:<br>
</div>
<blockquote
cite="mid:CA+TxYvNS6y-eiEY3BzMCePfPEZEmJFgj6Dp3ViPbRkHQ1-_LAw@mail.gmail.com"
type="cite">
<div dir="ltr">I have implemented something like this some time
ago, based on a gui from QT - Settings Editor.
<div><br>
</div>
<div>I am not sure if I never commited it or if someone removed
it.</div>
<div><br>
</div>
<div>I will try to find the code and submit a pull request.</div>
<div><br>
</div>
<div>Etienne</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Thu, Sep 5, 2013 at 5:12 AM, Victor
Olaya <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:volayaf@gmail.com" target="_blank">volayaf@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">The idea
is to have that common place for all settings. The bad thing<br>
that I see (and some people have told me), is that it might
be<br>
difficult to find for a user that searches for a
configuration panel<br>
for a given plugin, since he might look for it in the menu
of that<br>
plugin. A solution to that would be to make it easy to call
the<br>
settigns dialog, but open in the tab (or panel, or
whatever),<br>
corresponding to a given plugin. So there would be a "plugin
options"<br>
menu, with all options, but a plugin author could add a
shortcut to<br>
that and add a "setting of my plugin" menu entry which would
go<br>
straight to those settings.<br>
<br>
The thing is to avoid developers creating their own panels
and dialogs<br>
for settings, which is time consuming and each one looks
differently.<br>
<br>
I would suggest a design similar to the eclipse one, with a
tree in<br>
the left hand side where you have all plugins, and once you
select<br>
one, you see all its parameters in the right-hand side
panel.<br>
<br>
If anyone is interested, we can discuss this in the HF. It
looks to me<br>
like a nice thing to work on, and we can also adapt some
existing<br>
plugins to use it, once it is done.<br>
<br>
cheers<br>
Víctor<br>
<br>
<br>
<br>
2013/9/5 Matthias Kuhn <<a moz-do-not-send="true"
href="mailto:matthias.kuhn@gmx.ch">matthias.kuhn@gmx.ch</a>>:<br>
<div class="HOEnZb">
<div class="h5">> Hi,<br>
><br>
> Other applications have unified setting centers
like firefox when you<br>
> enter <a class="moz-txt-link-freetext" href="about:config">about:config</a> in the URL bar. But this is in
addition to the<br>
> settings dialog(s) which is/are still offered. Are
you thinking about<br>
> something like this? A simple config value editor,
like regedit?<br>
><br>
> Or is the aim of this project a unified config
dialog, where plugins<br>
> register their own tab (or list entry or
whatsoever)? In this case,<br>
> would it be a new dialog "Plugin Options" which
would act as container<br>
> for all options? Or opening up the "Options" dialog
for registering<br>
> additional tabs? IMO the first one has the drawback
of brandmarking<br>
> plugins as 3rd-party, not fully integrated, while
the second one has<br>
> the drawback/risk of cluttering this dialog.<br>
><br>
> Talking about this, I recently did a similar thing
for the vector layer<br>
> properties (add the possibility to add a new tab
for plugins. POC<br>
> implemented in form of layer specific globe
settings, not yet merged)<br>
><br>
> Cheers<br>
> Matthias<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a moz-do-not-send="true"
href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/qgis-developer"
target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</body>
</html>