Hi all, <br><br><div class="gmail_quote">On Wed, Aug 18, 2010 at 10:05 PM, Martin Dobias <span dir="ltr"><<a href="http://wonder.sk">wonder.sk</a>@<a href="http://gmail.com">gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Borys<br>
<div class="im"><br>
On Sun, Aug 15, 2010 at 11:59 AM, Borys Jurgiel <<a href="mailto:borysiasty@aster.pl">borysiasty@aster.pl</a>> wrote:<br>
> My suggestion for now is to put everything to a PostGIS submenu within the<br>
> Plugins menu:<br>
><br>
> self.iface.addPluginToMenu('PostGIS', actionBlahBlah)<br>
<br>
</div>Right. I will do that for postgis manager in the next release. </blockquote><div> </div><div>I moved all my 2 PostGis plugins (rt_sql-layer e rt_postgres-extractor) <br>to the PostGIS menu:<br><br>self.iface.addPluginToMenu('&PostGIS', self.action)<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
> Then we can modify the QgsInterface.addPluginToMenu method to put each<br>
> submenu either to the Plugins branch or to the main menu, so each user can<br>
> configure which plugin sumbenus are at hand. It's a five-minuts-fix to read<br>
> it from QSettings (still without any GUI for configuring it, but it's a step<br>
> forward).<br>
><br>
> The third step is the GUI. I started refactoring the Installer (just three<br>
> hours per month, so it's why no changes are commited) and with Martin and<br>
> Anne we plan to put it as a second tab of the manager. What about a third<br>
> tab "menus and toolbars", when an user can be able to:<br>
><br>
> 1. Select whether given submenu (e.g. PostGIS) goes to the main menu or the<br>
> Plugins menu<br>
><br>
> 2. Select whether given submenu creates its own toolbar or goes to the main<br>
> Plugin toolbar.<br>
><br>
> 3. Compose own toolbar(s) with a set of individual plugin buttons. It allows<br>
> to hide the native plugin toolbar and enable personalized ones, like<br>
> "Monday's tasks", "Tools useful for X-files processing etc"<br>
><br>
> 4. Save/load profiles (at least sets of plugins to be loaded - now I often<br>
> have to use --noplugins option to make qgis faster)<br>
><br>
> What do you think? The first two steps can be done in a moment.<br>
<br>
</div>I like this idea of giving the users a chance to override the default<br>
placement. I would like to go even further - to allow user to<br>
manipulate individual actions created by the plugins - but that would<br>
probably need an addition to interface API (otherwise the<br>
identification of actions would depend on their name in current<br>
translation). I think of showing a tree widget to the user where nodes<br>
would be menus and submenus, the leafs would be individual actions.<br>
The user would be able to modify the tree in any way he likes: add new<br>
top level menus with some actions or just reorganize the 'Plugins'<br>
menu.<br>
<br>
If we end up updating the plugin interface, we could also proceed with<br>
defining the categories as we have discussed at the hackfests. Each<br>
plugin would be _strongly_ advised to suggest a category where it<br>
belongs, so ideally the users will not have to organize the plugins<br>
manually.<br clear="all"></blockquote><div>+1, would be great!<br><br>Cheers<br></div></div><br>-- <br>Giuseppe Sucameli<br>