Rands on slides

Rands has written some really great articles on how to give and prepare for seminar presentations (too lazy for links; use Google). Here’s another gem of his via Twitter:

If you can’t practice the hell out of your slides, you can, at least, care the hell out of your slides.

I believe the point here is that with carefully-done slides, half of your problem is solved already. When your slides don’t help to pull you along in your train of thought, it’s easy to lose momentum and lose the coherency of your overall “message”.

Oh god, my eyes

A little while ago I complained about the “Podcast Information” window in iTunes.

Well, there’s now been an iTunes update, and I’m sad to say things are now much, much worse. On the plus side they fixed my bug.

It’s a pity they had to hit the damn window with an ugly stick at the same time.

Come on, guys. It’s not that hard. At least the old one had some padding in there:

And that new shadow looks ridiculous. Really.

---

They also didn’t paid any attention to improving its behaviour. That’s okay. The other new features in iTunes 8 are rather nice.

But this window now floats above all others even when iTunes is not frontmost. This is the least appropriate behaviour this window could possibly have. I guess I’ll have to file another bug report…

iTunes’ “Genius” logo

This logo, for iTunes’ new “Genius” feature, is only going to look good once we have displays capable of 200 dpi:

Too many jaggies in the lower half of that centre orbit.

Google Earth and running

Let me just say that one of the few actual uses I’ve found for Google Earth is utterly indispensable to me right now. Path distance measuring:

With only eleven days to go before the 12km City to Bay run, I’ve got some training to do…

A thought on iPods, 2008

Jesper wrote the definitive prediction list for what Apple might reveal in this year’s iPod lineup refresh, but I just wanted to make a comment or two to see how badly I’m wrong when the announcements are actually made.

Firstly, I believe that if solid state drives were large enough, Apple would have no problem retiring the iPod classic. Not that it doesn’t have advantages over the iPod touch (“blind” operation, first and foremost), the iPod touch is a much better device in the scheme of things.

However, while it’s possible the iPod touch could reach 64GB this year, I still don’t think that’s big enough to drop the 160GB iPod classic. Next year, though, definitely.

Jesper raised a possibility I hadn’t considered: the iPod shuffle could be retired in favour of the iPod nano. (Not the iPod nona, which still has strong support in the Mediterranean community.) Considering you can buy 4GB flash drives for less than $30 these days, it’s probably going to happen sooner rather than later. I think the timing is a shade too early to completely drop the iPod shuffle entirely, and this is a change that will be happening next year, not this.

If a new product was going to be announced, I’d peg money on a re-designed iPod nano that has a similar form factor the iPod touch but much smaller. That is, an approximately 16/9 ratio device with a screen on one side and a button or two on the edges. Removing the scroll wheel allows for a large screen without really increasing the size of the whole device. And I think the screen would be just large enough to accept a limited range of input behaviour.

But really, I don’t think that’s going to happen (I can imagine an iPhone nano product sooner than this one); my predictions for this year are lack-lustre: no new products, very big de-emphasis on the iPods shuffle and classic; bumps on specs and price drops across the line for the iPods nano and touch. Hopefully bigger announcements regarding software and services. It’s about time for a bit of a refresh of the iTunes store, methinks. I could dream about a re-designed iTunes itself, but I don’t want to get my hopes up.

The chngpage package vs the changepage package

It occurs to me that there aren’t many people writing on the web about LaTeX. Mostly, I suspect, for the same reasons you don’t see as many people writing about HTML+CSS these days. It’s just a tool that some people use.

(That’s not to say that there aren’t periodicals and the like for people to write about what’s been going on.)

Anyway; here’s a nugget of information that might be of some use to some people in the near future.

Peter Wilson’s memoir LaTeX class is a major, recent, project that ties in many ideas for how to layout and customise a document in a single class. Some of the ideas in the class are also broken out into separate packages so that people who aren’t using memoir can still take advantage of them.

“chngpage” was one such package. It allowed you to locally change the layout of the text block in various different ways (for example, to place a figure that is centred on the physical page rather than centred in the text block). It also provided the very nice ability to robustly detect whether you’re on an even or odd page at any given position in the document (which is harder than you might expect).

Unfortunately, because chngpage was written before memoir it differed in one important way; to cut a long story short this made it tedious to write code that required the chngpage package because you had to jump through hoops to get it working in memoir as well. (As an example, see my addlines package.)

The problem was that neither memoir nor chngpage could be changed because of backwards compatibility problems. So Peter Wilson wrote a new package “changepage” that provides the same functionality as chngpage but uses the same interface as memoir; the result of this new package is that chngpage should no longer be used.

While it can still be found in the “obsolete” section of CTAN (here), chngpage is no longer included in TeX Live (as of TeX Live 2008). Packages that use it should switch to changepage, which is simply a matter of something like s/\ifcpoddpage/\ifoddpage/ for those who like regular expressions.

That reminds me. I’ve got a package that uses chngpage that I really need to update now…

Update: Fearless Leader (a.k.a. Karl Berry) has convinced me that any backwards compatibility problems caused by removing chngpage outweighs any nice ideological benefit from removing the package entirely. So it still exists in TeX Live! (Which was not my decision, but I agree with it.) The moral of the story, in the end, is the same: in new documents and packages, use the new changepage so that you play nicely with memoir

iTunes’ “Podcast Information” window doesn’t scroll

This is bug #6139143.

SUMMARY

iTunes’ “Podcast information” window doesn’t accept scrollwheel or two finger trackpad scroll input.

STEPS TO REPRODUCE

• Open the “Podcast Information” window (note that there’s no menu item for it, too)
• Select a podcast with a long enough blurb so that the scroll bar appears
• Try and scroll the text with the trackpad or with a scroll wheel

RESULTS

Doesn’t scroll.

Should.

NOTES

