Guidance in KDE Admin

[Nicolas Ternisien]

Thank you for your review of those apps.

Of course, the goal is not to put Guidance folder into KDE Admin and wait
the next release of KDE 4.

So each Guidance applications (with the approval of main developers, I would
like to remember that I've never modify any lines of code of this project,
and I'm only talking in the name of KDE Admin coordinator) will follow the
classical way of improvements, comments, comparison between existing apps
(I'm talking in this case about KUser/Userconfig, KSysV/ServiceConfig,
DisplayConfig/XRandr) and finally kdereview move to be sure we won't lose
features, well thought ergonomy or ideas.

As some people said previously, KDE developers/usability and users will have
more ideas with something concrete, so I will come back here with some fresh
meat in some weeks/months.

It's just for the moment a good news that you agree with the Python hard
dependency.

The last important approval before starting anything is now from Simon
Edwards, who is the main and original developer of Guidance

Sorry Aaron, I've attributed you a good idea shared with others ;-)

On Thu, Mar 27, 2008 at 1:03 AM, Jakob Petsovits <jpetso at gmx.at> wrote:

> On Wednesday, 26. March 2008, Nicolas Ternisien wrote:
> > No other opinion ? If you agree, just say Yes/+1 or No/-1, just to be
> > sure this is something useful, and that will help KDE Admin being more
> > interesting.
>
> Guidance's modules are mostly cool, but I never liked its runlevel config
> module.
>
> It doesn't attempt to explain what those four "Multiuser Modes" are good
> for
> or what's the difference betwen those (and the "Singleuser Mode"), or
> which
> one is the one that is relevant to my standard session.
> Its list view doesn't contribute to a good overview of the services that
> should be run, the matrix view of the sysv-rc-conf ncurses tool does a
> much
> better job at that.
> The "Halt" and "Reboot" runlevels also use the "Start at Boot" column
> despite
> the services being shut down actually. (If you don't know that, you're
> screwed.)
>
> On the whole, I personally would not leave Guidance's runlevel config in
> the
> hands of a user who doesn't know upfront how to configure this kind of
> stuff
> via the command line. If that module goes into KDE Admin, it needs a
> serious
> rework of the whole user interface.
>
> Guidance's userconfig mostly duplicates KUser, although the latter is not
> implemented as a KCM module and has a slightly different interface. It
> would
> be interesting to see which application provides a better starting point,
> and
> merge features of the other user configuration app into that one in order
> to
> prevent two apps in KDE Admin that have the same goals.
> (displayconfig vs. xrandr has already been mentioned by Jonathan.)
>
> I find mountconfig and wineconfig very nice, they do fill a gap and are
> sufficiently nice on the user interface. If you work on getting Guidance
> into
> KDE Admin, I would assume those two to be the most worthwhile targets.
> Plus the challenge to merge displayconfig/xrandr and userconfig/KUser
> features
> into one each.
>
> In hope not to sound too offending, wishes,
>   Jakob
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080327/c0023cad/attachment.htm>