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

List:       kde-usability
Subject:    Re: Proposal for KControl
From:       Troels Tolstrup <troels () tolstrup ! org>
Date:       2002-06-30 17:54:05
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 30 June 2002 09:42, Simon Edwards wrote:
> Hi,
>
> > On Saturday 29 June 2002 23:13, Waldo Bastian wrote:
> > > On Saturday 29 June 2002 03:54 pm, Joseph Wenninger wrote:
> > > > > Why do we have an "Information" group?  What does that have
> > > > > to do with a _Control_ center?
>
> errrr.... because the same information that is provided is relevant
> to configuring other aspects of the system. Configuration and
> "getting info" about a system are closely related tasks when you
> think about it.
>
> The "Information" group has got to go still. "Information" as a
> concept/grouping doesn't fit the other groups. "Information" is a
> different kind of thing than "Network" or "Sound".
>
> What I would like to see is the "Peripherals" top level get renamed
> to something people understand, like "Hardware". All the read-only
> hardware information 'controls' (Block Devices, IO-Ports etc) be put
> together onto one 'control' page using tabs. This new merged control
> should then, logically be placed under the "Hardware" top level
> group... and called "Information".

But we cant configure the hardware from within kde anyway, so i dont see 
what it is useful for in the rest of kcontrol, so unless you plan to 
make a ms like "device manager" then i dont see the point of this. 

> > > > I don't know. I've thought for a long time that it would be
> > > > better to split it into it's own "System Information" Container
> > > > application (which could be a special mode of the Control
> > > > Center Applications)
> > >
> > > I like that. I can make a patch for that if people like.
> >
> > I do like that. If nothing else, it removes an entire toplevel
> > entry in the control center without losing any functionality.
>
> Please don't go making patches yet. This topic needs to be discussed
> and planned out properly first.

I agree on this in general for the control center modules, but in this 
single case i think it makes sense to make a "system information" 
program instead of having them in the control center, and i think it 
could be a good thing to do that before 3.1. Then later if things are 
configurable from within kde then i think it maybe should go in again, 
but in its current form i cant see what it is doing in there at all.

Mvh
Troels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9H2E0mTmAA3i3lrERAqLwAJ4kLm+KNWvRTMtw/bbr6zMcNWPLAwCbBmVZ
8KyTnUNFJ0+3ARK9K7TxyWw=
=w4jE
-----END PGP SIGNATURE-----

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]