gsysinfo is a GNOME panel applet, modeled after the "xsysinfo" monitor. It displays system load, CPU usage (broken down by system/user/nice/idle), memory usage (normal/kernel cache/available), and swap space usage. Each of the gauges can be turned on or off, and the colours can be configured as desired.
Phormation is a set of PHP functions which provide a framework for developing any HTML form connected to a database backend (currently PostgreSQL, MySQL, and ODBC are supported). It allows you to write and make use of reusable widgets so you can develop Web sites more quickly. Phormation has more than 10 widgets including text field, date, file upload, and foreign key select, and is easily extensible. It has good documentation.
Re: While we're at it...
> This primary config application itself
> lives by its own rules, in its own
> unique subdir. And, if we're fitting
> this into the "registry"
> model, then that application is
> necessarily aware of the location of all
> applications and their config files
> (through preferably a discovery/report
> model like the bizarro-ldconfig, for
> robustness). From there, it is trivial
> to write an app that dumps the location
> of all config files to stdout for
> feeding into tar for backup.
Fair enough, but why would I want to implement this when I can do tar -vzf etc.tgz /etc today?
What are the compelling reasons, in your mind, for wanting all application files to live together? What would that allow you to do that can't already be done?
Re: While we're at it...
> Who's benefitting from having config files in /etc, man pages in /usr/man, libraries in /usr/lib, cache and locks and things in /var, and the program binary in /usr/bin?
I am. One way I benefit is by knowing that I don't have to backup my entire system; I can backup the configuration of my entire machine by taking a snapshot of the /etc directory. So it only costs me about 2 MB, instead of 8GB to back up everything I need to reconstruct my system.
> Let's have a bit more than a config read/write library. Let's encapsulate a program and all of its files into a single system subdirectory.
> Installation and uninstallation of a program becomes easy.
It already is easy. If it's not easy for you, try a different distribution (like debian, for example).
> Complete backup and recovery of an application becomes easy.
I already do this. I use dpkg-repack to re-create a package from its constituent files on my system, which means I can take a snapshot of a package and its current configuration.
> A clean separation between programs is better than an arbitrary intermingling.
Why? I find that consistent location of files by function
has advantages (as stated above) over lumping all application files together, especially when your packaging system takes care of installation/deinstallation. How would you propose to separate things like shared libraries "cleanly"?