Another oversight by Apple, another third party Quick Look plug-in. This one is for .webarchive files saved by Safari. It isn’t great, but it’s functional.
Posts Tagged ‘Mac OS X Leopard’
Lorem ipsum dolor sit amet, Apple?
Sunday, August 10th, 2008If you make a text clipping in Leopard, you’ll be surprised to discover that QuickLook can’t generate a preview for it.
A surprising omission by Apple, given that Leopard still generates these when you drag text to the desktop. But Google found HetimaClipping.qlgenerator, which fills the void:
A moldy corner in Mac OS X Leopard
Friday, February 29th, 2008Apple claims fix to Time Machine security bug
Monday, February 11th, 2008Apple claims to have fixed the issue where applications could run automatically out of a Time Machine backup. Look for CVE-2008-0038 in Apple’s About the security content of Mac OS X 10.5.2 and Security Update 2008-001 .
Thanks to Apple for mentioning me. I certainly would have reported the bug regardless, but it’s a nice bonus.
The only thing I wish had happened differently was an earlier acknowledgement from Apple that they realized what I was describing and agreed it was a security problem. I didn’t find out Apple considered it a problem until January 22nd, when they asked how I’d like to be credited for discovery. Most of that time I wondered if I should file more details in an attempt to convince them it really was a problem.
Note: I’m saying “claims” only because I haven’t installed the update and verified the fix yet. I have no reason to disbelieve Apple.
Stacks: Disaster mitigation?
Thursday, December 20th, 2007I consider Stacks the very worst feature Apple’s ever added to Mac OS X (or Mac OS before it). Even QuickTime auto-play could be turned off! So I was very pleased to see a report that 10.5.2 fixes stacks (in the same way people fix their dogs). Hooray! (via Daring Fireball.)
Leopard’s date column
Tuesday, November 27th, 2007The Finder is generally pretty good at reformatting the data column to show dates without truncation. Give it enough space, and it will display the date as “Friday, November 23, 2007, 12:52 PM.” A little less and it is supposed to drop the Friday part. A little less and it switches to a numeric format.
Unfortunately, it seems less than perfect. Sometimes it keeps the long format with columns that are too narrow, as seen in the following picture:
Why? I don’t know. It seems they put so much effort into this already, it’s hard to imagine why they didn’t make the final push to make date columns always usable.
Radar #5612934.
Stacks as modern art?
Tuesday, November 13th, 2007Okay, I don’t like Leopard’s stacks. In fact, I could go on a large rant about all the deficiencies compared to putting a folder in the Dock in Tiger. That doesn’t seem to matter, though; they’re here to stay.
Instead, I thought I’d talk about something completely different.
Namely, stack art. Here’s what came up today after I cleaned up my Downloads folder of everything except the files I wanted:
If you’re curious, the acorn is Acorn from Flying Meat1 and the leaf is Coda from Panic2. Both of these are applications I’ve been meaning to try out, but haven’t really had the chance yet.3
Of course, this was complete luck. Still, it makes me wonder: What have you seen on your Dock that was interesting? Did you do it on purpose, or did it just happen?4
- See also: Gus Mueller’s blog. Gus is the developer of Acorn. [↩]
- See also: Steven Frank’s blog and Cabel Sasser’s blog. Steven and Cabel are the founders of Panic. [↩]
- Come to think of it, not only do the icons go together well, but so would the applications. You three should talk! [↩]
- It counts if you do it on purpose, it just counts slightly less! [↩]
Time Machine failure details
Friday, November 9th, 2007Latest backup failed, I see. So what’s the latest backup that actually worked? You can’t tell here. And what failed? You can’t tell that, either.
“Click that red icon!” you might think. Here’s what that does:
That’s not very helpful. It could at least tell me if the error occurred when reading, writing or in internal logic. That’d be a start.
There’s a little more information in the console log, of course. What actually failed? It looks like Time Machine tripped on an email. Nothing special about that email that I can see. But how many end users are going to look in there?
Here’s hoping 10.5.1 fixes a few things about Time Machine.







