Also, the KDE4 HIG is being developed Wiki-style and is open to comments/edits/ideas/fixes. I'd recommend you look into helping them out Kimmo S (and anyone who thinks they could make positive contributions to the developing HIG.
<br><br>The KDE4 HIG wiki can be found here:<br><a href="http://wiki.openusability.org/guidelines/index.php/Main_Page">http://wiki.openusability.org/guidelines/index.php/Main_Page</a><br><br>Vlad<br><br><div><span class="gmail_quote">
On 10/24/06, <b class="gmail_sendername">jos poortvliet</b> <<a href="mailto:jos@mijnkamer.nl">jos@mijnkamer.nl</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;">
Op dinsdag 24 oktober 2006 17:08, schreef Kimmo Sundqvist:<br>> On Monday 23 October 2006 00:43, Lex Hider wrote:<br>> > Thanks for the feed back. The most appropriate action to take is to file<br>> > bugs for the problems that you find with KDE.
<br>><br>> My two cents on this.<br>><br>> The name of this mailing list has a some kind of holistic ring to it. "If<br>> there is something wrong or odd in the whole KDE, on the overall KDE<br>> experience, but you can't put your finger on it exactly, then this is the
<br>> list to discuss things out and find names for problems."<br>><br>> The reusable component architecture in KDE is really considered one of its<br>> strongest selling points. It has to do with power, meaning what the users
<br>> are able to do with it. But it is also easy to forget the user experience<br>> in all those possibilities.<br>><br>> I recently used OS X for a couple of minutes. Compared to Kubuntu, what I<br>> felt using it was the level of integration. OS X Finder feels like one well
<br>> thought out piece. It feels powerful because everything is easily<br>> accessible, and the user feels that he can try things out and not do<br>> anything damaging or end up in a situation where it is hard to get back.
<br>><br>> Rule: the user should be encouraged to try things out.<br>><br>> Rule: whatever user is encouraged to try, he should easily be able to get<br>> back to the exact previous state he was in.<br><br>
>(more rules)<br><br>if you can define these rules in precise and practical rules for the KDE 4<br>HIG, you can really help with making KDE more usable. if not, it's a lot like<br>saying 'KDE should be better!' and being happy with the great accomplishment
<br>of saying it.<br><br>giving practical tips for the applications (<a href="http://bugzilla.kde.org">bugzilla.kde.org</a>) on how to<br>improve them would, i'm sure, be appreciated. including mockups would rock.<br>saying (something in) the apps are bad is rather useless, as that's something
<br>the developers already know: nothing is perfect.<br><br>> -Kimmo S.<br><br>grtz<br>Jos<br><br>--<br>Disclaimer:<br><br>Alles wat ik doe denk en zeg is gebaseerd op het wereldbeeld<br>wat ik nu heb. Ik ben niet verantwoordelijk voor wijzigingen
<br>van de wereld, of het beeld wat ik daarvan heb, noch voor de<br>daaruit voortvloeiende gedragingen van mezelf.<br>Alles wat ik zeg is aardig bedoeld, tenzij expliciet vermeld.<br><br><br>_______________________________________________
<br>kde-quality mailing list<br><a href="mailto:kde-quality@kde.org">kde-quality@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kde-quality">https://mail.kde.org/mailman/listinfo/kde-quality</a><br><br><br>
<br></blockquote></div><br><br clear="all"><br>-- <br> = Vladislav Blanton =<br> = <a href="mailto:vblanton@gmail.com">vblanton@gmail.com</a> =