I will try to contribute in Wonko's place while he's gone, but don't get your hopes up, my time is just as limited, and split between many projects.

However, I have finally gotten this to the point that I can semi-announce (full announcement thread when I'm sure it works as desired and can package it): Monitor Clock. This is that clock style I've been working on from almost the day this Advanced Clock Plugin came out.
MonitorClock.tar

It features:

• Technically support for all the features the other clock styles have - 12/24 hour modes, show/hide seconds, fill/stroke for the numbers/letters, and I think text resizing and text recoloring should work too, but the catch is there isn't as much room for the text for you to make it bigger. It supports the Klingon fonts and the .png pictures for numbers as well.
• cpu/mem applet improved clone. Clone in that it shows the same info as cpu/mem applet, improved because it shows the info more accurately and gives a little bit more info for mem usage. Namely, unlike CPU/MEM applet, this shows five bars instead of four. This lets it use even 20% intervals for determining when to show the next bar, so for example for CPU it uses ≤20%, ≤40%, ≤60%, ≤80%, and =100%, to show bars 1-5 respectively. CPU/MEM applet uses somewhat odd numbers which do make sense, but if you want to know slightly more accurately how much CPU or RAM you're using, it's more intuitively accurate then trying to remember cpu/mem's numbers, in my opinion. My clone also shows both the "actually" used memory (as the cpu/mem applet), AND the truly used memory including buffers. It shows gray bars for the true memory use, and white ones that override the gray ones for actual non-buffer/cache memory.
• WiFi Signal bars. Effectively a clone of the WiFi Signal Applet, except it uses 5 bars to show the ten different signal strengths. E.G. 1 = one gray bar, 2 = bar becomes white, 3 = second gray bar above that white one, etc. This spot also shows a gray X when the wifi driver is completely unloaded, and shows a white X when the wifi driver is loaded but not connected (although right now it can also show a white X when it is still technically connected but has horribly bad signal, to the point where it detects it as 0% signal.
  And the best part in my opinion:
• Colored bars to show how much data (in packets) is being received and sent over each interface (wifi [wlan0 and mon0], phone [there are separate interfaces for basic telephony like sending sms and actual gprs internet; this shows both separately], usb, bluetooth, and the "local" interface). This will also show packets received in monitor mode by the wifi card, and if you have the right version of lxp's driver, it will show the packets sent when injecting too (the normal bleeding edge wifi driver lxp released didn't actually count injected packets as sent - I asked lxp about it and he sent me a slightly modified one that did, though).

This last one I'm hoping to have This last one I'm hoping to have people test and report back on, because I'm not able to test the GPRS one or the bluetooth one effectively, as I have neither 3G/internet data on my plan, nor have been able to set up bluetooth PAN or DUN to test bluetooth interfaces. This is also really the only thing I have left to iron out before I feel up to releasing this to Extras-Devel. Though ideally I would still love it if someone knew how to get raw I/O data over these hardware peices, instead of the interfaces over them, since there's a decent amount of data over them that this can't pick up.

Now this clock style is pretty heavy as far as clock styles go, but as near as I can tell this does not slow down the N900 or impact performance - except for at boot where - especially if combined with other status menu python programs like Advanced Power Monitor or whatever, status menu takes a noticeably longer time to load.

Now screenies:
Just showing a comparison between cpu/mem and wifi applets along with my clock style. After my reflash a couple days ago, I haven't bothere to reinstall either of those applets because my clock style replaced them, but I had kept them for the purposes of making sure mine were working right and so that I could take screen shots to show both at once (screenies are from before reflash) - mainly you see the general similarity in cpu/mem, albeit with different bar amounts because of the difference in total bars and which values are assigned to which (also shows wifi signal bars and wifi signal applet at 7):

This shows the telephony receiving some data (you'll notice this regularly if you're using your N900 as a phone - expecially when your phone is about to receive a text message or just hopped to a new radio tower. It also shows one increment of the gray/white bar at the bottom - this is the bar of the mon0 interface. In this case my wifi was in monitor mode and was having a lull in local network activity. I was also not using the wifi's normal wlan0 interface for anything, which is why there are no green bars. If you use the aircrack-ng in the repos or the FruMMaGe (however his name's written) aircrack-gui, your wifi card will use monitor mode on the wlan0 interface, and you'll see the green bars acting up. Also, the X in the above version is slightly higher up than in that screen shot.

These two just show a good idea of typical semi-heavy internet usage and how that will show up - both receiving and sending bars being relatively long, the receiving slightly longer than the sending. The page loading example is a bit misleading since the bars tend to jump up and down a decent amount during the loading of a page, depending on how much has loaded and how much is left.



And tmo won't let me upload more screens at once, so I'll leave it at that. Couple things - a few times, and I can't quite figure out what causes it, this clock style gets twitchy (cpu bar is the main place I've seen this, it jumps from whatever it's actually at to some higher value and back down, repeatedly), and once I had one of the data traffic bars freeze. However, this only seems to happen rarely, and since my reflash it hasn't occured. I suspect it has something to do with different programs trying to read from the same files in /proc or /sys or /dev or whatever. Other than that tiny glitch though, cpu/mem and wifi signal applets and this coexist - not that you need them with this, but if for some reason you feel like having both, it won't break. IF you suspect yours is doing that, simply toggling the lock switch to turn the screen on/off resets it back to normal.

Comments, suggestions, feedback?