<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/122522/">https://git.reviewboard.kde.org/r/122522/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On February 11th, 2015, 5:14 p.m. CET, <b>Andrew Lake</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;">It might be worth investigating the use-case a bit further to try to understand if this is the best way to solve this. Is it useful? Yes. But there are potentiall negative impacts that should be balanced against the relative increase in utility.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">We also need to belly up to identifying primary and secondary target personas and scenarios for Plasma (maybe a thing for the upcomign sprint). At best, I'd suggest that exposing the host name here would target a secondary persona and any associated scenarios. </p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">While I can't argue that the scenario in the bug report isn't legitimate, I'm not sure it warrants adding information to the lock-screen that is of little-to-no value to primary target personas and scenarios. The cost we're trying to mitigate in the bug report is that the user logs in/unlocks to identify the computer versus knowing it one interaction step earlier. </p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">For the lab/shared computers, the scenario requires that more than one computer is shared (probably in relative proximity to each other) and some particular need that requires knowing the computer identity <em style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: normal;">before</em> logging in/unlocking. Even in corporate environments that seems like quite a marginal scenario.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">So for me, I'm struggling to see how the potentially negative impact of added information noise for what I think are the primary target personas and scenarios balances what is, I think, a marginal increase in utility for a marginal scenario for a secondary target persona.</p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Hope this helps!</p></pre>
</blockquote>
<p>On February 11th, 2015, 6:26 p.m. CET, <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;">Thanks for your feedback. I'm wondering whether we could make the information easily available without adding noise in general. I really think it's worth to invest the effort to provide this data as it's important in the situations when it's needed (e.g. labs).</p></pre>
</blockquote>
<p>On February 11th, 2015, 6:31 p.m. CET, <b>Aleix Pol Gonzalez</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;">Would it be possible to use something like Kiosk to decide what information to show?
Such deployments usually mingle with Kiosk.</p></pre>
</blockquote>
<p>On February 11th, 2015, 6:35 p.m. CET, <b>Marco Martin</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;">yeah, didn't chime in on this one so far but i agree with Andrew
could be enabled as aleix says with kiosk (that would mean pretty much an hidden config option, which poses the problem that will make it bitrot.
or could be just supposed for deployers to customize the look and feel package.. will ask them to maintain qml code that's a bit nasty as well</p></pre>
</blockquote>
<p>On February 13th, 2015, 8:33 a.m. CET, <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;">An idea: Kickoff alternates the User Name and host information. Could that be a solution?</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;"><p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Personally I'd find it a bit strange there, especially if your hostname is not clear hostname (eg. my computer has hostname "martin" and my wife is using it), then the alternation could look like random login/unlock. </p>
<p style="padding: 0;text-rendering: inherit;margin: 0;line-height: inherit;white-space: inherit;">Just my opinion :)</p></pre>
<br />
<p>- Martin</p>
<br />
<p>On February 11th, 2015, 2:59 p.m. CET, Martin Gräßlin 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 Andrew Lake.</div>
<div>By Martin Gräßlin.</div>
<p style="color: grey;"><i>Updated Feb. 11, 2015, 2:59 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Bugs: </b>
<a href="https://bugs.kde.org/show_bug.cgi?id=294778">294778</a>
</div>
<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;">FEATURE: 294778
FIXED-IN: 5.3.0</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>lookandfeel/contents/components/InfoPane.qml <span style="color: grey">(18739ad96724f520ce8467ba5d4c9595e8a9e9ed)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/122522/diff/" style="margin-left: 3em;">View Diff</a></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">File Attachments </h1>
<li><a href="https://git.reviewboard.kde.org/media/uploaded/files/2015/02/11/771f0a24-aaa1-4bc4-afe8-53c44fe68d71__snapshot_TJ8703.png">Screenshot of LockScreen with new info</a></li>
</ul>
</td>
</tr>
</table>
</div>
</body>
</html>