<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=181177" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/codebrainz">@codebrainz</a> you forgot the <code></rant></code> :)  But basically took the words out of my mouth. <g-emoji class="g-emoji" alias="-1" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f44e.png">👎</g-emoji></p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=652673" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/arigit">@arigit</a> Adding an extra action to get the menus every operation does not improve usability.  The point of a menu interface is to make it easier to use than apps like vim or emacs that are totally keyboard driven (or were, they both now have menus IIUC :) Whilst Geany is not specifically targetted at "my first IDE" its also not targeted at leet developers only, its a happy middle ground.</p>
<p>Of course GUIs are very personal things, and what is the best GUI for a particular app varies, but Geany has attracted contributors who seem to appreciate the effectiveness of a traditional GUI in this use-case.  So I suspect you won't get much support for a GUI "refresh" without providing significant real world data that demonstrates an improvement in effectiveness.  Simply "its new" won't cut it.  And also being tied to a specific platform and desktop isn't acceptable either.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/issues/2061#issuecomment-455828912">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ3OHilMeQX5ZR_DDqDZROuywtM8Kks5vE8MngaJpZM4aJS2w">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJ7ixqS9hI_GxmlaVIxwDxVTQjf0Hks5vE8MngaJpZM4aJS2w.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #2061: @codebrainz you forgot the `\u003c/rant\u003e` :)  But basically took the words out of my mouth. :-1:\r\n\r\n@arigit Adding an extra action to get the menus every operation does not improve usability.  The point of a menu interface is to make it easier to use than apps like vim or emacs that are totally keyboard driven (or were, they both now have menus IIUC :) Whilst Geany is not specifically targetted at \"my first IDE\" its also not targeted at leet developers only, its a happy middle ground.\r\n\r\nOf course GUIs are very personal things, and what is the best GUI for a particular app varies, but Geany has attracted contributors who seem to appreciate the effectiveness of a traditional GUI in this use-case.  So I suspect you won't get much support for a GUI \"refresh\" without providing significant real world data that demonstrates an improvement in effectiveness.  Simply \"its new\" won't cut it.  And also being tied to a specific platform and desktop isn't acceptable either."}],"action":{"name":"View Issue","url":"https://github.com/geany/geany/issues/2061#issuecomment-455828912"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/issues/2061#issuecomment-455828912",
"url": "https://github.com/geany/geany/issues/2061#issuecomment-455828912",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>