<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body smarttemplateinserted="true" bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 05-10-16 16:50, Sören Gebbert wrote:<br>
</div>
<blockquote
cite="mid:CAPHDReLg9XzXz66dt4Jdvii8=D+q=U-ibAbWjA+cynBuwfh--w@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-10-05 16:46 GMT+02:00 Moritz
Lennert <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mlennert@club.worldonline.be"
target="_blank">mlennert@club.worldonline.be</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On 05/10/16 16:29, Paulo van Breugel wrote:<br>
</span>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
<br>
On <a moz-do-not-send="true" href="tel:05-10-16%2015"
value="+495101615" target="_blank">05-10-16 15</a>:20,
Moritz Lennert wrote:<br>
</span><span class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe we should ask the users of whether this
distinction between<br>
modules and core and extensions is really relevant
for them, or<br>
whether most are perfectly happy to just install
extensions.<br>
</blockquote>
<br>
Since you are asking :-) , as an user, my main
interest is in good<br>
documentation and reproducible examples (which I can
than also use to<br>
see if outputs make sense to me as an user). In that
respect there is no<br>
inherent difference between core modules and
extensions. What is<br>
different is that many (most?) of the core functions
are accessible<br>
through the menu. I personally don't find that very
important,<br>
especially with the modules tab giving fairly easy
access to extensions,<br>
but I can imagine that for new / other users,
especially those more<br>
inclined to menu-driven applications, this may make a
difference.<br>
<br>
</span></blockquote>
<br>
Thank you, Paulo, for this feedback.<br>
<br>
This means that finding a means to more easily integrate
addon modules into menus might be a task to keep in mind.<br>
<br>
Maybe the startup script could check the .grass7/addons
directory and automatically create an 'addons' menu using
[1] ? Maybe the mecanism can be changed in a way to just
allow to create toolboxes and that these are automatically
integrated into the main menu ?<br>
<br>
Just brainstorming, here...<br>
</blockquote>
<div><br>
</div>
<div>How about g.extension will create a menu entry based on
the modules keywords when it installs the module? And it
will remove the entry when the module gets removed?</div>
</div>
</div>
</div>
</blockquote>
<br>
These sound like interesting options. I don't have a very good idea
what would be the best approach, but I would caution against full
freedom for the module to install itself in any location in the
menu. I am having in mind how some QGIS addons create menu items,
including in the top-level menu, resulting in what for me is a more
chaotic bloated environment. In that sense, perhaps there could even
be an option at installation to prevent the module from creating a
menu item. <br>
<br>
<br>
<blockquote
cite="mid:CAPHDReLg9XzXz66dt4Jdvii8=D+q=U-ibAbWjA+cynBuwfh--w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Best regards</div>
<div>Soeren</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Moritz<br>
<br>
<br>
[1] <a moz-do-not-send="true"
href="https://grass.osgeo.org/grass70/manuals/wxGUI.toolboxes.html"
rel="noreferrer" target="_blank">https://grass.osgeo.org/grass7<wbr>0/manuals/wxGUI.toolboxes.html</a>
<div class="HOEnZb">
<div class="h5"><br>
______________________________<wbr>_________________<br>
grass-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:grass-dev@lists.osgeo.org"
target="_blank">grass-dev@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/grass-dev"
rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman<wbr>/listinfo/grass-dev</a></div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>