499 words
Having been mostly offline recently and a whopping 250 unread posts in NetNewsWire, just a few unrelated little remarks.
don’t care how well-structured and semantic your markup is; if it doesn’t look good on screen, you’re discriminating against people who can’t afford screen readers, and that ain’t right.
6JLNZTV9GP6WZGT
in the cap of a Coke bottle. Seems to be uningenious some rip off of that iTunes/Pepsi thing. With the added benefit of being limited to one platform. So, on a first-come first-served basis, I'll trade that code for an iTunes code or simply the promise to get a cool song for it and posting the title as a comment…
re:Markdown. I started to use Textile in MovableType but some of the tricks to avoid problems with XHTML strict were kinda cumbersome — handling of blockquotes and so forth. There were a few niggles here and there, and I find this new script effortless.
You’re right about conversion to another CMS, but since the script can be used as a ‘service’, in OS X, it should be possible to store entries to overcome this eventuality. I think it sounds straight-forward, and I agree that it would be alot of work after a couple of years worth of stuff. I suppose it comes down to an adoption among a broad range of systems, and that it remains persistent.
Well, most things computer related aren’t very difficult and ‘straightforward’ in some way.
But doing all those ‘straightforward’ things can be very tiring and even nerve-wrecking if there is software around that makes things harder.
The thought of having entries in both HTML and some other formats in MT gives me a bad feeling - so I’d need to convert everything now. Which I won’t do. Besides, I suppose that I use some strange HTML at times which might make a potentially automatic conversion choke… and then I have to worry again about how to fix all that.
Re: Quicksilver API for bibtex database.
I really want this too. I asked the LaunchBar people about it a while back and they said they had it planned, but you know how that goes. Hopefully some competition in the launcher space will be good.
You can bet that as soon as an API for these shows up, I’ll be thinking of ways to support it in BibDesk.
Michael,
that sounds great. Having support from application authors will certainly encourage the launchbar people.
I saw there was a new beta version of LaunchBar out today. It seems to be going much more towards interfacing with other applications (iTunes, Unix commands, AppleScripts). So getting an API for this may not be too faint a hope.
These are exciting days for quick launch utilities on the Mac. Just gives us a couple of tough choices as well.
One little thing both of those launchers still lack, IMO, is the ability to select an application and open its application bundle in a single step.
For the curious ones among us, this (and the fact that the f*cking Finder defaults to icon view to show the ‘Contents’ folder) is still a very annoying procedure.