I wasn’t surprised to find that my receiver takes a second or so to sync up to a new digital audio stream; this is not an unusual flaw. I was surprised that Airport Express isn’t sending a continuous audio signal to the receiver when it’s active, and that iTunes sends each song in a playlist as a separate digital stream.

Net result? My Kenwood VR-407 loses the first second or so of every song unless I set iTunes’ crossfade option to at least four seconds. With that, the first song is still chopped, but as long as I don’t change tracks manually very often, the majority are ok.

This would be acceptable as a short-term workaround, even though I despise crossfade, except that the device isn’t terribly stable. Several times in the first hour, the audio stream simply locked up and had to be restarted.

Bottom line, until there are updates for both iTunes and Airport Express, it won’t get much use at my house. I could switch the connection to analog to avoid the crossfade, but that won’t do anything about the unstable connection.

The iTunes Music Store has put up free audiobooks of the DNC speeches. Knock yourself out.

No, really.

It lasted about fifteen minutes on my laptop. Why? First, because the supplied widgets were primarily designed to be pretty. The weather and calendar widgets are translucent; you can’t make them not be translucent, even if you have wallpaper on your screen that makes them unreadable. The (thankfully not translucent) to-do list doesn’t allow you to edit in-place; anything you want to do with a to-do item involves popping up a bog-standard Mac dialog box and clicking “Okay”, which pretty much renders it useless as a “quick! write that down!” tool or organizing tool. Most of the other standard widgets are similarly long on chrome and short on function, to the point that I have trouble remembering them mere minutes after trying them out.

I was already underwhelmed by the contents of their user-submitted widget gallery, so I’m left with no possible reason to purchase this product, nor can I imagine it ever becoming a significant commercial success. This renders the whole “Apple stole our idea” and “Dashboard was designed to be a Konfabulator killer” claims completely moot. Konfabulator in its current form could never have made its way onto the desktops of a significant percentage of Mac users; it’s just not that interesting.

Will there be a lot of high-chrome, low-content Dashboard gadgets? Sure; as the man said, 90% of everything is crap. The difference is that you don’t need to learn a proprietary development environment to create gadgets for Dashboard. Hell, you don’t even need to learn JavaScript; Dashboard will cheerfully run Flash applications with a trivial DHTML wrapper. You can also embed Java applications, QuickTime videos, etc.

Konfabulator can’t do any of that.

If, for instance, I wanted to build a nice kana/kanji chart around this remarkable collection of QuickTime videos that demonstrate the correct stroke order for the entire hiragana and katakana syllabaries as well as all 1,945 Jōyō kanji, I could (and likely will, if only for my personal use), because a Dashboard gadget is just a web page, and web pages can have embedded QuickTime videos.

The closest thing they’ve got over in Konfab-land is the new Kanji-A-Day widget, which uses /usr/bin/curl to scrape a Japanese web site and import its content into a (cough) pretty window. Maybe that’s the one that will justify the $25 they want for the product…

I’m not really a programmer; I’ve been a Perl hacker since ’88, though, after discovering v1.010 and asking Larry Wall where the rest of the patches were (his reply: “wait a week for 2.0”). If I’m anything, I’m a toolsmith; I mostly write small programs to solve specific problems, and usually avoid touching large projects unless they’re horribly broken in a way that affects me, and no one else can be persuaded to fix them on my schedule.

So what does this have to do with learning Japanese? Everything. I’m in the early stages of a self-study course (the well-regarded Rosetta Stone software; “ask me how to defeat their must-insert-CD-to-run copy-protection”), and authorities agree that you must learn to read using the two phonetic alphabets, Hiragana (ひらがな, used for native Japanese words) and Katakana (カタカナ, used for foreign words). A course that’s taught using Rōmaji (phonetic transcriptions using roman characters) gives you habits that will have no value in real life; Rōmaji is not used for much in Japan.

So how do you learn two complete sets of 46 symbols plus their variations and combinations, as well as their correct pronunciations? Flashcards!

The best software I’ve found for this is a Classic-only Mac application called Kana Lab (link goes direct to download), which has a lot of options for introducing the character sets, and includes recordings of a native speaker pronouncing each one. I’ve also stumbled across a number of Java and JavaScript kana flashcards, but the only one that stood out was LanguageBug, which works on Java cellphones (including my new Motorola v600).

When the misconceptions about Apple’s upcoming Dashboard feature in OS X 10.4 were cleared up (sorry, Konfabulator, it will kill your product not by being a clone, but simply by being better), I acquired a copy of the beta (why, yes, I am a paid-up member of the Apple Developer Connection) and took a look, with the goal of building a functional, flexible flashcard gadget.

