Raskin zoomable desktop manager for Mac OS X
raskinformac.com
raskinformac.com
I posted a separate submission this morning but it hasn't seen any attention and I thought it would really appeal to HN's:
Window & tab switching with 'type to search' for OS X http://news.ycombinator.com/item?id=2675963
Something about how you interact with it all just doesn't feel right. I might be able to say more after I used it for a bit, but I just don't want to. The UI doesn't invite the user into interaction so much as it does gawking.
That is also "a nice experiment, but in no way useful for the day to day."
Additionally, Jef's involvement in the development of the Macintosh's user interface has been vastly overstated... mostly by himself. Evidence for this can be seen in reading his own essays which predate his 1981 "history of the Macintosh" (in the older essays, it's clear that his vision has little to do with the Macintosh at all), and online repositories of Apple stories like folklore.org where many people report that Jef had the habit of laying claim to everyone else's ideas.
Example: http://www.folklore.org/StoryView.py?story=The_Father_of_The...
The end result is basically this: everything Raskin worked on except the Mac is weird and experimental, and not practical or enjoyable.
His reputation definitely has the Halo Effect going on, but sadly, if you pay close attention, it's clear that the emperor may not be naked but he is certainly not fully clothed.
Considering Raskin's ideas about user interaction as "out there" is a matter of perspective. Touch screen interfaces that are now common today were once considered "out there". His love affair with the Canon Cat wasn't just a personal obsession. He made (what I considered to be) a group of well reasoned arguments about why it was so good based on the concepts it brought into reality. Off the top of my head I can recall automatic file saving (with no consideration to the file system) being one such argument. This feature will be shipping in the next release of OS X (Lion). If Raskin's ideas in the Humane Interface were "out there", then I take that phrase to be synonymous with "avant garde".
The zoom UI he talks about in another chapter (and what the OS X app Raskin has attempted to implement) seems like a strong candidate for a general data exploration and discovery UI. What he put forth in the book was conceptual, and no one has yet made a commercially or critically appealing implementation. That doesn't mean it won't happen. It just mean it hasn't happened.
My browser window is usually 700px or so wide which is why I encounter that particular bug all the time – especially on otherwise quite nicely designed websites. It absolutely breaks the website and sometimes makes it unreadable (try resizing the window and see what happens), forcing me to resize my browser window. Why don’t web designers like people like me who like to see more than one browser window at a time?
A design that would look good on your layout would look terrible on another user's widescreen; a design that would look good on a widescreen will look awkward, at best, on your setup.
It doesn't help that so many people are still clinging to CSS as the primary answer for this, since it is completely ill-equipped to deal with this problem.
For starters, I couldn't get it to actually pinch zoom, making it near impossible to read any file names. The scrolling itself was so fast that I found myself flying around the screen without any ability to recognize where I was or where I wanted to go. Images had a consistent and ugly black border. Files seemed to be resized and ranked without any plausible order. Loading was slow, slow, slow. There were no keyboard shortcuts to allow me to quickly flip through a row of images. The viewpoint would not stick to a column or series of images, causing me to easily lose my place. The font rendering was horrid.
I could go on...
I personally have no use for it but it certainly worked well enough.
[1]: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.89....
The previews of files are great if you work with images. Not so great for source code though.