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

List:       kde-usability
Subject:    RE: KAdmin
From:       "Jamethiel Knorth" <jamethknorth () hotmail ! com>
Date:       2004-08-01 6:31:43
Message-ID: BAY7-F15mtkmzc3DPcj00043157 () hotmail ! com
[Download RAW message or body]

>From: Frans Englich <frans.englich@telia.com>
>Date: Sat, 31 Jul 2004 23:02:01 +0000
>
>
>For long buzzed about is KAdmin, similar to KControl but
>does only contain server administration functionality(which KControl have 
>in
>addition to user preferences), and has KParts as content instead of
>KCModules.
>KAdmin would have kernel configuration, boot manager,  "pseudo modules"
>linking to web admin interfaces, kuser, KIOSK(no, that's nothing you need 
>as
>a regular user) -- all integrated under one roof. KAdmin would typically be
>installed on servers only.

[snipped a ton]

I'm all for KAdmin being conjured. The system is in need of simplification, 
and that is one way to give it.

When I was looking at module layout, I also decided that a Hardware Center 
was needed, due to how much actually involves the hardware.

What do other people think about having that (that would leave KInfoCenter, 
KControl, KAdmin, and KHardware all for use in managing the system)? The 
domain of hardware overlaps a lot with KAdmin, but I see it too often being 
a non-admin task (on home systems) and having too many options to fit 
cleanly into KAdmin.

I'm not leaning to strongly one way or the other on a KHardware tool being 
separated from KAdmin, I just wanted to make sure it was given some thought.

_________________________________________________________________
Don’t just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/

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