KDE system guard

Lubos Lunak l.lunak at suse.cz
Tue Oct 11 15:19:51 BST 2005

On Tuesday 11 of October 2005 15:54, Mirko Boehm wrote:
> On Tuesday 11 October 2005 15:22, Lubos Lunak wrote:
> > > I agree here. Maybe it can be integrated with kwin's feature to kill
> > > hanging windows.
> >
> >  No, it can't:
> >
> > - KWin itself can't create any windows (well, or at least I don't feel
> > like trying to complicate my life that way)
> >
> > - It's a window manager, not a process monitor, and somebody can also use
> > some other WM with KDE
> >
> > - When KWin kills a window it also tries to kill its application if it
> > can (which it usually can with modern apps)
> I do not want to be a PITA, but...
> What you say makes sense, but from the users point of view it is irrelevant
> - the user sees two different process managers.
> The difference between windows and processes is unclear to the user, he
> expects us to kill the process(es) if he kills the window.

 Which KWin does if it can. And I don't see why it should do more than that.

> To me, ksysguard 
> should be the "advanced view" to the "kill a hanging window" dialog.

 Why? Not that this would be a problem technically, the kill hanging window 
dialog is a small helper in kwin/killer, but I don't see the point from the 
users point of view. If you try to close a window and it doesn't respond, you 
get this dialog and you decide whether you want or don't want to kill the 
offending app. If you for some reason want to run ksysguard at exactly this 
point, you also most probably know how to launch it yourself.

> The necessity for a process manager should be clear (honestly, if you have
> ever used a windows system, who has *never* had to use the task manager to
> kill an app?).
> --Mirko.

Lubos Lunak
KDE developer
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/

More information about the kde-core-devel mailing list