Unfortunately, I’ve spent the past few years stubbornly refusing to learn JavaScript and how it’s used to manipulate HTML using the DOM, so I had to go through a little remedial course. I stopped at a Barnes & Noble on Sunday afternoon and picked up the O’Reilly JavaScript Pocket Reference and started hacking out a DHTML flashcard set, using Safari 1.2 under Panther as the platform.

Note: TextEdit and Safari do not a great DHTML IDE make. It worked, but it wasn’t fast or pretty, especially for someone who was new to JavaScript and still making stupid coding errors.

I got it working Tuesday morning, finished off the configuration form Wednesday afternoon, and squashed a few annoying bugs Wednesday night. Somewhere in there I went to work. If you’re running Safari, you can try it out here; I’ve made no attempt to cater to non-W3C DOM models, so it won’t work in Explorer or Mozilla.

There’s a lot more it could do, but right now you can select which character sets to compare, which subsets of them to include in the quiz, and you can make your guesses either by clicking with the mouse or pressing the 1-4 keys on the keyboard. I’ve deliberately kept the visual design simple, not just because I’m not a graphic designer, but also to show how Apple’s use of DHTML as the basis for gadgets makes it possible for any experienced web designer to come in and supply the chrome.

So what does it take to turn my little DHTML web page into a Dashboard gadget?

more...

After hearing all the whining about another example of how Apple is killing off third-party developers by “shamelessly copying Konfabulator” (which can fairly be described as Super Desk Accessory Toolkit, an update of the classic Mac OS utilities), I decided to take a look at this amazing product that I’d somehow overlooked.

Um, where’s the fire? I just went through the gallery of Konfabulator widgets, and far too many of them are like these two:

A small handful of them were useful, but while some of Apple’s sample gadgets from the Tiger beta are badly designed, at least they’re good for something. In fifteen minutes of browsing, I couldn’t find a single Konfabulator widget that was interesting enough to encourage me to buy and install their application. Indeed, the trite “get the original Dashboard now” page at their site showcases a bunch of gaudy widgets that I simply don’t want on my computer.

There’s a fugly clock that slavishly emulates a low-resolution, low-legibility digital clock; another one that slavishly emulates the limitations of an old analog wristwatch; a color-coded pseudo-3D to-do list that’s covered with redundant buttons; a Google searchbar that looks like it’s supposed to be inserted somewhere; and a user-hostile iTunes controller (okay, Apple screwed that one up, too). And how do you gain access to these screen toys? Through a pull-down menu, just like the old Apple desk accessories.

Designing your own means learning to use their XML layout schema. Designing a Dashboard gadget, on the other hand, is as easy as laying out a web page, because it is a web page, rendered with the same engine as Safari. In fact, you can create it with your favorite text editor and graphics program, leveraging your knowledge of HTML and CSS.

This Mac security hole has been all over the web recently. The thing that makes it dangerous is that it’s ridiculously easy to exploit. The thing that makes it annoying is that anyone on the development team should have seen it coming a mile away, especially given the many well-publicized scripting exploits in Windows software.

How did it happen? WebCore. In an effort to produce a common HTML/HTTP library for all applications, functionality that used to be restricted to the Help tool was suddenly embedded in everything that retrieved or displayed web pages. Apple’s pervasive AppleScript support completes the circle.

Ask not what you can do with scriptable applications; ask rather what scriptable applications can do to you…

Update: The official fix is available via Software Update.

Update: You still need to turn off the Open “safe” files after downloading option in Safari, because disk: URLs still work, and mounted disk images can include auto-execute programs. Yes, there are two stupid features in the previous sentence.

Mostly bugfixes and minor tweaks. Still need third-party freeware for many import/export tasks.

Update: It’s being reported that 1.1 silently fixed a bug that prevented use of free third-party instruments.

For some time now, I’ve been mildly annoyed by Safari’s “Open in tabs” option at the bottom of every menu entry in the Bookmarks Bar; it’s too easy to select by accident with certain pointing devices. This is second only to my annoyance that the Bookmarks Bar doesn’t obey the same UI rules as standard Mac pulldown menus.

Well, I’m still stuck with the second one, but I just discovered that someone on the development team recognized that it was a little too easy to wipe out all of your open tabs and replace them with thirty new ones. It’s not obvious, but immediately after selecting “Open in tabs”, the back button acts as an undo.