Incidentally I've been developing a Java browser for the DT, keeping the data in an Apache Derby database (a small footprint Java relational DB). The browser and search facilities were almost trivial to set up. The advantages of Java are that it's completely transportable across platforms (well maybe not DOS; but is anyone using the DOS version of DT?) and that the apps are very small.

I'm running Derby as a desktop app at the moment, but it can also run in server mode with only a minor change to the program (load a different driver). Also it's trivial to make it handle other databases - MySQL, Access, ODBC - it really only needs the program to know which database driver to load.

The data structure keeps my preferred semantic distinctions - ie song text separate from notes and identification fields.

I'm also adding a song entry feature so that you can keep your own songs and tunes in the same database. Planned features are to hold abc tunes in the database and to keep links to external tune/music files. I'm also implementing an abc2.0 system (the spec has remained in draft for several years now and no work is being done on it as far as I know. It must also be said that there are some problems with the spec that I would change - macros in particular aren't well thought out, but I believe there ought to be some standard to use.), also in Java, intending ultimately to generate PS and use the Toastscript (Java) PS renderer to display the tunes. Sadly work has to stop until mid-August now as I have other things to do, but I'll keep you posted.

Mick