[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: kdebase/kcontrol/kdemm (silent)
From:       Frans Englich <frans.englich () telia ! com>
Date:       2004-08-25 21:12:28
Message-ID: 200408252112.28763.frans.englich () telia ! com
[Download RAW message or body]

On Wednesday 25 August 2004 20:50, Matthias Kretz wrote:
> On Wednesday 25 August 2004 22:43, Frans Englich wrote:
> > On Wednesday 25 August 2004 20:30, Matthias Kretz wrote:
> > > CVS commit by mkretz:
> > >
> > > Directory /home/kde/kdebase/kcontrol/kdemm added to the repository
> >
> > And here goes another KCM(which will replace another one OTOH). The MM
> > framework is by no doubt important, but so is each KCM, and here's a
> > great chance to make a conscious design instead of it being a KCM which
> > is the "symptoms of an implementation"(not suggestion it will become
> > that).
> >
> > Here's an idea, Matthias:
> > When you've reached an alpha/beta version, write a document which
> > outlines the design decisions you've done. For example, /why/ the
> > configuration options are there, and why they haven't been done
> > KConfigXT-designer only -- why they are needed(we need to keep the count
> > down). Usability folks could then flame themselves to death over it :}
>
> I'm not sure I understand what you're asking. You think we could get away
> without a KCM (btw, there are more KCMs to come) for kdemm? Without any
> configuration except messing with the config files directly or via
> KConfigXT editor?

If configuration is needed, we should of course have it. But judging from 
configuration dialogs of our main applications and the look of KControl, we 
can do configuration better.
What I mean is a document is written which outlines why the GUI was designed 
as it was, and why the configuration options are considered important(perhaps 
some of them only are used by technical/power users and can hence be put in 
the Configuration Editor). Usability people could then provide feedback.


			Frans


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic