I have decided to add GUI support for Fedora 8 to my supported Linux distributions. Bringing the total to two, with the other as Ubuntu. The C++ & Java code still runs everywhere. I was only testing the Ubuntu version because, that is what I was using.

I started with slackware ( on floppies no less ! ) and bouncing through several distributions, I landed at Ubuntu. I was a big RedHat fan until they made the split. I just wasn’t happy with Fedora then ( And I am still not happy now ) and I started on the part to Debian systems.

So after speaking with a RedHat user, I think RedHat would be the other Linux to support. I am not supporting RedHat because of the costs ( and the Fedora thing ).

So I have downloaded Fedora 8, and I will make a new VMWare image over the weekend and start giving Fedora a try.

I renamed the classes for RaydoConfig to RaydoStartup. It still does the same, but it seems much more natural to express it this way. While true that these settings are only used at startup, I want to avoid confusion with the configuration settings that are coming off the backplane.

The classes still read the raydo.ini/raydo.rc startup file as they did before, only the class name changed.

Thanks to the advice of a person who shall remain nameless, I have posted the first draft of the Contributor License Agreement in the svn source tree. Unfortunately , I am not shipping any more tarballs until the other legal stuff gets settled.

The doc is in the doc folder as Raydo Contributor License Agreement.txt


As with anything of this nature, this is a work in progress.

I have been doing a lot of work with Java. A lot of it in getting the     C++ and Java interfaces to align. So when I went looking for a database engine, I settled on H2 for the Java engine.

    Since you can run Raydo in an application, H2 can be run in an embedded mode, as well as HSQLDB and Derby. It can also be run as a client / server and a cluster.

The ‘plugin’ was added to the Java tree.
    So looking at the benchmarks, it seems that H2 is faster than HSQLDB & Derby in the embedded space, and comparable with Postgres and MySQL in the client/server space.

About two weeks ago, we started making amalgamated header files.

It turned out to work much better than we thought, so we are going to make it the standard way for releases. So starting today, only the amalgamated version will be available for download of svn.

I have been putzing with unit testing frameworks all week. I could not find one I really liked. First a lot were too complicated for my purposes. Most of my unit testing exercises computation. Making sure 1 + 1 is 2, is what I really , really need. The other gripe I had is the text file output. I want somewhat is databaseable. I want to look back and see when something stopped working, with out digging thru a lot of files or doing the svn thing. You know, pulling out old copies, running the unit tests to see where things broke. Granted, I only had to do that a few times, mainly when I had a busted import into svn. Oh, and I wanted the same output accross implementations since the interfaces will be developed in parallel.

So I decided to write my own. Not as featured as JUnit, CUnit, G-Unit , but functional. It has databaseable output and fits in a header file in C++. So that is getting dumped into svn, but it won’t be in the release for a while.

And I know databasable and putzing are not real words.

We are moving to an amalgamated header file. The development version will still have the separate header files for each class/group of classes.

Raydo is a header only development library. Just include one file in you application to use the framework.

There were too many header files originally and it is much easier to have one include file. The mutiple files will still be there if you need them.