<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/106768/">http://git.reviewboard.kde.org/r/106768/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On October 8th, 2012, 5:31 p.m., <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;">just an idea: what about hiding the whole X screen saver stuff behind another configure dialog. Looking at the screenshot I find the design puts emphasis on the wrong part: what we want to remove takes more than 50 % of the available screen estate.</pre>
</blockquote>
<p>On October 8th, 2012, 5:50 p.m., <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;">another idea would be just show the screen saver part only when the screensaver radio is selected (i kept it a bit that way before merging btw, seemed a bit flashy..)</pre>
</blockquote>
<p>On October 8th, 2012, 5:50 p.m., <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;">I agree. On the other hand, showing new dialogs it's considered bad practice. :/
Maybe we can show the xscreensaver part when it's enabled?
**Aleix turns the agateau-sign on** (see bat-signal for further reference)</pre>
</blockquote>
<p>On October 8th, 2012, 8:40 p.m., <b>Aurélien Gâteau</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;">Played a bit with the .ui file and came up with this: http://simplest-image-hosting.net/png-0-plasma-windowedk16149 . Not sure it is possible, depends on how "previewable" the "simple locker" and "desktop widgets" lockers are. I can provide the .ui file if you want but I butchered it, I doubt it would compile.</pre>
</blockquote>
<p>On October 8th, 2012, 10:21 p.m., <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;">It kind of makes sense to share the preview, but it seems it's not that easy to preview the plasma-overlay.
Anybody knows how hard would be to invoke it in hte preview thingie?</pre>
</blockquote>
<p>On October 9th, 2012, 8:55 a.m., <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;">I really like Aurélien's attempt! Here is some detailed feedback:
- Putting the screensaver selection in a combo box makes sense to make it less prominent. Question here: Is it possible to update the preview while the user navigates through the combo box item list with the keyboard (without closing it)? Usually when people select a screensaver, they want to browse through the available savers before settling on one and that would become tedious if they had to open the box again for each saver.
- I'd rename "Setup..." to "Configure..." as this is the word we normally use for this. Setup sounds more like "First-time configuration routine" to me, like something really complex.
- The spin boxes for the timings seem to narrow to hold unit indicators to me, but I suppose this would change in the final implementation</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;">We can do a lot better than this.
Note the complete lack of visual alignment, the mix of widget placement strategies (left, right; vertical, horizontal) .. meh.
So .. let's step back and reconsider our assumptions.
Is this something a person configures *often*? No. So does it need to be hyper optimized for speed usage? No.
How much granularity do we need to offer in the UI for things like how long to wait until a password is required? Not much.
This should lead us to conclusions such as:
A spinner is not needed for "Require password after:". A drop down with a few sensible entries should be enough: Never, Immediately, After 1 minute, After 2 Minutes, After 5 minutes ... is anything more really necessary? This also lets us get rid of the checkbox and shorten the text to "Require a password:"
Note that "require a password" is an anachronism in our newfound QML world -> the Plasma Active locker does not require a password at all. In that light, perhaps this should not even be exposed in the UI at all. If the user intentionally locks the desktop -> it locks hard instantly. If it is an automatic trigger, only require a password after 30s or some sensible timeout. Voila, one more option evaporates and we no longer have a conflict with the QML themes.
the spinner after "Start automatically" should have units in it (minutes) and 0 should be "Never"; drop the checkbox.
"Locker type" => what does that even mean? It's jargon. "Lock style:" might be more descriptive and understandable?
"Simple locker" is meaningless. What is "Simple"? Compared to what? Perhaps "Password entry" or some other phrase that speaks to the user-perceptible function.
The radio buttons also fail in a significant way: we can now have lockers in QML .. which means we can (and will) have multiple options here.
So a drop down next to the label "Lock style:" listing the various installed options.
I'm not sure why "Desktop widgets" is orthogonal here either. They are also somewhat broken in the current QML locker; personally, I think how they are managed needs some rethink. Is fully customized placement of widgets the easiest / most sensible thing? Or would some auto-alignment with simplified access to configuration of the widgets in question be more sensible?
Finally, get rid of both the group boxes in the design; they are visual noise and increase the number of alignments in the dialog.
Would be fantastic if we could get rid of "Test" and "Setup" somehow as well...
</pre>
<br />
<p>- Aaron J.</p>
<br />
<p>On October 8th, 2012, 3:43 p.m., Aleix Pol Gonzalez wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/media/rb/images/review_request_box_top_bg.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for Plasma and KDE Usability.</div>
<div>By Aleix Pol Gonzalez.</div>
<p style="color: grey;"><i>Updated Oct. 8, 2012, 3:43 p.m.</i></p>
<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;">After complaining about this KCM last week, I wanted to give it a try to improve it a little. I think that the biggest stopper here is wanting to keep the screensaver here, because we've ended up with a 3-head monster:
* simple locker
* plasma-based locker
* xscreensavers
Since it seems it's something we may want for the moment. IMHO, we should end up with the Plasma-based option alone. I just tried to re-organize it in a way I like a little better.
What I did
- I aligned the locking labels to the left, like the Form Layout suggests. It creates a small puzzle, I'm unsure if that's a problem.
- I added toolTips and whatsThis in the locking type option buttons, so that we can at least figure out what will happen when we lock.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </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;">just messed with it for a while.</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>kcontrol/screensaver/screensaver.ui <span style="color: grey">(6524e27)</span></li>
<li>kcontrol/screensaver/scrnsave.cpp <span style="color: grey">(0125620)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/106768/diff/" style="margin-left: 3em;">View Diff</a></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Screenshots </h1>
<div>
<a href="http://git.reviewboard.kde.org/r/106768/s/758/"><img src="http://git.reviewboard.kde.org/media/uploaded/images/2012/10/08/screensavers_400x100.png" style="border: 1px black solid;" alt="result" /></a>
</div>
</td>
</tr>
</table>
</div>
</body>
</html>