<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="12" style="border: 1px #c9c399 solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://git.reviewboard.kde.org/r/128726/">https://git.reviewboard.kde.org/r/128726/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On August 21st, 2016, 9:08 a.m. CEST, <b>Martin Gräßlin</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">As the maintainer of both klipper and kglobalaccel I'm strictly against ading this shortcut by default! This was already stated by me in the bug report by setting it to wontfix.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">At the moment this would result in a hidden default shortcut no user knows about. This is bad, we should not add unexepected and unknown shortcuts. And we should not needlessly steal shortcuts from applications. In doubt don't set a shortcut by default. At the current time this would only result in a degrated user experience: either an in-application shortcut, which we don't know that it existed, started to break, or the user presses the shortcut and gets hit by surprise what happens. It's totally unexpected behavior to open this menu.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Before we start to add new shortcuts, we need to rethink and implement better ways of global shortcut handling:
1. educating users about shortcuts
2. ensuring that we don't steal shortcuts (e.g. by setting up a policy about which modifier belongs to the DE)</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">As long as these problems are not solved, I'm strictly against adding shortcuts for hidden functionality. No matter how much we personally think they are sensible.</p></pre>
</blockquote>
<p>On August 21st, 2016, 10:03 a.m. CEST, <b>Andreas Kainz</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">In General you are right and we work on aa shortcut strategy, but it need time and in the end everybody will say. Dont Change my shortcut workflow.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Why There are two global shortcuts available in klipper. Arent They hidden functionality?</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">What Is your user scenario for klipper?</p></pre>
</blockquote>
<p>On August 21st, 2016, 8:52 p.m. CEST, <b>Martin Gräßlin</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><blockquote style="text-rendering: inherit;padding: 0 0 0 1em;border-left: 1px solid #bbb;white-space: normal;margin: 0 0 0 0.5em;line-height: inherit;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Why There are two global shortcuts available in klipper</p>
</blockquote>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">No idea. Legacy. Probably should be removed.</p>
<blockquote style="text-rendering: inherit;padding: 0 0 0 1em;border-left: 1px solid #bbb;white-space: normal;margin: 0 0 0 0.5em;line-height: inherit;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Arent They hidden functionality?</p>
</blockquote>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Yes they are. But they still are if we expose the shortcut and nobody knows about it.</p>
<blockquote style="text-rendering: inherit;padding: 0 0 0 1em;border-left: 1px solid #bbb;white-space: normal;margin: 0 0 0 0.5em;line-height: inherit;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">What Is your user scenario for klipper?</p>
</blockquote>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">If I'm totally honest I would love to kill most functionality of klipper. Because it's unmaintained and as you say hidden functionality. I don't know why there are things like the "Invoke action". Also the menu is something I'm not totally happy with as it requires a completely differnt code path. If I'm totally honest I don't want these features to be exposed to more users as I don't think they are in a good shape and we don't have developers working on klipper (haven't had for years, I only took over maintainership because it needs significant adjustment for Wayland).</p></pre>
</blockquote>
<p>On August 21st, 2016, 9:27 p.m. CEST, <b>Andreas Kainz</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Its aAA default widget and it is aa usefull one in my workflow, but with the new shortcut it would improve the widget to a great feature. aa</p></pre>
</blockquote>
<p>On August 21st, 2016, 10:30 p.m. CEST, <b>Thomas Pfeiffer</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Klipper does have very corner-case features which I suppose could be removed without much of a loss for most users ("invoke action" definitely being among them). Klipper is a KDE-typical case of just adding features because they're possible, without any product vision.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Invoking Klipper at cursor position, on the other hand, is a useful feature, which can in fact make users more productive if they know about it.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">The shortcuts overlay is in the plans and will certainly happen, and it could expose that shortcut.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">As for the actual shortcut: It should be with Meta, following a scheme we want to establish where global shortcuts should by default be with meta in order not to conflict with any applicaiton shortcuts.</p></pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><blockquote style="text-rendering: inherit;padding: 0 0 0 1em;border-left: 1px solid #bbb;white-space: normal;margin: 0 0 0 0.5em;line-height: inherit;">
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">but with the new shortcut it would improve the widget to a great feature</p>
</blockquote>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Only if the shortcut is known to the user. Which it currently isn't. This turns the whole thing pointless.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Let's first improve the infrastructure, then start adding new shortcuts. Also we need to evaluate very carefully which features to expose with a default shortcut. Every shortcut we have is a risk of breaking applications.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">If having the clipboard history open at the cursor position is an important feature, then we need to think about the best way to expose it. I'm not sure whether having a global shortcut by default improves this is any way. In fact I know about it and even have a global shortcut set, but I don't use it at all.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">I'm sure that there are better ways to include a clipboard history. It might need more code, but let's think at a good global experience and not just at the global shortcut. This must be possible with the existing interaction pattern using ctrl+v or right click.</p></pre>
<br />
<p>- Martin</p>
<br />
<p>On August 21st, 2016, 2:47 a.m. CEST, Andreas Kainz wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="12" style="border: 1px #888a85 solid; border-radius: 6px; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tr>
<td>
<div>Review request for Plasma and KDE Usability.</div>
<div>By Andreas Kainz.</div>
<p style="color: grey;"><i>Updated Aug. 21, 2016, 2:47 a.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
plasma-workspace
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">add a default shortcut for open clipboard at mouse point (ctrl+alt+c)</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">BUG 366690</p></pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>klipper/klipper.cpp <span style="color: grey">(525ef87)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/128726/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>