--nextPart2658922.heoNh1vmxh
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 07 November 2004 03:03, Dawit A. wrote:
> From my perspective the problem with this proposal is that it completely
> ignores the fact that network transparency is almost always a power user
> feature.

and yet i constantly come across people who are above average to true power=
=20
users who are blithely unaware of our ioslaves.

for one, all our slaves are lumped together in one big family. kio_smtp is=
=20
given the same billing as irc6 as is fish. this makes no sense from an HCI=
=20
perspective. it represents their implementation, not their meaningfulness t=
o=20
the user.

furthermore, we almost never make it explicit in our interfaces that these=
=20
things are available to the user! even with documentation, they have to=20
remember and identify which interface elements can be used to access io=20
slaves.

this is not a power user versus new user issue. i doubt most basic users wi=
ll=20
have a need to explicitly use most of our ioslaves; but i do know that many=
=20
people who can and should be using them are unaware of how to do so or=20
ill-equipped to do so. this is the aspect of the problem that needs to be=20
addressed, since even power users deserve and even require usable interface=
s.

> To me it is much more easier and effective to have a nice tutorial
> explaining the feature than to somehow present it visually.=20

this has been proven time and again to be more effective than nothing, but=
=20
less effective than to qualify as a solution.=20

=2D-=20
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

--nextPart2658922.heoNh1vmxh
Content-Type: application/pgp-signature

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

iD8DBQBBjro61rcusafx20MRAryhAJ9ClrqON3s8MJfdG2955aIdIVIWnQCeJ4vd
B35PR4REZrUu2f02VFVjmPo=
=TUhU
-----END PGP SIGNATURE-----

--nextPart2658922.heoNh1vmxh--