While we’re on the subject, what’s with that weird window re-size widget?

Problems with LyX #1

This is the first article in a possibly ongoing series documenting the problems in LyX that I’ve had to debug for people in my department. If you’re not a LyX or LaTeX user, there won’t be much to interest you here.

I’m a LaTeX guy through and through, and while I would never think of writing in LyX myself, I can totally appreciate that “normal” people find LyX much more approachable (and easier!) than LaTeX. Nonetheless, LyX is a rather leaky abstraction, and most errors that people have are due to their complete lack of understanding of the underlying LaTeX layer. In my limited experience.

That’s okay; LyX is free software and they can’t afford to test on beginners. I’m sure heavy LyX users (and the developers) don’t run into the same problems that I have to solve, because they know what they’re doing and don’t make the same mistakes. At the same time, I’ll go out on a limb and suggest that sometimes their knowledge of LaTeX isn’t as comprehensive as someone like me who actually writes documents and programs packages in it.

Now, the errors I report here are necessarily vague and don’t pin down problems very well. That’s because I can’t afford to spend any more time on this at all. That said, if contacted directly I’ll do my best to reply quickly and in as much detail as I can. Here we go:

• Please make it much easier to insert a floating graphic; it’s the 99% case and should be a single action in the GUI. New users see “Insert graphic” (or whatever it says) and paste it inline in their document. If it were wrapped in a float, they’d get what they actually wanted.

• Especially in maths mode, if non-existent macros are typed they shouldn’t be displayed in a pretty way. For example, I had a user who was used to typing “\alpha” to get greek type slashes before all roman characters in maths (e.g., “\x”). The visual display in this case (simply an italic “x”) implied that this was legal when it in fact produced sometimes complicated errors (in the case that an accent macro was typed such as, say, \i).

• The prettyref package for automatically formatted cross-references is basically the worst choice from a variety of packages that do this function. Use the refstyle package instead.

• If there is no bibliography inserted in the document, please prompt for one (with explanation) if a citation is attempted. It’s not obvious that you have to insert a bibliography before you’re allowed to reference citations (the logical flow is the other way around: I cite a paper and a bibliography is created from that). Adopting the biblatex package and putting the \bibliography{} into the preamble would help things in this regard.

• File paths seem to continue to be a big problem. Yes, it offends my sensibilities when people use analphabetic characters in the directory names (not to mention spaces), but these damn users are just doing what the OS allows. If putting a LyX file inside the folder “# New Stuff/” causes the compilation to fail, then it should either protect the path better or just tell the user straight up to rename the folder.

• This may no longer even be a problem, but a while back it was fiendishly annoying debugging a problem where something like “vector $[a,b,c]$” was put inside a subfigure caption. The reason? Subfigure captions are input in LaTeX in square brackets, so any square brackets in the caption need to be hidden from the parsing. LyX should automatically wrap the subfigure caption with curly braces behind the scenes.

That’s all for now. That these are only minor details, which is a testament to the highly useable state the LyX team have brought their program over the years. Here’s to a brighter future yet.

Naming in a bibliography

So, how should it look? The bibliography, I mean. Is it the author or the work that is the most important aspect of the citation? In other words, how much emphasis should be placed on the name? Here are (most of) the possibilities for representing people’s names, let alone the rest of the citation information. Enumerating the types has helped me decide on a style for my thesis.

The default for the biblatex package is to place the first author’s last name first, which makes the bibliography look more obviously alphabetised:

Robertson, Will S., Ben S. Cazzolato, and Anthony C. Zander

This is a nice example but I don’t think it’s helpful for displaying the names more clearly. All last names first removes the inconsistency of reversing the name order of the first author only:

Robertson, Will S., Cazzolato, Ben S., and Zander, Anthony C.

In all of these “full name” cases, I’d prefer to use the European tradition of printing the last names in small caps for emphasis.

Will S. Robertson, Ben S. Cazzolato, and Anthony C. Zander

But maybe first names don’t matter, and should be normalised away to single initials:

Robertson, W. S., Cazzolato, B. S., and Zander, A. C. (*)

or

W. S. Robertson, B. S. Cazzolato, and A. C. Zander

With names in initialised form, it just doesn’t work to have mixed name orders: (The possibility of too many adjacent initials.)

Robertson, W. S., B. S. Cazzolato, and A. C. Zander

I’m inclined to favour the starred example above. Mostly because full first names aren’t always supplied by authors (or the references to them), so without the “initialisation” you’d get a mix of full first names and initials between different entries in the bibliography.

The counter-argument here is that bibliographic databases should always provide first names to avoid problems of author ambiguity, but this is a printed bibliography we’re talking about, not a bibliographic database. Nice to be concise.

And really, it is the work that’s important. The authors of the paper provide, perhaps, a taste of the authority the paper might hold, but whether it’s interesting to chase up should rest entirely on how it’s being referenced in the work in which it is cited.

Improving iTunes’ “Podcast Information” window

Open a playlist that contains podcasts and turn on the “Description” column in the “View Options”. Each item in this column contains a circled “i” icon that opens up the “Podcast Information” window.

I have two small suggestions to improve this window:

• There should be a way to open/show this window with a keyboard shortcut, and (optionally) a menu item as well. Shift+Cmd+I is a suitable candidate (and this shortcut could also toggle the visibility; that is, hide the window when it is already visible).

• Only the selected row should display the icon to minimise the visual clutter of displaying this icon on every row. This is analogous to the “iTunes Store” links that are displayed in the respective name/artist/album rows when viewing music listings.

This is Apple “bug” #6075588.

The New Yorker’s (now) curly quotes

Say, whaddya know?

Now that’s much more attractive.

Expensive connectivity

