Holy crap. I was just looking for something completely unrelated to this, but a random neuron got fired, and led me to this page, featuring 8 of Cory Doctorow’s books in iPod Notes format.
That’s too freaking cool! I’ve downloaded them, and will start reading through them (starting with Down and Out in the Magic Kingdom) during the daily commute…
UPDATE: Well, ok… that’s kinda interesting. After the iPod loaded all 500-odd pages of Notes for the books I downloaded to it, I’m really seeing the limitations of the iPod for this kind of thing. I’ll have to go in an rename some of the books so I can read the titles in the menu. And, after scrolling through the first 5 pages of Down and Out, I finally got the the end of the quotes, FAQ, and Creative Commons license… Doh. Might have to add a “Start the book already” link on page 1 of each book. Also, looks like there’s no way to bookmark where you are… Or, to quickly get back to the menu without going back through all of the pages you’ve read. oy.
So, the news of the new 4G iPods has been leaked rather publicly via MSNBC/Newsweek. Ars Technica is saying it’s a huge improvement (they’ve updated their article on AT - the first release of it was so full of incorrect information I was very surprised to see it on Ars!)
My reaction to the new scroll wheel is something like “uh, I prefer the separate buttons, thank you very much.” The combined scroll-wheel-button thingy was created for the iPod Mini, which doesn’t have the real estate available for dedicated buttons. Makes sense there, not so much on the Full iPod.
Following a post by Scott Leslie mentioning the release of Sakai 1.0 rc1, I figured I’d take a swing at installing it on our shiny new XServe.
Installation was a piece of cake (just be sure to set all of the environment variables, and download/configure the ~/build.properties file so it can find all dependencies for downloading). Once the source was downloaded, it really only took a minute to compile and deploy the application (although I spent much MUCH longer than that twiddling around with configuring the build).
Actually, it finally arrived on Monday, after slightly over 4 months on the waiting list. After it was taken out of the box and plugged in, it took maybe 5 minutes to fully configure the machine. Now, we just have to copy some APOLLO apps and resources on it, and it’s good to go!
This beauty sports dual 2GHz G5 processors, and a moderate-sized 80GB drive - we’ll tie it into our XRAID as soon as the card arrives, so it will have something silly like 3.5TB of storage space. It’s a little RAM starved at the moment, coming with the stock 512MB - that won’t do for long…
Mike and I were discussing the XML stuff we’ve been doing the other day, and I suggested we should post the JavaEOXMLSupport framework and JavaXStreamDBAdaptor as open source, to test the waters. He agreed, and so I’ve created a project on SourceForge to host it.
Currently, there are only 2 packages available, in raw source form (with little or no documentation - actually, there aren’t even READMEs in there yet!), but I’ll be updating the releases as we move along, and adding documentation and test apps when they’re ready.
I’m in the process of migrating a copy of the metadata records from CAREO into an XStreamDB database. As part of that process, I’m transforming all documents from various malformed IMS LOM versions to the clean IEEE LOM schema. I looked around for a batch tool, and didn’t find one that didn’t rely on VB or MSXML or something equally unusable for me. So, I rolled my own java command line utility, called “BatchXSLT”.
I finally got around to removing some of the krufty old test records from CAREO. I did a few searches, and came up with a list of 76 records that shouldn’t have been left in the “live” CAREO database - they got added during various stages of software building/testing, by various developers.
Searches should turn up fewer “testing” results, and the “Newest Objects” isn’t polluted by crap added by folks just kicking the tires…
Just came across this entry by Jonathan Rentzsch that goes into the pros of using WOProject and Ant to build complex WebObjects projects.
Here are the summary bullet points:
Cross-project dependancies
Automated deployment
Speed
Open Source
Transparent project description
Cross-Platform
Sounds like it would be perfect for APOLLO, with its several frameworks and adaptors, needing to be built in a particular order, and deployed in particular places. I’ll be investigating building an Ant project for the various bits of APOLLO, and seeing if it will co-exist with the existing XCode build process.
You are an SECF–Sober Emotional Constructive Follower. This makes you a hippie. You are passionate about your causes and steadfast in your commitments. Once you’ve made up your mind, no one can convince you otherwise. Your politics are left-leaning, and your lifestyle choices decidedly temperate and chaste.
There has been some noise on the web because I’ve kept the password for posting to this weblog a “secret”, and that may go against a decentralist philosophy.
The initial plan was to have this weblog used by the “in person” folks at the conference, and for those who couldn’t attend personally to contribute via their own weblogs (hence decentralism). But such is life. This frankensession took on a life of its own long, long ago. So, let’s adapt a little…