On Mon, 4 Apr 2011 20:24:50 +0200 "[email protected]"
<[email protected]> said:

> 2011/4/4 المسالم المسالمة <[email protected]>:
> > hello again
> >
> > it seems i didn't clear my idea here
> >
> > i already know that this environment had alot of modules here that will just
> > make system monitor is a bad idea
> >
> > and with this thinking in your minds
> >
> > you didn't get the point of such request like this
> >
> > you see
> >
> > i didn't request this thing for monitoring the system because we already
> > have those modules which can do such a thing like that
> >
> > i requested that because how can i suppose kill some programs if it can't be
> > closed from its gui
> >
> > seriously
> >
> > in this case i will use this SYSTEM MONITOR to kill it from there
> >
> > you see thats why i requested this thing
> >
> >
> There is already a way to kill not responding windows in window menu.
> Sure, no problem with requesting features, but you'll need to convince
> a developer that he needs the feature that you want to have
> implemented. If it's not implemented yet it means no one felt the urge
> or didn't had the spare time to do it.

FYI... with netwm properites apps provide PID properties (not all do, but these
days most do) (_NET_WM_PID). this means e KNOWS the PID. e17 will, if you press
close, and IF the app sets delete request (99% of apps set this). if apps also
do ping protocol, e knows if the app is hung and not responding to events, and
if it becomes hung, and you tried a close, after a timeout it will KILL the PID
for you. so actually no need for such a system monitor to kill processes.

now.. if you truly DO want to kill the process.. the window menu "kill" will,
if netwm_pid property is set, sent a sigint (ctrl+c) to the process, then if it
is hung (netwm ping protocol) after a timeout, will send a sigkill (kill -9).
so in most cases you dont NEED such a system monitor... in a modern world e
will go trying to kill processes for you as part of its "closing" setup. if the
app doesnt set the pid prop - it's most likely some old style thing, so e just
kills off its x connection. it may be a remote app.

sure. this doesn't cover processes that dont have a window, but it makes the
NEED for such a system monitor thing with process lists much less so that means
there is little need to work on it as most cases are handled automatically
without such a thing. sure - it can be useful but the amount of usefulness is
significantly reduced, thus priority of it is very low.

as i explained. not on the todo list for e17 release. if someone wants to do
it... they can. :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [email protected]


------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to