«« How this Developer sees the Business of Software AudioMan Screenshots: With and Without View Titles »»
blog header image
Week 04 Status Report

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

What was done last week

The build machine Ant scripts are ready to go. They will be modified as time goes on, so it's certainly not done but it's ready for the first iteration. I'm very happy with the results after being inspired by Andrew's build ideas, thanks buddy!

The build machine is building and packaging two RCP applications: AudioMan2 and the Durham Quick Editor; for four platforms: Windows, Mac OS X, Linux GTK and Linux motif. All of the packages are ZIP files around 5 MB each. I love being able to build native-looking applications for four(+) platforms at once with the same code! This should be awesome.

The Windows packages work, the Mac OS X ones do but with a small problem (see below). Roy is going to test my Linux builds when he gets back from Cuba. Thanks!

I'll probably wait until after the first iteration to write up how AudioMan's Ant build scripts work to make sure that they actually do work well in development and on the build machine after some inevitable tweaking. This is the fourth rewrite of the build scripts for AudioMan so I have a good amount of confidence in my Ant skillz.

So what about the monster that is PDE BUILD? I took a look at the docs and decided it wasn't worth learning how to integrate some tools (like EMMA) and partial builds (just compile code, just run tests, etc) into it. It seems like PDEBUILD would be great for a build machine, just not my build machine.

This week I also talked to my excellent web host Epicworks about hosting the AudioMan source code repository and build machine on their servers instead of a Fedora Core 3 box in my apartment under my desk. A hosted box has several advantanges over the home machine:

  • Insane reliability and uptime
  • Faster build times
  • Better public access
  • Backups!
Yes I am paying for this out of my own pocket -- that's how serious I am about AudioMan. The new source code repository slash build machine should be ready this week or next, I'll let you know.

After getting the build machine ready I dug into the AudioMan code. I took the standard RCP template application and modified the perspective, view and action names to match AudioMan. We're all ready to go now, it's off to the races.

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.
  • Publish my sequence diagrams for Durham so that people can review them. Very soon!

Unsolved problems

  • The Mac OS X launcher from the Eclipse 3.0.1 RCP binary distributions that I use for the packages isn't working properly. I think it may have something to do with the way that Ant copies the launcher .app directory but I'm not sure. If I copy the launcher manually, it works! Weird.

New things to do

  1. Be able to add tracks to the track list (no collection persistence).
  2. Connect the metadata retrieval calls from Audible to Durham.
  3. Get Durham reading ID3 and File metadata.
  4. Copy (and relicense) the collection browsing models and Viewers from AudioMan1 and set up the Collection Browsing Perspective to browse artists and albums.

That's quite a bit to do -- and will keep me busy over the next two weeks or so. The long weekend this week will definitely help. If you are interested in writing some code in the next two weeks just let me know and we'll figure out a way to collaborate.

Posted at March 21, 2005 at 08:00 AM EST
Last updated March 21, 2005 at 08:00 AM EST

Question: what are some of Andrew's build ideas?

I wonder if you are having troubles with the mail thing because you have rogers (?) and they have secure SMTP... with the Ant script do you have to put in your ISP's user name / password?

» Posted by: Jim at March 21, 2005 10:45 AM

I'll explain Andrew's build ideas when I explain what my build process is doing. I'd like to give my build process a decent explanation so I'll probably wait until I have time to do it justice.

I'm using the correct SMTP server, username and password and the <mail> task still fails, PLUS it gives no reason for the failure. :(

» Posted by: Ryan at March 21, 2005 11:02 AM

Have you tried using rogers smtp without using the ant task to see if you can get it working? When we had to write our mail clients for school I recall having to do "something" to get it working. I'll update if I remember.

» Posted by: James at March 21, 2005 01:03 PM

Yep, I use the Rogers SMTP server to send mail from my Mac email client -- so I know it works. But Ant is failing on the <mail> task.

It could have been something to do with my build machine, which will be moot in the next week or so when I move to the new build machine and have a new SMTP server to deal with.

» Posted by: Ryan at March 21, 2005 01:17 PM

Andrew here. The build ideas are actually pretty boring (unless you love automation like me), but maybe that's why they are so relevant. I'll talk about my process (its built for .net so it differs slightly from the java world) - and then provide a link here (I don't know how to use the TrackBack ;-()

» Posted by: andrew at March 22, 2005 10:57 AM

Awesome, that will save me some time. ;)

» Posted by: Ryan at March 22, 2005 11:05 AM

Quick note, my blogs are confusing in general - so Ryan may re-write this content so the everyone else can understand.


» Posted by: andrew at March 22, 2005 02:20 PM
Search scope: Web ryanlowe.ca