From kde-core-devel  Mon Apr 22 18:54:35 2002
From: Thomas Zander <zander () planescape ! com>
Date: Mon, 22 Apr 2002 18:54:35 +0000
To: kde-core-devel
Subject: Re: Gnome Article on UI Design on /.
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=101950203105264
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--LZvS9be/3tNcYl/X"


--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 22, 2002 at 11:47:04AM -0700, Waldo Bastian wrote:
> On Monday 22 April 2002 05:41 am, Aaron J. Seigo wrote:
> > why do you think it is hard to side with a "single idea"? probably beca=
use
> > different people work in vastly diferent ways/methods/environments. so =
you
> > end up with a large chunk of people who need/want it something one way,=
 and
> > a large chunk who want it another. you can either have a niche product,
> > cripple the interface for many users, or be configurable.
>=20
> I think the problem is that many features are being added without taking =
the=20
> big picture into account, without thinking of the feature in terms of "ta=
sk".=20
>=20
> I am currently looking into kcmfontinst and one the things that puzzles m=
e is=20
> that you can choose whether to delete a font or to move it to /tmp. This =
is a=20
> typical example of a bad feature. I don't want to move a font to /tmp. I =
can=20
> hardly imagine anyone else would. Maybe people want to temporary disable =
a=20
> font (why?) and you could implement that by moving the font to /tmp, but =
the=20
> feature to move the font to /tmp is pretty silly. If I want to move files=
=20
> around I use konqueror.

While you are right in the moving part the feature is actually quite nice, =
but
useless in its current implementation.

The thing the author probably wanted to accieve is what the enable/disable =
action
on the macOs (8 is the last I used) extention manager does.

You can click on a checkbox in front of the extention and the thing gets mo=
ved to
another dir; and the other way around if you click it again.
Naturally that approuch is totally useless for the amount of fonts people t=
end to
have on their systems and the logical move to join the feature with delete =
is=20
easy.
That just overlooks the re-activate feature that made the thing worth-while=
 in=20
the first place.

IMO a better solution would be to add a way to deactivate a font and add a =
list
of deactivated fonts which can then be activated afterwards.
A good implementation would be to store the original position of the font (=
the
subdir if you use the advanced GUI) and add a context menu to reenable it.

Just some thoughts...

--=20
Thomas Zander                                            zander@earthling.n=
et
The only thing worse than failure is the fear of trying something new

--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8xFxrCojCW6H2z/QRAk/rAKCq+91V0zhtcdKosQprqg0/PxMpJgCg5Dij
v748NrZAe3hillsjwOsGIjI=
=uNC7
-----END PGP SIGNATURE-----

--LZvS9be/3tNcYl/X--