-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 26 Aug 2004 00:12:47, Aaron Seigo wrote:
> at the BOF meeting we also discussed how to put out requests for studies so
> that those who can do field studies know what sort of information we are
> looking for, how to manage the lifecycle of this information between
> usability teams and developers, looked at the (ongoing) kdepim experience
> and more. all in all, quite a productive roundtable for usability issues.

Which is why I think everyone should wait, see what comes out of this and not 
go off on a massive tangent, so steady on Frans and take things at more of a 
measured steady pace. Looking around the openusability site, and at the 
emerging repository of information and knowledge, I see good things here.

On Thu, Thu, 26 Aug 2004 04:09:29, Frans Englich wrote:
> As we know, what the HIG is and what it's not, what goes in and what goes
> out, must be well defined.

Well yer, but a HIG does not mean usability being put into action. Will people 
understand that having a HIG guarantees you absolutely nothing? It's 
important that it is done right, and that it happens, but I get the 
impression that some people think that having a HIG is vereything. Only when 
you have guidelines, and start using them and working out where they are 
sensibly used, that your problems really start :). That's why I like what I 
see with the openusabiliy stuff, and the stuff coming out of akademy. There's 
more background thinking to be done.

> Accessibility is a subset of usability(taking a certain user group in
> consideration) and artwork is also a subset of usability(focuses on a
> certain technical part, not widgets, but pictures and colors):  

No, they are not. There is cross-over, and collaboration, and they are 
separate areas that fit together like a jigsaw puzzle. They're not the same 
thing, nor does one come under the other.

> "hardcore writers" will be on the list, and this typical knowledge net
> caused by different people who knows what goes on in all corners, and
> what's relevant, is lost. All the expertise the people on the current lists
> have, is missed.

I don't think kde-guidelines is meant for this purpose.

Cheers,

David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBL6Ie53OaWc7M8G0RAkTMAKCa2pcVH8Em2rbBYfb3qeOwp+K48QCfaOFJ
0jdMhzg70aZg1ZDasQajffo=
=aLjv
-----END PGP SIGNATURE-----
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability