I’ve come to the conclusion that PHP libraries are simply designed to eat up RAM and do their very best to never spit it back out. There seems to be an assumption that everything will be done in RAM and then at the last possible moment dump everything out to the browser. Sadly, this doesn’t work if what you’re building in RAM happens to be a zip file containing a whole heap of images.

Apparently my bashrc is append-only: export gucis=z1419539@gucis.cit.gu.edu.au: For those who didn’t study IT at Griffith Uni, gucis is the student UNIX server. This particular shortcut was so that I could scp files over there more easily. Actually, given that gucis had open access to the Internet and my dorm room didn’t1{#footlink1:1243014118649.footnote}, it was far more often transferring files from gucis back to my local machine. I finally removed those shortcuts today.

The otherwise mostly link bait suggestion from Matt Asay that Apple and Google should drop their browsers in favour of FireFox triggered an interesting reaction for me. The argument goes along the lines that IE is dominating the browser landscape and FireFox is clearly the second place runner, so everyone who wants to bring down IE should just pool resources behind FireFox. My immediate reaction was to wonder why people saw FireFox as the best horse to back.

Since my last question was so quickly solved thanks to Kaushal Sinha, I thought I’d try a simpler one. I need to set up a page in WebSphere Portal that doesn’t appear in any of the navigation structure but it does need a known URL. It’s used only as a landing point in the portal, has a portlet that asks a couple of questions and then sends the user on to the right place.

I’m stumped so I’m throwing this one out there in the hope that someone might know the answer. I have a JSP component that builds a URL to create a new content item, in a specific site area with a specific authoring template. It works great on Portal 6.0.1.3 and Portal 6.1.0.0 but breaks on 6.1.0.1 and 6.1.0.2. When you go to the URL, it correctly starts creating content but instead of skipping the stage where it asks for an authoring template it just gives a blank list to choose from.

Note to self: That magical file that controls just about everything you ever want to control about IBM LWCM (at least so far as things that are controlled from the file system rather than the web interface) is under the profile directory at /wcm/shared/app/config/wcmservices/WCMConfigService.properties This includes: configuring backwards compatibility for WCM 6.0 -> 6.1 migrations. Primarily the don’t expire content immediately when no expire date is set. setting up the SMTP server properties so you can get e-mail notifications in workflow Side note: These get annoying really quickly if you’re not careful.

Rob wanted to know where I’ve been getting the clip art images on my recent posts. They’re from the seriously cool, but overly hard to use, Open Clip Art Library. They have a ton of SVG images so when combined with Inkscape can be converted to PNG images at any size. I wound up downloading an old archive release of the library which includes PNG versions of all the images and now use OS X to browse and search.

The conversation that has sprung up around how the use of distributed version control, Github in particular, affects community is a refreshing change in the blogosphere1. It’s people collectively thinking things through rather than just reacting in uproar or following the latest meme. The latest installment is from Ben Hyde, git: Balene for Knowledge2. It’s definitely worth reading in its entirety, but let me pull out a couple of key points:

A few handy links about JavaScript techniques. Loading Scripts Without Blocking – Steve Souders Coupling Asynchronous Scripts – Steve Souders Why I Don’t Love JavaScript’s Module Pattern – Jonathan Snook I find the last one on JavaScript’s module pattern most interesting. It’s main reason for existing is to add the concept of private variables to a language which was designed without any access controls. It reminds me a lot of the argument around typing in languages.

Our office in Windsor has a huge window at the front which makes a nice atmosphere on clear blue-sky days like today. Occasionally,it also provides entertainment, from the odd kid knocking on the window to watching the occasional drunk singing as he goes by. When the Queen is staying just up the hill at Windsor castle, we often get a couple of the Queen’s guard on horse back come down for a coffee next door.

JavaScript libraries are awesome – they make it possible to develop cross browser coolness without going completely insane working around all the incompatibilities. The trouble is, we’re talking about JavaScript libraries. Instead of working around differences in browsers, now you work around differences and incompatibilities in JavaScript libraries. While the simple response is to just pick one and stick with it, there are some problems with that: If you’re developing a library, you will very likely have users who are already committed to a particular library.

I spent the weekend discovering just how poorly thought out and poorly supported closed captioning is in online video. Some highlights (based on the SRT format because that was the only one I could find any information about syntax for): Definitive guides to the format either don’t exist or are so poorly used that they don’t appear in the first 3-4 pages of a Google search. Timestamps use a non-standard format.