Okay, look. I know that Australia is a technological wasteland and it is damned expensive to have us connected to the global grid because we’re so far away from everywhere. Download limits on our internet, and all that (I’m currently allowed 11GB per month for which I pay AUS$45). Read Neil Stephenson’s ridiculously long and entertaining article on undersea data cables (“Mother Earth Mother Board”) for some insight on why it’s expensive to get internet down under.

It’s always been expensive to access the internet in Australia. Our first plan when I was a teenager cost $5 per hour at 14.4 kbps. These crazy prices were always initiated by our national carrier, Telstra, who charges through the roof and caters only to those who don’t have the time or energy to shop around to the cheaper alternatives. Or who live in regional areas.

Yes, Telstra does a lot of infrastructure work, including having to cater to this regional population that’s not huge in number but spread over an enormous area — think trying to economically provide internet to every resident of New York City but spread them over the entire land mass of America. Not an easy, or cheap, problem.

Nonetheless, there are competitors to Telstra (in the civilised parts of the country) that manage not to charge ludicrous amounts for their services. To use the example above of how much I pay for internet at the moment, the equivalent Telstra plan by price is $40/month which gives me paltry 400MB and 15¢ per MB after that. OUCH.

To be fair, paying $90/month is pretty much the same as my current $45 plan, so it’s only twice as expensive at the higher end of the scale.

On that note, let’s look at Telstra’s new rates for iPhone 3G. There’s a story in The Australian that compares the different carriers in more detail. Well, here’s the simplified look:

Carrier   Cost      Calls    Data
Telstra   $80/mth   $ 70      5 MB
Optus     $79/mth   $550    700 MB

What. The. Fuck. That’s orders of magnitude difference, even after considering that the per-minute rate for calls is about 30% cheaper on Telstra. The article is bang on the money as to the reasons behind this huge pricing chasm:

… the low data capacity has been included to protect Telstra’s walled garden of online content.

The day that big telcos get out of the services game and realise that their purpose in life should be to make money in connectivity, and that’s it, will be a happier day for everyone. Just let me pay for bits from where-ever, and compete doing that the cheapest and fastest and most agnostic way possible. We don’t want to buy goods from an ISP.

iTunes’ “Shuffle” is repeatable!

For years now I’ve been getting frustrated with iTunes’ seeming repetitiveness when listening to music with ‘shuffle’ turned on. I find ‘Album Shuffle’ a pretty good way to listen to music: just select the album you want now and a random album will be cued up in due course. (Listening to full albums is, of course, the only way to properly listen to music.)

You’re not stuck with the interruption of choosing what to listen to next (without getting stuck into listening ruts at the same time), and of course there’s nothing stopping you from skipping the album if you’re not in the mood.

Every now and then I’d realise that after going back to a previously-played album that I wanted to listen to again, the next album that started playing “randomly” next was in fact the same one that started playing next last time. I’m not the only one to have noticed this.

Try it out for yourself. Turn on Shuffle, with ‘Shuffle: Songs’ checked in the Playback preferences. (You get the same problem with both albums and songs.) Start playing a song and hit ‘Next song’ a few times. Keep track; here’s me:

• Down By The River, Live At The Fillmore East, Neil Young & Crazy Horse
• Les bras de mer , Le phare, Yann Tiersen
• The Believer, Chrome Dreams II, Neil Young
• Everything Will Be Alright, Hot Fuss, The Killers
• A Drop in Time, All Is Dream, Mercury Rev

Now go back to, say, the second one, and hit play. Hit next song. Wouldn’t you know?

• The Believer, Chrome Dreams II, Neil Young

Just to prove it wasn’t a fluke, hit next again:

• Everything Will Be Alright, Hot Fuss, The Killers

I don’t know about you, but I find this behaviour incredibly (a) annoying, and (b) stupid.

Sure, you should be able to retrace your steps backwards in the random sequence. But under no circumstances should I be subjected to the same random sequence if my only crime was to want to re-listen to a particular favourite.

In Apple’s internal database, this is bug #6033030.

Applescript for iTunes: ‘Next Album’

Here’s an Applescript I like to use. I listen to iTunes with ‘Album Shuffle’ activated, so I don’t have to think about what to listen to next. (And, embarrassingly, to keep the music going after an album finishes; if I’m thinking about something when the music stops, I’ll totally forget that I had music going in the first place and sit in silence for hours.)

The problem is that sometimes you don’t want to listen to a particular album. And there’s little worse than hitting ‘Next Song’ a dozen times to skip to the next one. Luckily, iTunes is rather scriptable:

tell application "iTunes"
    pause
    set |current album| to the album of the current track
    repeat while the album of the current track is equal to |current album|
        next track
    end repeat
    play
end tell

The New Yorker's straight quotes

Usually The New Yorker is the epitome of good and consistent typographic design. Oops:

Note that they’ve got it right for the running text, but for whatever reason the quotation mark in the lettrine remains uncurled.

Mathematica packages of mine

A couple of years ago I picked up Mathematica to use for some of my PhD research. And I quickly grew enamoured to its programming style and mathematical capabilities; as opposed to Matlab, my other tool of choice, which acts like and (mostly) has all the grace of a glorified number cruncher.

Since using Mathematica I discovered a few things it can’t do so well and wrote some packages to help myself along. The cost-benefit time ratio was heavily skewed against me, but what the hell. In for a penny, in for a pound. I could hardly ditch Mathematica because it couldn’t output graphics (say) in a form I felt to be sufficiently suitable.

Now, Wolfram has a site set up as a centralised repository of Mathematica code: the Wolfram Library Archive. At present I have three packages that live there:

• ColorbarPlot co-authored with Mike Croucher,
• FixPolygons co-authored with (actually rewritten by) Michele Ceriotti, and
• FakeRegionPlot.

(I don’t, sadly, have time to elucidate their existence right now. Some pretty pictures would be nice.)

