Yes, cutting-edge autoconf technology is making gchrom work for YOU! Yeah. I've got it compiling with autoconf, which I hope will make gchrom work on a wider range of platforms, but I'm sure it won't work on just anything. Needs gtk+-2.0, libgnomeui-2.0, and libpanelapplet-2.0. But at least it'll compile with a ./configure and a make.
I'm using RedHat 9 now (yes, I'm right on the bleeding edge), so I've updated GChrom to work with the Gnome 2.0 panel and GTK+ 2.0.
The holiday season has slowed me down in getting things started on Sourceforge. But here is a beginning.
There is now a gchrom homepage at http://gchrom.sourceforge.net, and the CVS is now populated. Interested parties can now check out the CVS and (hopefully) build gchrom. This marks the first time that my gchrom code has been made available for public use. Hurray!
Since things work stably with just a few minor quirks, I am considering releasing what I've got as version 0.1. There should probably be a bit more user documentation before I do, though. Perhaps a source tarball will be up soon.
Well, good news to everyone reading this, which is likely nobody at time of posting but I hope that will improve. Anyway, the gchrom project was approved by Sourceforge today, which means that over the next few days I will be putting things together as a Sourceforge project. The actual gchrom program has been running on my desktop (RedHat Linux 7.3 with XFree86 4.2 and Sawfish 1.0.1) and in my panel (GNOME 1.4) for the past two days without any trouble. But of course there are always other desktops. I don't know how to make this work well with KDE (though the standalone mode should work), and I haven't tested this on other Unices, since I don't have access to them. And there are always new features to be considered. So there is still work to be done, just not exhausting work.