Stripes: A Conceptual Operating System User Interface
ignorethecode.net
ignorethecode.net
That said, I love the way you can search menus, this is a feature that every toolkit should support. I don't know how long I've spent searching Gimp's erratically organised menus.
I don't see how this is innovative though, he would want to have some very convincing results from his usability tests.
Some filters and plugins might really be better if integrated into the core menus, but then you run into problems with a plugin seeming to override a core menu item (maybe this is desirable) producing a confusing interface for the user. In this regard, Gimp had taken a play from the likes of KPT, where all those cool filters were available as a separate (and guh, inconsistent) menu/UI to call them out as separate (although, in the case of KPT, it seemed to be more of a branding thing).
I think a lot of the problems stem from the need for a consistent UI being incompatible with a tool that is infinitely extendable by the user via installable plugins. You end up with something like the Windows 95 Start menu, where all vendors were effectively encouraged to put things wherever they wanted in the hope that you'd find them the easiest and/or associate the application with their brand (all Adobe products being in the Adobe subfolder, for example).
The window management concept seems very similar to recent mobile operating systems, specifically the "card" concept in Palm's webOS and the tiled window view in Nokia's Maemo 5.
It seems to me that the Stripes menu design presents too much information to be applicable to small mobile devices with low-res screens (e.g. iPhone), but it might be very effective on the new generation of mobile phones with higher screen resolutions (Motorola Droid/Milestone, Nokia N900).
I guess you won't drag and drop elements from one window to the other with such a GUI.