The terrible shame, however, is that Wolfram has a huge problem actually updating those sites. A few months ago I sent them updates to these packages and I’ve yet to hear any reply. It makes my life hard if I need to pay attention to whether people are even able to access the most recent versions of my code. Frankly, I’m far better off hosting the code myself.

(Cue suppressed announcement of a long overdue actual website that I’ll one day create but which is on ice until I finish my PhD.)

So here I’d like to point you all to the canonical repository for this work (and any future work as well): wspr/mmapkg at GitHub. It contains the three packages above in addition to a couple of other packages that aren’t as generally useful (yet).

I’d recommend that you use these links instead of the Wolfram ones; who knows how long it will take me to update the Wolfram library versions if it takes so long for them to get back to me. I understand the time constraints, but really. CTAN (for TeX and LaTeX code) is staffed by volunteers and they usually check and upload packages for me within 24 hours.

The other advantage to using GitHub for this sort of work is that it makes things easy for anyone interested in using these packages to make changes and fix bugs in my code.

Since posting the original versions at various times I’ve collaborated with two authors on two packages respectively to improve the features and performance of the code. It’s just so rewarding working in collaboration with people I’ve never met because we share some sort of passion with this tiny piece of code.

While I don’t expect any of the readers of this site to actually be using Mathematica (shout out if you are), hopefully Google will render the information here useful to some people at a later date.

Update: Mike Croucher has made his own announcement of the new version of ColorbarPlot with a great explanation of what’s new and — even better — some pretty pictures.

Update the second: The most recent versions of the packages are now (finally) available at the Wolfram Library (16 July, 2008).

‘Happiness’ by Matthieu Ricard

My reading drought is over! After being stuck on a couple of books for the entirety of this year, I’ve finally got through one of them. Trying to read in parallel is simply a bad idea, even if one is fiction and the other non.

The subtitle of ‘Happiness’ is ‘A guide to developing life’s most important skill’. With respect, this is exactly what ‘Happiness’ is not, but I’ll forgive the marketing people for sexing up the idea of the book.

Oh, sure, there’s the occasional exercise in which we’re advised to perform deep meditative acts, but colour me sceptical that a non-meditator will be able to derive much outcome from such exercises without years of practise. (Indeed, my own experience confirms this :)) Not that the simplifications used to promote these techniques aren’t useful: when grumpy, meditate on your grumpiness itself and you’ll realise it’s meaningless — suddenly you feel better. In a perhaps overused analogy in the book, the negative emotion disappears like a snowflake in the spring sunshine.

What the book does do to great success is inspire one to take up a path of developing their happiness — and it’s not surprising that the teaching that the Buddhist Ricard espouses is Buddhism itself. But that’s, in fact, the strength of the book in my eyes. While Christians might stumble around trying to prove the power of prayer, the Buddhists can equivocally state why and how their practises help develop the mind from an objectively point of view.

Or perhaps I’m swallowing their bait, line and sinker.

Regardless, what this book emphasises is that being happy isn’t a genetic or environmental factor that’s out of your control. Rather, we create our own happinesses in our own minds, and with practise one can be happy all of the time. Sounds good, right? Well, Ricard spends an entire book teasing out the idea of being happy all the time. I guess the easy way to sum it up would be that once you’ve worked out the meaning of (your own) life then you’ll be happy. Simple, huh? Well…

This book isn’t just a “swallow this pill and you’ll be happy” solution. The pursuit of happiness is inextricably tied to the way we live our lives. Perhaps another way to boil it down is to say “be optimistic always, spend every moment doing what you should be doing, and make other people happy at the same time”.

Realistically, everyone’s search of happiness, if they are even trying, will follow a different path. The appeal of this book is that it’s a great elucidation on the different little meanings around “being happy”, and inspiration that our brains are tactile enough that, with practise, we can live our lives in a positive frame of mind.

Now, where do I sign up for meditation lessons?

A new TeXShop console window

Sometimes I expend energy doing things that to the untrained eye look like a waste of time. Take TeXShop’s console window:

That’s easily the single ugliest window I have to look at on a daily basis. Running Matlab is a close second, but I’m not doing that quite so often these days. But considering both my work and my play is done in TeXShop, that’s a lot of ugly looking right back at me.

Eventually you just can’t take it any more.

In the end, a few long minutes messing around in Interface Builder yields a relative delight:

Ah, bliss. I’m literally a happier man for veritable seconds every day. I’m sure you’ll agree that the benefits of this can not be understated.

---

A couple of notes about the design of the window itself. Note the output of TeX is hard-wrapped before printing to 80 characters, so it’s essential to have a fixed width font in there. Using Helvetica as the default is just crazy. Since we know that 80 chars of Monaco 10 takes up about 500 pixels, the window can be fixed to that width. (To do this “properly”, you would want to adjust the width of the window depending on the size of the fixed width font that has been chosen.)

I’ve added a slight yellow colour to the window; this facilitates easy of background recognition when you’re trying to grab a background document. When there are three windows per document (source, output, console), it’s important to distinguish them in little ways. It would probably be better to consolidate the console window into the source, visible only during a typesetting run; this is more work than I have time for, however.

The placeholder text has been carefully constructed to try and get people to use the various commands that are available on error during a TeX compilation. The best is i, which replaces the token on which the error occurred with whatever text you write. Pity it doesn’t also edit the text of your document to synchronise the correction. Again, it would be better if this text field only became visible after an error had occurred.

The destructive buttons “Abort” and “Trash Aux Files” have been moved to the right to separate them from the constructive button “Goto Error”; I like adding keyboard shortcuts to interface elements (in heavy moderation, of course) so that I remember to use them.

Finally, the scroll bar (that disappears when not required, by the way) is mini-sized. Scroll bars are an anachronism in the era of two-finger scrolling and mouse wheels/balls (to a certain extent; they shouldn’t be eliminated entirely), and the fewer pixels used for their representation, the better.

