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

List:       kde-bugs-dist
Subject:    [Bug 127728] Wish: display more details for a process (like
From:       John Tapsell <johnflux () gmail ! com>
Date:       2009-05-21 10:47:39
Message-ID: 20090521104739.9BC34169E6 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=127728





--- Comment #9 from John Tapsell <johnflux gmail com>  2009-05-21 12:47:35 ---
(In reply to comment #8)
> (In reply to comment #7)
> > err... that's really not what I meant. (...). Please take a look at process
> > explorer, you'll understand what I mean. :)
> 
> I use process explorer daily and it's indeed a *great* application. But if I
> understood John's comment correctly, he is wary that he'll get such a large
> number of requests for some features to display that he wants to make it easy
> for developers to create (and distribute ?) their own apps.
> 
> On the UI side, the new "detailed" monitor could be launched from ksysguard. Or
> a default dialog could easily be implemented in terms of the base bricks inside
> ksysguard itself. It's all about having a flexible design from the start.

That's exactly what I meant :-)

The process list part is actually always in memory when running KDE, so that it
can load when the system is under heavy strain (since that's when you most want
to kill a process).  So the process list part itself needs to use the minimum
amount of memory.

So what I want is a seperate process that is launched when you want to view the
details of a process.

Also on the flexibility side, ideally I want to spend a weekend writing a
simple application that is just a single browser widget and a javascript engine
with a couple of a functions to read files from /proc.  Then rely on other
people to write the complex html to display the huge amount of information
available in /proc for a process. (which frankly I don't understand).  It would
be great for someone to write a parser for the memory maps, for example, to
show the memory usage of the apps, visually seeing how applications are sharing
memory.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]