Allan Saddi's projects blog

I took the time to clean up (and that mainly involved ripping out the version checking code) both VanaClock and VanaClockMIDlet. I then threw in a copy of the GPL and slapped the standard GPL header on all of my source files. And now this somehow means it's open source.

Anyhow, see their respective pages for download links.

I got an inquiry about VanaClockMIDlet today. It turns out my webserver was misconfigured and was using the text/plain MIME-type for .jar files (bad!). After fixing that, I found out from the user that though it ran, certain things were broken. Unsurprising, actually, since the sister project, VanaClock, developed overflow problems that I eventually corrected.

I was about to tell him "I'm sorry, I can't do anything" (because I don't have a MIDP development environment anymore), when I decided to just give it a try. So I tracked down MIDP for OS X, ProGuard, and an illusive little Ant task named JarSizeFix. After updating the build.xml file and correctly guessing where the overflow was occuring, I managed to create a fixed version.

At least, it appeared fixed on the simulator.

Anyway, VanaClock and VanaClockMIDlet are projects that I've openly abandoned. Yet I still get feature requests and other inquiries about them now and then. And for some reason, I feel the need to keep the source code locked up. Maybe because they were my first non-trivial Objective-C and Java applications (respectively). There's an element of nostalgia... or embarrassment. Ah well, someday I'll set them free. And oddly enough, I will probably release them under GPL (rather than my favorite 2-clause BSD license). I just need to be bugged about it more...