Update: the NIB file can be downloaded here: TSDocument.nib.zip. To install it, pull up a contextual menu on TeXShop in the Finder and select ‘Show Package Contents’. Then drop it into Contents/Resources/English.lproj/ (or as appropriate for your localisation; only tested with English). Probably a good idea to make a backup of the original…

The man who absorbed the world

One day I’m going to write a fairy tale about a man whose affection for the people in his life grows without bound, unchecked, until he ends up absorbing into himself everyone that he loves in the exterior world and then becomes totally alone. It may or may not be partly auto-biographical.

The whole notion of “absorbing” another being seems a little creepy when taken literally, but that’s kind of the point.

Applescripting Mail.app

Applescript support for Apple’s own applications has typically been absent or poorly implemented. Leopard’s Mail.app is no exception, which is a pity because there are many nice things that a functioning scripting interface could perform. In this post, I’ll expound a couple of irritating bugs I have quickly run into while trying to write Applescripts for Mail.app; I’ll finish up with a useful Applescript that actually works and that I frequently use.

Bug the first

This one’s easy to sum up: get the properties of just doesn’t work. This works fine:

tell application "Mail"
    get the front message viewer
end tell

The usual way I write Applescripts is to just bung in a the properties of after the get to receive a nice list of, well, properties that I can extract and set for the object. Sure, I can get this sort of information (in the abstract) from the documentation, but querying the object with Applescript is easier and much more useful for debugging purposes. Alas, Mail does not support this, despite claiming to be able to:

properties inherited from item [snip] properties (record) : All of the object’s properties.

Here’s an example of the fail:

tell application "Mail"
    get the properties of (the front message viewer)
end tell

Update: this is Bug ID# 5981534.

Bug the second

I find Mail’s “Inbox” to be largely useless, because I filter much of my mail into sub-mailboxes as it arrives. Only unfiltered Mail is shown in the Inbox, which isn’t very helpful when there’s no “jump to next unread message in any mailbox” feature.

To work around this perceived problem, I have a “Smart Mailbox” to collect all Mail that needs my attention:

The “Message is in Sent” is so that I file/delete my own messages rather than let my Sent mailbox accumulate to thousands and thousands of emails.

Now, I really like Mail.app’s ⌘1 shortcut to select the “Inbox” mailbox. But since I don’t use the Inbox, I’d much rather it select my “Attention!” mailbox instead. This is the perfect case for Applescript, and should be a one-liner:

tell application "Mail"
    set the selected mailboxes of the front message viewer to {mailbox "xxx" of application "Mail"}
end tell

where xxx is the name of the mailbox. Well, sure, that works fine for a regular old static mailbox. But for a smart mailbox? Not a chance.

tell application "Mail"
    get the selected mailboxes of the front message viewer
end tell

With a selected Smart Mailbox the result is {application "Mail"}, and trying to set the selected mailboxes to a Smart Mailbox just gives an unhelpful error. Not very helpful at all, in the end.

Update: this is Bug ID#5981547.

Bug the third

This bug is less major because it can be obviated by using GUI scripting. I’m not really a fan of GUI scripting, though. Not very elegant (says the Applescript user).

Anyway, I’d like to be able to customise the template used to construct “Reply” emails (as you could in Mac OS X 10.2 or so by tweaking some hidden system files); specifically, I find the line

On 02/04/2008, at 9:13 PM, Will Robertson wrote:

terribly verbose and overly detailed. There’s a couple of other things that could be improved, too (cf. this year-old post by John Gruber in a similar vein; by the way, I’m a staunch bottom-posting advocate — although I prefer a top poster than a bottom poster who doesn’t snip).

The main problem is that Mail’s reply Applescript command has buggy side-effects:

tell application "Mail"
    set sel to the selected messages of the front message viewer
    set repl to reply (first item of sel)
    set repl_contents to the content of repl
end tell

Two reply windows are opened, only one of which is the actual reply. More often as not, the message repl is the other one, which is simply an empty Mail message. To add insult to injury, the empty reply requires a save/discard confirmation when the window is closed, whereas the actual reply lets you close its window (and destroy its content) with nary a warning in sight.

Finally, adding to reply the boolean without opening window doesn’t do what it claims.

I’ll probably adapt Gruber’s script, in the end, to do what I want. But this stuff is supposed to be quick and easy — and it’s not.

Update: this seems to have been fixed in Mac OS X 10.5.3; it's necessary to call `reply (first item of sel) with opening window` to get the reply window to appear.

A nice script I use

Okay, I don’t want to complain too much — when it works, Applescript can make life much easier and I bug report because I care. Now I’d like to share a script, Next-message.scpt, that I use many times in Mail on a daily basis (with the help of FastScripts to assign it the convenient keyboard shortcut ⌘\ ).

This script exists to make it easy to jump to the next message when you’re not using Mail’s three-paned interface (I greatly prefer having to open the message in a new window). To quote from the blurb at the top of the script:

This script is designed to open the next message in a thread when Mail is used in two-paned mode. To elucidate the problem, when viewing messages in the third pane below the mailbox list of messages, the space bar does a great job of jumping to the next unread message. When the message pane is hidden and messages are opened in their own window to be viewed, there’s no way to get to the next message without switching to the message list, selecting the next message, and opening it. This script automates this process, closing the original message and placing the next message in a window of the same size, in the same location.

The script currently does not detect if the next message is part of the same thread as the current. In fact, I don’t think it’s possible within Applescript to detect that (especially as their subjects will not necessarily be the same). Besides, sometimes you want to jump to the next message even if it’s not in the same thread as the one you’re reading.

---

As soon as I can I’ll write these up formally for Apple’s bug reporter. I needed to get them off my chest before doing that, however.

In closing, I really appreciate the power that Applescript can give, especially for cross–application tasks that would be otherwise impossible to achieve. For example, running a script in TeXShop to highlight uncited references in BibDesk.

