<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NO-BOK" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Agreed with Paulo.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">My impression is that new users rely on the menu to explore the software and its modules...<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Paulo van Breugel [mailto:p.vanbreugel@gmail.com]
<br>
<b>Sent:</b> 7. oktober 2016 13:35<br>
<b>To:</b> Moritz Lennert <mlennert@club.worldonline.be>; Blumentrath, Stefan <Stefan.Blumentrath@nina.no>; Vaclav Petras <wenzeslaus@gmail.com>; Anna Petrášová <kratochanna@gmail.com><br>
<b>Cc:</b> GRASS developers list <grass-dev@lists.osgeo.org>; Markus Metz <markus.metz.giswork@gmail.com><br>
<b>Subject:</b> Re: [GRASS-dev] Fwd: Re: Upcoming 7.2.0: review which addons to move to core<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span lang="EN-US" style="font-family:"Arial",sans-serif;color:black">On 7 October 2016 1:26:09 pm Moritz Lennert <</span><span style="font-family:"Arial",sans-serif;color:black"><a href="mailto:mlennert@club.worldonline.be"><span lang="EN-US">mlennert@club.worldonline.be</span></a></span><span lang="EN-US" style="font-family:"Arial",sans-serif;color:black">>
wrote:<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-family:"Arial",sans-serif;color:black">> On 07/10/16 11:35, Blumentrath, Stefan wrote:<br>
>> Ahhh, yes, there was that branch of the discussion too...<br>
>><br>
>> g.extension is great and I do not see any limit with that, esp. not<br>
>> for single user environments.<br>
>><br>
>> However, on our server I download, compile and install centrally all<br>
>> addons from source using a script. Thus, the main perceivable<br>
>> difference between core modules and addons would be visibility in the<br>
>> GUI...<br>
>><br>
>> For me personally, that is no issue. But people who start with GRASS<br>
>> likely often explore GRASS "graphically", thus a toolbox-approach<br>
>> would be very nice I think. Having an "Addons" entry in the menu (if<br>
>> there is space for that) where all installed addons register, would<br>
>> be a demonstration of existing addional functionality...<br>
><br>
> [...]<br>
><br>
> On 05/10/16 23:10, Anna Petrášová wrote:<br>
> > Hmm, this is already implemented (several years I would say). Look<br>
> > into the tab Modules in layer manager. At least we now know, that<br>
> > nobody here is using it...<br>
><br>
> Yes, I have to admit that I rarely use the other tabs in the GUI, to my <br>
> own disadvantage most probably...<br>
><br>
> But maybe we can think more radically. Just as several OS have moved <br>
> away from the classical menu paradigm to search-based access to <br>
> functionalities (e.g. gnome-shell, etc), why not completely get rid of <br>
> the menus and only leave the modules tab as entry point ?<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="color:black">That works for some but surely not all users.<o:p></o:p></span></p>
<p style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:0cm">
<span style="font-family:"Arial",sans-serif;color:black"><br>
><br>
> Again, just brainstorming...<br>
><br>
> Moritz<br>
> _______________________________________________<br>
> grass-dev mailing list<br>
> <a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/grass-dev">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><o:p></o:p></span></p>
</div>
</div>
</body>
</html>