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

List:       kde-devel
Subject:    Re: Hidding Virtual size column by default in ksysguard
From:       "Mark A. Taff" <marktaff () comcast ! net>
Date:       2007-01-05 20:46:15
Message-ID: 200701051246.15604.marktaff () comcast ! net
[Download RAW message or body]

On Friday 05 January 2007 11:33, Aaron J. Seigo wrote:
> On Friday 05 January 2007 12:19, Matthew Woehlke wrote:
> > Personally (as a developer)
>
> this is the salient point of this email, imho.
>
> who is the primary audience for ksysguard? developers? if so, then optimize
> the default interface for them (us) and they (we) expect/want to see.
>
> similarly, if the primary intended audience is sys admins, users or green
> battlefrogs ... optimize the default interface for them.

I support John's solution, and as such don't agree with Thiago's position.  My 
reasoning is that I want to know at a glance how much memory a process is 
using, excluding shared memory.  To me, that is a much more meaningful and 
practical number.

As for my category, I am a power KDE/CLI user who dabbles and is learning 
C++/QT/KDE development (I can program in several other languages).

>
> options to show other aspects of avilable, reportable data can cater to the
> secondary, tertiary, etc. audiences.
>
> and to be honest, i for one an tired of having to explain Yet Again to a
> concerned user that no, kfooapp is not taking 48MB of their RAM all on its
> own.

My fiance, though beautiful and intelligent (hi honey!), would be among those 
wondering why the heck kfooapp was taking so much memory.  Someone once said 
that a little inaccuracy saves a lot of explanation.  I think this is a prime 
case where the default should be a little inaccurate for the sake of 
comprehension.

Regards,

Mark
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]