I’m happy to see even lacklustre support despite the frustrations when it doesn’t work; I hope that, over time, Applescript support improves for all Mac OS X applications.

iTunes customer service

One of the less tangible aspects of shopping online is the lack of any face-to-face contact in the inevitable case that something goes wrong. I haven’t had much experience with online shopping in general, but I have had a couple of things go wrong for me on iTunes. And I’m happy to report that, in Australia at least, their customer support is excellent.

My problems

The worst of my problems occurred quite some time ago when iTunes was periodically crashing on me. Not really sure how or why, and iTunes these days is fairly reliable, but back then it was rather a pain in the ass. Playing music over wireless was fraught with embarrassment (“aren’t Apple products supposed to just work?”), and buying music online a risky business. Once or twice, iTunes crashed midway through an iTunes download and a song or two from the purchased album was lost in the æther. (Usually this problem can be fixed with the Store > Check for Purchases… menu item — but not in this particular case.)

Another time, I simply bought the wrong album, due to the ridiculous setup where iTunes will often sell both an AU$18 basic album as well as an AU$22-ish album with music videos or live or bonus tracks — generally I buy the more expensive version, but in this case the link from the iTunes main page was for the basic version and I bought it before checking for the other.

Finally, just the other day I bought the “iTunes Live” Nick Cave and the Bad Seeds EP and found that the last track ended abruptly, mid-chorus, at 5:13. Clearly something had gone wrong with the encoding of this track, and the one review of that album mentioned the anomaly in rather negative terms.

Reporting those problems

In each case, the response from Apple was swift and appropriate. I had to look around for a little while before I worked out how to report a problem. Recently, Apple’s been sending email receipts on all purchases, and these emails make the “Report a Problem” links rather more prominent. Through iTunes, however, here’s how you do it. In your iTunes account, access your purchase history:

You can then select any of your purchases with the little circled arrows:

Thus, each item that passes through your iTunes account can be separately reported upon.

Apple’s response

As previously mentioned, I have been completely satisfied with Apple’s response for each of the small number of problems I’ve had over the last few years. After a very short interval and despite the very brief exchange of words on both sides, I’ve always received a full “refund” to fix the problem by re-downloading the content. (As you would expect considering the cost to them is negligible, and you get to keep what you originally purchased, so it’s more of a “credit” than a “refund”. Whatever.) Apple claims to reply within 24 hours, and I think that’s about right (the most recent one certainly was). It even only took them a couple of days to fix the clipped Nick Cave track, restoring the missing ninety-odd seconds.

To conclude, how they cope with failure is a pretty important measure of the customer service of a business. Any misstep could result in alienating their very customers, especially when the business is as faceless as the iTunes store. (I wonder if this sort of thing can be fixed in the bricks’n’mortar Apple Stores in the U.S.) Disregard for now the causes of the problems that I had, which could probably be blamed in various measures on iTunes itself — that’s a rant for another time. In my own experience, iTunes’ customer service is very satisfactory and reassures me against any further problems down the road.

Make (in)visible Applescripts

John Gruber’s latest fireball discusses invisibility in Mac OS X. He rightly comments that using the SetFile command line utility (which is bundled with the Developer Tools) is probably not that convenient when dealing with the visibility of items in the Finder.

For simple cases, however, I find the use of programs like “Super Get Info” to be overkill to an extent. Many years ago, I wrote two Applescripts for the exact purpose of using SetFile in a user-friendly way in the Finder.

The first, Make-invisible.scpt, is pretty simple; just select the items you want made invisible and run the script.

The second, Make-visible.scpt, obviously can’t be used by first selecting the invisible items! On run, it will display a list of currently invisible items in the frontmost folder window, from which you can select items to make visible.

To use these, you’ll want to use either the system-wide Applescript menu bar, Red Sweater Software’s FastScripts, Waffle Software’s ThisService, or something else again.

So, there it is.

---

One thing I just noticed is that the admin privileges no longer work;

do shell script … with administrator privileges

is failing with

Finder got an error: A privilege violation occurred.

Uh, isn’t that the sort of thing with administrator privileges is supposed to avoid? Oh well — I don’t have time to debug this (in my experience, Applescript support from Apple products tends to be a minefield of poorly tested functionality literally riddled with bugs) so if anyone can help with this I’d be greatly appreciative.

Update: this error comes about because the do shell script (with admin privileges) is situated inside the tell application "Finder" scope. Please find new versions of the scripts that fix this error in the links above.

Useless proposal #1

This is an idea that requires way too much engineering, but I wish it could happen: How cool would it be if Mac OS X had a concept of “subscribed RSS feeds”, so that no matter which browser or feedreader you used, viewing a site’s webpage would not offer you the “subscribe” link if you already were indeed subscribed to it.

At present this would require browsers parsing the formats of whichever feedreader the user was using, which is clearly a rather unscalable approach. If all feedreaders used a common format file (ahem, not OPML) then this would be a lot easier :)

Twitterrific notes

I’ve been using Twitterrific for a while now as my Twitter client. There’s no huge reason, really, that the web interface isn’t just fine, but a dedicated client is nice for a few reasons, such as: polling for updates, albeit bad for productivity; shortcuts for replying; a more compact interface; and so on.

I don’t have time to write extensively about any of my wish-list, so a bulleted list will have to do. Here are a few of features that, individually or together, could make Twitterrific even better:

