KCM rename

[David Faure]

On Wednesday 19 July 2006 16:45, Friedrich W. H. Kossebau wrote:
> Am Mittwoch, 19. Juli 2006 11:02, schrieb Matthias Kretz:
> > Hi,
> >
> > as KCModule and friends are not bound to KControl anymore I believe a
> > rename of the classes is in order. In Trysil Aaron and Ben said to call
> > everything KSettings:
> > KCModule -> KSettingsModule or KSettingsPlugin
> > KCModuleInfo -> KSettingsInfo(rmation)
> > KCModuleProxy -> KSettingsWidget
> > KCMultiDialog -> KSettingsDialog
> > KSettings::Dialog -> KSettingsDialog
> > KSettings::CompontentsDialog -> KSettingsDialog
> > KCModuleContainer -> KSettings(Module|Plugin)Container
> >
> > Another obvious name would be to use Config, but KConfig is already taken.
> > I'm not satisfied with the name change yet and before I'd tackle such a
> > drastic change I'd like to hear some more opinions.
> 
> But what is the semantic difference between config and setting? Why is that 
> stuff called config in one place and setting in another? Looks strange to me.
It's not the same stuff. Matthias' proposal is:
config == file on disk
settings == end user GUI
Given that the above says "KSettingsDialog" and stuff like that (never just "KSettings"),
I think this is fine (it says as part of the name, that it's about the GUI).

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).