replacing kcontrol with system settings

[jos poortvliet]

Op Sunday 17 June 2007, schreef Benjamin Meyer:
> On Jun 16, 2007, at 11:57 PM, Jonathan Riddell wrote:
> >> 2. System settings shows only a partial list of the modules
> >> (e.g. the theme manager is missing, which is needed for
> >> accessibility)
> >
> > Arguably the theme manager should be a separate application, but I'm
> > happy to include it along with a few changes (removing the links to
> > other control modules).
>
> Hmm, I see no reason for it to be include and would not make me happy
> if you included it.  It should be a separate application.  It was not
> included in system settings for a good reason and you don't need to
> include it because one person noticed it wasn't there and brought it
> up, a handful of modules are not there and they were removed for good
> reasons.   Does it make any sense to have a background module and a
> theme module that lets you change the background?
>
> You do one of the following:
>   - Configure the background/screensaver etc separately and
> externally have an application that can download themes install and
> configure them.
>   - Only have the theme manager integrated in kcontrol as the one
> method to configure backgrounds etc.

I think the theme manager should be the primary way of changing theme 
settings. PPL should be able to choose a theme, and then customize it. This 
way you wouldn't have all the seperate theme tools. But of course, I 
understand this needs someone to work on...

>   - Have both the separate modules and the theme manager in kcontrol
>
> Putting them both in kcontrol is (and was) just stupid.  It just begs
> the user question: "Which is the right way to configure my
> background?"  How would we document that action?

I'm not diametrically opposed to putting the theme manager AND the seperate 
modules in system settings or kcontrol, though I agree it IS a bit confusing. 
But not including it might mean ppl won't find it, and think KDE doesn't have 
a full theme solution... So it's balancing these two: possible confusion and 
discoverability.

> -Benjamin Meyer

-- 
Disclaimer:

Alles wat ik doe denk en zeg is gebaseerd op het wereldbeeld wat ik nu heb. 
Ik ben niet verantwoordelijk voor wijzigingen van de wereld, of het beeld wat 
ik daarvan heb, noch voor de daaruit voortvloeiende gedragingen van mezelf. 
Alles wat ik zeg is aardig bedoeld, tenzij expliciet vermeld.

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

   A: Because it destroys the flow of the conversation
   Q: Why is top-posting bad?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070617/950019fe/attachment.sig>