• Own posts are automatically marked as “read”.
• “Favourited” tweets are indicated visually (or at the very least the action of favourite-ing them is indicated; I’ve got many favourite posts by mistake trying to hit CMD-2 to reply and missing).
• Last read message is remembered so that relaunching Twitterrific doesn’t result in 40-odd unread tweets. (Alternatively, simply zero-ing the unread counter on launch.)
• On that note, it would be even better if it could track back through the pages of unread tweets until it found where I was up to; currently when I wake up my ’puter in the morning there’ll be way more tweets that I’ve missed than Twitterrific gives me.
• The input text box grows with my text rather than fixed to a certain height.
• Less UI preferences. You guys are good designers! No need to ask us if the window should have a drop shadow or not.
• Auto tinyurl (or snurl, or …) of pasted links.
• Auto-expanding tinyurl-ed links.
• Auto-completion of followers’ handles when manually typing replies to them (say there aren’t any of their actual tweets currently visible).
• Perhaps: ability to un-follow people.

Now, I’m sure some of these suggestions are technically unfeasible due to network latency/efficiency. But without thinking too hard about the underlying technicalities, I think it’s not a bad list. So what have I left off?

‘View as single page’

Yet another reason to love the New Yorker:

Clicking through multiple pages of a single article is one of my least favourite things on the web. I know I’m not alone in this. I don’t know why it is exactly; I think the mental hiccups that it causes impede the natural reading flow, or something along those lines.

It has always been possible to read articles in the New Yorker on a single page via their ‘Print’ version of each one. I suppose they must have realised that all of their longer articles (which can get up to, oh, eight or nine web-pages) were being read in this form because it’s clearly much more pleasant. Rather than restrict us this luxury because of lost ad impressions, they made the whole thing easier even for people who previously did not realise that you could access the single-page version.

The New Yorker is the only periodical I read. This is the kind of reason why.

Update five minutes later. It occurs to me that this is also good for the New Yorker, because people who were likely to read the single-page articles would probably also be inclined to link to them; the ‘Print’ pages lack the all important context links that keep people browsing the entirety of the website; it's therefore in their interest to provide linkable pages that do contain the rest of the auxiliary content (“Subscribe for just 85¢ an issue” possibly being the big one). The fact of their acting as capitalists bothers me not one whit; I'm even gratified by it. (I’d rather them be pragmatists that stay in business.) Because, after all, they could be like all of those other websites that don’t allow you to view their articles in a single page.

iPod timezones

With great fanfare I’d like to report one of the bugs fixed in the latest iPod firmware update. Since, you know, no-one seems to know what they are (fourth dot point).

Back in 2003 when I first started earning money, I saved for a few months and bought the brand-spanking new 12 inch PowerBook and 3G iPod. This was the first iPod, if you recall, that introduced the touch sensitive buttons and that was actually quite small. The iPod that really gathered the momentum on Apple’s success with the product since. Before then it was a cool gadget only used by a select few. By the time the 4G iPod came around, white earbuds were popping up all over the place.

I digress. Does anyone remember the popping bug that plagued the 3G iPod initially after its release? It was fairly surreptitious but annoying once you noticed it; a faint click whenever you skipped or moved between tracks. It was sorted in relatively short order (the buzz about this bug on the internet was, as always, ridiculously over the top), but clearly the iPod firmware guys had their hands full at that stage, because they unfortunately forgot little old Adelaide when building their list of timezones. Obviously iPod owners in South Australia are a fairly niche market, all things considered. But how hard is it to get GMT+9.5 in that little list? And how could you possibly omit it in the first place?

I dutifully filed my bug and long ago forgot about it. Let’s face it; the iPod wasn’t exactly man’s best organisational friend. I certainly wasn’t using it to check up on my calendar when my phone could do the same as well as add new events.

But Apple didn’t forget about me, and a couple of days ago I received the blissful line in an emailed reply:

We believe this issue has been addressed in the latest iPod update (version 1.3).

Five years might be a long time to wait for alarms that go off at the correct time and appointments that aren’t half an hour out, but it’s nice to know that sometimes they do listen.

Leopard bugs: Finder symlinks

Here’s a Finder window in Mac OS X showing an alias and a symlink, respectively, to a file:

See the problem? (The image might be being cut off on the right.) The symlink is being displayed as if it were a folder, with the triangle on the right of its name. Obviously it’s not a folder, so that triangle is a big fat bug. Bug #5789538, to be precise.

Digital music

News over the last little while included the staggering (to me) nugget that Apple is now the number two music retailer in America. It’s pretty inconceivable how much music this actually is, and it’s pretty damn impressive given that Apple’s only been in the music business for pretty much bang on five years.

Credit being given where it is due, I do believe that Apple has done extremely well at executing an idea that, before them, really wasn’t feasible given the restrictions of the music industry.

Michael Gartenberg’s reaction:

The question is can anyone overtake them? Or even come close?

DRM or lack thereof is not the issue that will change the game here. It’s either going to be another device that can drive consumers elsewhere (devices still drive consumers to the stores and services, not the other way around) or a totally game changing experience that re-defines how music is purchased and consumed.

Apple has clearly managed to reach a demographic with iTunes that is not particularly tech-savvy in that no-one really cares about the DRM that is being served up. For all of the noise against Apple for the low-quality and DRM-crippled files they sell, it’s worth remembering that they were the first to get unencumbered MP3s sold through a major label.

(The irony of Apple lock-in due to the labels’ demand of DRM is sweet, all the more so for it convinced the labels to drop the DRM in the first place. Online video will hopefully follow the same path, but if the future turns out to be in video rental I guess it’s not such an important point.)

