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

List:       kde-devel
Subject:    Bug#18947: KDE should use LinuxConf as a source for System and   NetworkApps...why not?
From:       Leon Widdershoven <l.widdershoven () fz-juelich ! de>
Date:       2001-01-23 10:56:51
[Download RAW message or body]

It is up to the distribution providers to deliver this, 
especially since it is often very distribution dependent
which printer tool is installed etc etc.

However, for linux systems running Mandrake or so we could
provide a generic utility - a .desktop file executing 
konqueror with webmin:) (or webadmin or how it's called).
But again this would probably a linux-only solution so 
not fitting with a generic KDE version.

leon


Kuba Ober wrote:
> 
> > You know what KDE really needs, at this moment? System and Network
> > utilites...There are not much System and Network configuration tools
> > available in KDE. I as a RH user can see LinuxConf quite useful and very
> > confusing sometimes ;) due to its Gnomic interface.
> >
> > I request you to kindly use the sources of Linuxconf and the modules to
> > create better KDE based System and Network Configuration and other
> > linuxconf based sysadmin stuff.
> 
> Linuxconf sucks - it's not maintained well enough to stay in sync with latest
> developments. Alas, it's sort of a `nice thing', but for what you'd expect of
> kde control center - it's not enough. Anyway, it's only for linux. KDE is
> very loosely coupled to linux...
> 
> > If you really want KDE to succeed then you got to have full (system and
> > network) configuration facility in it.
> 
> This is no tiny job because KDE works on quite many systems. Nearly each one
> has got its own utilities and configuration file formats. We can easily
> provide configuration for most gnu-style apps (like apache, samba, etc) as
> they are quite portable, but still this is a lot to do. And some of this
> stuff doesn't belong to control center - samba settings for example can be
> implemented more-or-less like in Windo$e - per directory settings:
> right-click on directory, choose Sharing, and then set up whatever sharing
> you desire. You name it, more or less - amount of work to be done is
> seemingly unlimited.
> 
> Then there are other things, like ppp dial-up: each system typically uses its
> own ppp dial-up utility, its own filesystem tools, etc.
> 
> Huge task. But yes, it should be done, and the good thing is that it's
> inherently modular. Once we have say an apache module, it works on all
> systems. Once we have solaris ppp module, we have ppp support for solaris,
> etc. But we must integrate it better with ioslaves and make all the
> functionality accessible from different places in the most natural way (say
> like directory sharing/http/ftp access made available via right-click on
> directory AND via control center/web, control center/ftp, etc.)
> 
> Cheerz,
> Kuba
> 
> >> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

-- 
==========================================================
Undefined behaviour: It works in the debug phase, it works 
during testing, and it blows up in your customers' face.
		Inspired by: Scott Meyers, Effective C++
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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