Yeh I see what you are saying, if I remember rightly you can indeed bind shortcuts (involving the windows (or "super") key to locking and other things though I have a feeling they are bound to other things by default (if at all). I wasn't necessarily suggesting not having the functionality (it is something KDE has which can be very valuable), but I don't feel that using it over having the currently well organized menu is a good idea.<br>
<br><div><span class="gmail_quote">On 05/02/2008, <b class="gmail_sendername">Andrew Laignel</b> <<a href="mailto:a.laignel@ukdotcafe.com">a.laignel@ukdotcafe.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Webmaster, <a href="http://Jhnet.co.uk">Jhnet.co.uk</a> wrote:<br>> "I also think the addition of the power off button on the main bar is<br>> also silly<br>> for the same reasons - your only ever going to use it max once per<br>
> session."<br>> No, it is something very valuable, though only really on mobile or<br>> public systems: when I am using my laptop it allows me to quickly<br>> throw it in to suspend or lock the screen when I walk away. It is<br>
> something that I have found many users come to love once they get used<br>> to it being there (for the most part the ability to lock, suspend or<br>> switch user is handy (especially in a school-like or family<br>
> environment). While the user switcher is probably necessary I do feel<br>> the power button is a worth while addition, especially given that we<br>> are taking up a solid 24 odd pixels of the users screen that, lets<br>
> face it, do very little more than provide a launcher, clock and status<br>> items. (I am not debating the need for the top panel, things<br>> definitely become crowded all squashed into the bottom, but this area<br>
> should be utilized better.)<br>To be honest the hate I have for the power-off button is mainly due to<br>the fact it's an ugly blob. If it was a bit more elegant and discreet I<br>would probably have less problems with it.<br>
<br>Is the Windows key not used on Ubuntu still? One of the nice things<br>about Windows is WIN+L locks the computer (WIN+D is minimise all). I<br>also generally set the power button my laptop to hibernate and just use<br>
that. I do see how the power button may be of use to other people though.<br><br>Maybe make it look nicer and put it in the system tray? It could also<br>then handle power settings and other bits and bobs.<br>> "As an example from Windows XP, the 'new style' Start box has on the left<br>
> hand side a list of your most commonly used applications. I've set it<br>> to display 12 at once and you can pin items to it permanently. As a<br>> result if you use an app more than a couple of times in future is never<br>
> more than two clicks away with no need to scan a list for it."<br>> I agree this is definitely a useful function that would be nice to see<br>> however given how well organized a typical gnome Applications menu is<br>
> compared to a windows all programs menu (without any user<br>> intervention) it becomes less important. While teaching basic<br>> computing skills to elderly people (I run classes for a charity called<br>> Age Concern) I find that many are confused as to why their programs<br>
> sometimes appear in the frequently used list, why they move and why<br>> all the programs they need are not there. In this scenario, well named<br>> and *subject categorized* (not manufacturer or application suite<br>
> organized) programs lists are a generally good idea. What would be<br>> nice is a way of making it more obvious that they can add their own<br>> applications to the top bar to allow single click access to them and<br>
> to make use of the space there rather than ending up like windows'<br>> quick launch that many people do not realize can actually be added to.<br>><br>> Just some thoughts<br>With regards to your Age Concern example - and I have tried to teach old<br>
people computing - it's a difficult task - but it sounds like the<br>problem isn't due to the idea being flawed but instead the<br>implementation of the idea being flawed. The task is to implement the<br>idea in such a way as to avoid the problem you have stated.<br>
<br>I am a massive proponent of usability, but I am also heavily against<br>dumbing down and definitely do not believe in catering for the lowest<br>common denominator. While all effort must be made to make a system as<br>
intuitive and useful as possible I do not believe that you should remove<br>or not include useful additions simply because a minority may have<br>problems initially with them.<br><br>--<br>ubuntu-art mailing list<br><a href="mailto:ubuntu-art@lists.ubuntu.com">ubuntu-art@lists.ubuntu.com</a><br>
<a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-art">https://lists.ubuntu.com/mailman/listinfo/ubuntu-art</a><br></blockquote></div><br>