<div dir="ltr"><div>Hi Richard,<br></div><span class="gmail-HOEnZb"></span><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div><div><div><div class="gmail-h5"><blockquote type="cite"><div>
<br><div class="gmail_quote"><div dir="ltr">On Fri., 13 Oct. 2017, 6:55 pm Richard Duivenvoorde, <<a href="mailto:rdmailings@duif.net" target="_blank">rdmailings@duif.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Dev's,<br>
<br>
Should/can we plan some ui discussion maybe before QGIS3 freeze?<br>
<br>
I know only discussion is not very helpfull, as it does not DO it, but I<br>
think we should use the big 3 release as a handle to cleanup/fix some ui<br>
too. As we add so much things, in my opinion you should not be afraid to<br>
also remove (non used/important) things.<br>
<br></blockquote></div></div></blockquote></div></div></div></div></div></blockquote><div> While we are at UI/UX discussion, may I recall that we created months ago an ad hoc repository (<a href="https://github.com/qgis/qgis3_UIX_discussion/issues" target="_blank">https://github.com/qgis/<wbr>qgis3_UIX_discussion/issues</a>) and that repository is full of issues waiting for pickers/opinions? And to paraphrase someone, "Freeze is coming"...<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div><div><div><div class="gmail-h5"><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Some low hanging fruit I would like to do/discuss:<br>
- move 'Plugins/Install plugin from zip' to the dialog<br></blockquote></div></div></blockquote></div></div></div></div></div></blockquote><div>Keen to see how this can integrate the Plugin manager and stays obvious for user but why not <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div><div><div><div class="gmail-h5"><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- remove overview panel (and menu actions)<br>
- remove Help toolbar (we have helpbuttons and a menu item)<br>
</blockquote></div></div></blockquote></div></div></div></div></div></blockquote><div>No strong opinion for above. I neither use them.<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div><div><div><div class="gmail-h5"><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">- move stuff (which I think clutter menu's but personally never use) to<br>
'menu groups' (like all Save Map as.. and DXF import/export (and rename<br>
those)<br></blockquote></div></div></blockquote></div></div></div></div></div></blockquote><div>Why not. What could be nice if we group buttons is to provide default shortcut for those that often use them.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div><div><div><div class="gmail-h5"><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
- merge Project New and New from Template to one 'menu group'-action<br>
<br></blockquote></div></div></blockquote></div></div></div></div></div></blockquote><div>-1 from me. New project is a normal and expected button directly under Project menu. I don't know how the group would be called but merging anyway adds another click (for a basic action).</div><div>Question: are there many people around using template project?<br></div><div><br></div><div>According to another thread/comment from you, if you are trying to customize and simplify QGIS interface, isn't it easier to deal with direct and single button from a menu than buttons within a "menu group" under a menu? There could be a risk to end up with a sub-menu with a single item. Hope that i'm clear :)<br></div><div><br></div><div>Regards,</div><div>Harrissou<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div><div><div><div class="gmail-h5"><blockquote type="cite"><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
(with menu group I mean a button/action with a little dropdown next to<br>
it, like you have for the select tools)<br>
<br>
Opinions? Anybody interested?<br>
<br>
Regards,<br>
<br>
Richard Duivenvoorde<br>
<br>
______________________________<wbr>_________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a></blockquote></div>
______________________________<wbr>_________________<br>QGIS-Developer mailing list<br><a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a></div></blockquote></div></div></div><br></div></div><br>______________________________<wbr>_________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">https://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br></blockquote></div><br></div></div>