[Bug 187154] Add kuser, ksystemlog, kinfocenter and ksysguard as kcm modules to be accessible via KDE4 system-settings

[Pino Toscano]

https://bugs.kde.org/show_bug.cgi?id=187154





--- Comment #13 from Pino Toscano <pino kde org>  2009-03-14 22:27:12 ---
> >That does not imply making everything in one just because "it feels better".
> >Mixing different things with totally purpouses (configuring vs just viewing
> >data) makes exactly the opposite effect, ie configusion about "what is doing
> >what".
> 
> To set something good you have to monitor something to know what is needed to
> be set and how.

Examples?

> The first thing is that one is connected to the other so I
> think adding monitoring category in system-settings will not cause the mess
> because every people using linux has to know how to read

So you are saying that every new Linux user *has* to know about
a) system logs
b) system processes
and then we complain "Linux is hard to use" just because we have three separate
applications, each tied for a specific use? This won't work at all.
Weekend users should not need ksysguard and ksystemlog at all; who really need
to use any of them would not bother at all opening a separate application, that
is *tied* to that, and not a "generic container" of whatever has "system" in
its name.

> I know that partitionmanager is being developed but we are talking about
> system-settings modules and partitionmanager is another program and till now it
> has no system-settings module as I know.

Assuming partitionmanager is a kcm: while you do real partition work (eg
resizing, creation, etc), you cannot do any other configuration from the same
application. IMHO this should really bad.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.