Hipnot

For the most part I’ve been pretty happy with my Hiptop (you can read my early adopter excitement in the archives), but one thing that’s been incredibly frustrating is the complete lack of response of the CSS rendering problems (namely improperly rendering style sheets that are specified for “screen” media types [and ironically ignoring those specified with type=”handheld”!!!]) are still with us.

I gave ’em a rundown tonight night after spotting a recent thread on new server software, and for the blogs that haven’t undergone redesigns, they render exactly as I reported last October. So, I posted a rant on the forums, although I honestly don’t know what difference that’ll make considering those with much more clout already made their voices heard to no avail.

Still, I thought I’d mention it because it pisses me off. With all this talk about moblogging, I’m surprising this hasn’t been in the conversation more. I mean, sure Mena picked up a Hiptop recently (and hey, why not, they’re literally free after rebate w/ a contract nowadays) and posts tons of neat little hiptop camera shots on her site, but have you tried visiting dollarshort on your Hiptop? Give it a try. While you’re at it, give Six Log a visit. And try some of these fancy schmancy ‘standards compliant’ sites. Give Wired News a shot, or DevEdge, or any of the high profile W3C sites coming out over the next few months.

These sites should work on the Hiptop. They’re designed to be accessible for multiple devices. But they don’t. Because Danger doesn’t care.

You have your clustered web farm and you’re set to go. Except for session handling. You could depend on load balancer for session affinity, you might have some collateral damage (lost sessions) if a machine goes down. You’re probably better off with a separate custom session handler instead (attached to a HA architecture of course):

Currently Programming

PDF output w/ PHP: FPDF has several advantages over PDFlib. Among them are that it doesn’t need to be compiled in, and has a bunch of high level features, including: automatic page breaks, line breaks, and columning, as well as extensive docs and tutorials online.

Which is not to say that it’s still not a pain in the ass. Developing is especially a pain because 1) Acrobat Reader is a bear to reload and 2) Errors still stream out to Acrobat Reader. I’m debugging with lynx –dump.

Related: TTF2PT1 – True Type to PS Type 1 Converter, t1utils – Type 1 font utilites (does to/from mac conversions!)

[20030303 – Update: Phil recommends PDF::API2 for Perl]