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

List:       kde-core-devel
Subject:    Re: Factoring out standard system information
From:       Richard Moore <richmoore44 () gmail ! com>
Date:       2005-12-30 12:04:22
Message-ID: 5491a5150512300404q47d4a2f0xb8f4c6730d6d7818 () mail ! gmail ! com
[Download RAW message or body]

On 12/30/05, Adriaan de Groot <groot@kde.org> wrote:
>
> There's a couple of non-portable system things that are really popular to
> know
> for KDE applications. These are CPU information (load; percentage time
> idle,
> interrupt, user, etc.), swap and RAM information (free and used). Reading
> these data is a pain in the ass, and it's implemented who knows how many
> times across the KDE codebase -- superkaramba, ksysguard and the just
> discovered (and hopelessly buggy) ktimemon come to mind. I think SK has
> the


Also in kasbar and kst IIRC.


So would it make sense to factor this stuff out and stick it in kdelibs
> somewhere? ksysinfo or some such -- one central place to query system
> resource usage, so there's only one place reading /proc/icky/memusage or
> calling sysctlbyname("hw.memusage") or calling table() or using kvm(4).


I think that's a great idea.

Rich.

[Attachment #3 (text/html)]

<br><br>
<div><span class="gmail_quote">On 12/30/05, <b class="gmail_sendername">Adriaan de \
Groot</b> &lt;<a href="mailto:groot@kde.org">groot@kde.org</a>&gt; wrote:</span> \
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid">There's a couple of non-portable system things that are \
really popular to know<br>for KDE applications. These are CPU information (load; \
percentage time idle, <br>interrupt, user, etc.), swap and RAM information (free and \
used). Reading<br>these data is a pain in the ass, and it's implemented who knows how \
many<br>times across the KDE codebase -- superkaramba, ksysguard and the just \
<br>discovered (and hopelessly buggy) ktimemon come to mind. I think SK has \
the</blockquote> <div>&nbsp;</div>
<div>Also in kasbar and kst IIRC.</div>
<div>&nbsp;</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid">So would it make sense to factor this stuff out and \
stick it in kdelibs<br>somewhere? ksysinfo or some such -- one central place to query \
system <br>resource usage, so there's only one place reading /proc/icky/memusage \
or<br>calling sysctlbyname(&quot;hw.memusage&quot;) or calling table() or using \
kvm(4).</blockquote> <div>&nbsp;</div>
<div>I think that's a great idea.</div>
<div>&nbsp;</div>
<div>Rich.</div><br>&nbsp;</div>



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