This is the week 05 status report for AudioMan and its subprojects.

What was done last week

A few numbers: there were 117 CVS check-ins last week. There are now 23 Eclipse projects: 3 for platform, 5 for build, 11 plugins, 2 features and 2 branding. There are over 400 passing unit tests, most of them inherited from the Java ID3 code I wrote last summer.

Half of the work I did in week 05 involved branding, building and packaging but I also did some development work on the Durham Quick Editor (QE). QE now reads file, MPEG and ID3 metadata and also writes ID3 metadata! Here's a screenshot:

You add files to the list on the left, select a file and then its metadata is editable on the right. QE will be a good way to test Durham plugins for new metadata types and that's why I started on it first. QE will also be a good place to use non-audio metadata plugins so if anyone is interested in doing that it's almost ready to do.

AudioMan and QE will share quite a bit of code so I made two projects to put that shared code: org.audioman.apps.core and org.audioman.apps.ui. In a future post I'll show how all of the plugin projects are linked together (ie. dependency map).

On the building and packaging side, ALL of the plugin projects are built on a default build. A product build file chooses the correct plugins for a specific product and asks the packager build file to package it for a specific platform. I'm considering releasing my AudioMan build files as a separate subproject - RCP-RelEng - so people can use them to build their own RCP apps.

Platform integration for both products on the Mac is almost done. The last thing to to is package all of the product files in the .app bundle and then dmg it. I'm very close.

On Windows the user will just unzip the directory anywhere they want and run the EXE. That's good enough for now but later we'll have to make a real Windows installer.

What got bumped?

• Email results of the build to the releng mailing list -- figure out why Ant's <mail> task isn't working. I'll wait for the new build machine to be set up first.

Unsolved Problems

• If I bundle my RCP product into an .app directory can it still be updated through the Update Manager? I'm thinking no.

New things to do

• Use the new build machine for CVS and nightly builds
• Improve nightly build reports; consolidate JUnit and EMMA reports for all projects to get the big picture.
• Mac: package products in a dmg'd bundle
• Windows: customize the launcher EXE
• Start working on AudioMan's Collection Browsing perspective.
• Make a logo and splash screen for QE