Replace KcmFontinst with kio_fonts

David Faure dfaure at
Tue Mar 11 19:01:00 GMT 2003

Hash: SHA1

On Tuesday 11 March 2003 19:18, Neil Stevens wrote:
> On Tuesday March 11, 2003 10:05, Craig Drummond wrote:
> > > Please don't do this.  KIO is a nice flexible backend tool, but it's a
> > > lousy user interface.  Konqueror is nice for viewing files, but it's
> > > not a
> > >
> > > generic system administration tool.  Please don't force users to treat
> > > it as one.
> >
> > But surely this makes the job of installing fonts easier, and more
> > intuitive?
> I think a determined UI designer can do a better job than a hope that
> "intution" will make the user know what to do.

I think the best UI (at least the most common one) for copying/moving/renaming/deleting 
files is definitely one of a file manager.

> > Fonts are just files, and all a user wants to do
> > is copy these somewhere where they can then be used.
> Maybe to you they are files.  But to a user, they are a system service just
> like an application.  Also, on most X systems, installing fonts is more
> than just copying files around.  Any KDE UI should be equipped to handle
> such systems.

Surely kio_fonts can automatically add the font to whatever file needs to list
it, etc. The only manipulation the user should have to do, to install or remove
a font, is to copy or delete it.

> Sure, it *could*, but throwing away opportunites for good UI design is the
> step backward.

The config module would remain, for complex things that need a specific UI.
But if the config module opens "konqueror fonts:/" for "here's where you
can manage your fonts", this should definitely make "font management"
Once again, this would be "in addition to", not "as a replacement to", the kcm.

- -- 
David Faure -- faure at, dfaure at
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions
Version: GnuPG v1.0.7 (GNU/Linux)


More information about the kde-core-devel mailing list