Amongst those music purchasers who are both aware of DRM and leery of buying into it, the newly-constructed Amazon store seems to have gained a fair bit of mindshare. EMusic was always the crowd favourite (and online store #2 after iTunes) but against Amazon it’s hard to imagine how it can retain that lead. The big question is: after Apple finally re-negotiates with the labels to get DRM-free music across the board, will Amazon’s store retain its popularity?

Here’s where a critique of iTunes itself comes in. iTunes, as a browsing and discovering online store, is pretty woeful. If I know what I want, buying music is easy. Too easy, even. The emails I receive from Apple about new releases on the iTunes store being particularly effective of keeping my in the buying cycle.

But in terms of discovering new music in the first place, iTunes is really nothing more than a spreadsheet that plays music, in the insightful words of Ian Rogers. But do mainstream customers care? iTunes isn’t much worse than most media players around the place. Could it be better? God yes. But is it good enough? Unfortunately yes. Here’s to some vision inside Apple to improve it like they’ve improved that product that actually made them all this money: the iPod. No-one’s come close, because it’s improved at such a rate that the competitors are playing catch-up half the time.

So what about the question “Can anyone come close?” ? It’s hard to imagine in the near-to-medium future.

I originally thought that the “subscription music” model sounded pretty convincing on paper. Literally all music (that has been licensed online) unrestrictedly available to listen whenever you like? What’s not to like? Well, a monthly fee, I guess. If you buy less than one album a month that you’ll seriously be interested in an listen to, well, forever, then paying a monthly fee isn’t really worth your while. Especially when your music goes kaput when you stop paying your fees. Over a five year period you’re better off buying your music outright (for some definition of “buying” and “outright”). Broadly speaking.

I don’t really have a closing argument to all of this. I’m strongly in favour of buying digital things. Particularly ones that don’t lock me in so that five years later I’ve got gigabytes of encrypted junk that is no longer playable. Music is crossing into that sweet spot and Apple’s in a damn good position to sell yet more and more of it. Hopefully things just get better here on in.

Brain numbers

I’m fascinated by reading about the brain in abstract terms. Here’s a new article in The New Yorker by Jim Holt that takes a broad look at the research being done by Stanislas Dehaene in Paris. He takes high resolution 3D scans of peoples brains while they’re thinking about or doing things to try and understand how our mind works.

This might seem like madness: “well, I know the left side of my brain is responsible for jumping” (say). But by isolating separate thought processes and functions to separate brain areas, you can gauge the limits of certain types of thinking.

The aforementioned article discusses numbers in this context: turns out that there’re neurons in the brain that fire specifically to recognise groups of objects in numbers of up to about five. Any more than that and you need to count the objects individually before you can know how many there are.

Here’s a result that spins me out:

A few years ago, while analyzing an experiment on number comparisons, Dehaene noticed that subjects performed better with large numbers if they held the response key in their right hand but did better with small numbers if they held the response key in their left hand. Strangely, if the subjects were made to cross their hands, the effect was reversed. The actual hand used to make the response was, it seemed, irrelevant; it was space itself that the subjects unconsciously associated with larger or smaller numbers. […] He even suspects that this may be why travellers get disoriented entering Terminal 2 of Paris’s Charles de Gaulle Airport, where small-numbered gates are on the right and large-numbered gates are on the left.

Say what? What implications does this have for other cultures who write and do maths in other directions? What implications does it for how we read a number like “728456” where the smallest number is on the right? Could we suddenly become better at doing maths by hand if we reversed our number system?

And speaking of being better at maths (there are tangential parts of the article that discuss the immensely better mathematics teaching programs in Asian compared to the western world), I am absolutely stunned by this:

Chinese, by contrast, is simplicity itself; its number syntax perfectly mirrors the base-ten form of Arabic numerals, with a minimum of terms. Consequently, the average Chinese four-year-old can count up to forty, whereas American children of the same age struggle to get to fifteen. And the advantages extend to adults. Because Chinese number words are so brief—they take less than a quarter of a second to say, on average, compared with a third of a second for English—the average Chinese speaker has a memory span of nine digits, versus seven digits for English speakers. (Speakers of the marvellously efficient Cantonese dialect, common in Hong Kong, can juggle ten digits in active memory.)

If this is true (and the result is logical to me), then why on earth haven’t we invented new words for our numbers? In a bit of a coincidence, I’ve been thinking recently how inefficiently I count numbers in my head and lazily trying to improve how I do that. I thought the inefficiency of my technique was verbally thinking each number as it passed, which is extra slow in the teens and seventies. My plan was to try and simply visualise the numerals in my head ticking past and not say them at all; I found I could actually do it for small stretches of numbers but I’d quickly fall back on my old techniques. Does everyone count in their head by thinking of the actual words? (I probably should have mentioned by now that the article says that yes, this is the case; and furthermore, you always use the language you were taught to count in originally. Large numbers and multiplication are stored in memory, apparently, as language strings.)

Of course, this is all for “average” humans; it sounds like the experiments that have shown these results are only just getting off the ground and it would be interesting to see what things look like for autistic mathematicians (not to mention magnetic field-induced temporary autism).

Interesting stuff.

---

“one, two, tee, for, fev, six, sen, ate, nen”

“one tee + ate fev = nen ate”

Mac security

Another day, another computer security rant and rebuttal. Here’s a recent piece over at MacUser by Dan Moren.

Now, don’t let it be said that I disagree with the article in general. This is gold:

Okay, if an instant message window pops up on your computer, with a screenname you’ve never seen, asks for your Social Security Number and you give it to them, then frankly you didn’t deserve that identity in the first place.

But I feel Dan goes a little overboard here in his refutal of whatever some jackass is saying:

Mac users need security software, too. Oh, I know: Mac lovers will respond to this statement by puffing up their chests, raising their chins and sniffing, “Ha, my Mac always has been and always will be virus free. I don’t need no stinking security software.”

Who are these people? Where does one find them? Maybe it’s those same people who go to oxygen bars and drink fancy bottled waters and have weekend quail-shooting parties before jetting off to some balmy Caribbean island where they play shuffleboard and laugh about how they don’t need security software.

Okay, sure. The article is good. Make sure to teach the kids not to let in Trojan horsies. And that paragraph above made my giggle a bit. But you know freaking what? My Mac always has been and always will be virus free. I don’t need no stinking security software.