Académique Documents
Professionnel Documents
Culture Documents
Note: This is not an existing program, neither is this a design for a theme for some
operating system. This is a concept how an intuitive operating system should behave.
One more thing: Since the file manager of my ideal OS is pretty much run-of-the-mill
otherwise, I thought I'd mention one peculiarity: To provide quick access to your
documents and programs, apart from regular folder windows, you can have "query"
windows as well as "docked" windows. The latter are probably known as "pop-up
windows" to users of MacOS 9 and earlier. They are simply file manager windows that
you can drag to the edge of your screen, where they will reduce to a "tab". Click on that
tab (or drag a file onto it) and the window will slide out, functioning just like the dock or
the task bar. The difference is that this one can contain the contents of any file manager
window, and you can drag items onto the items in the tab, e.g. to tell a compression
program what file to compress.
A query window looks just like any other file manager window that lists the contents of a
folder (aka directory) or drive. The difference being, that you can specify certain criteria
as to what files it should display. For example, you can have it display the eight most
recently used applications, or most recently used documents. Or you could have them
display all image files on your disk, or whatever.
If you combine these, you get pretty much the behaviour of the task bar or the dock: A
list of the items you're currently working with, easy for quick access. Even better, you
can have several of these, containing e.g. lists of your favorite applications for different
purposes. You'd have a "DTP dock" and a "Programming dock" and a "Drawing dock" or
whatever.
And finally, you could even have docked windows that do not slide in when unused, but
rather stay open all of the time, in their own reserved area of the screen.
Feedback
One of the biggest problems in
modern, multi-threaded OSs is that of
feedback. When you open an
application in Windows, it simply takes
a while before you actually see the
result of your action. This delay causes many users to click twice, or three times,and
they get two or three copies of the same application, or worse, file icons begin stacking
up ontheir desktop or whatever.
MacOS X is a little smarter by having application icons bounce in the dock while they are
being opened. While this is nifty, it is also quite annoying, as a similar bounce is used to
indicate when an application needs your attention. Not to mention that, after clicking
three or more applications, you start to become really seasick from all those bouncing
icons.
What is needed is a more subtle effect. In the old, mostly single-threaded days, we had
animated cursors, or a small animated cursor that was overlaid on the mouse cursor.
While this is a nice approach, we can't have the cursor constantly animating. One
solution in Unix OSs to this problem is to only animate the cursor when it is on top of the
window that is busy right now, but this again requires that users constantly swipe their
mouse over several windows to find out whether it's finished (a problem our contextual
menus will already have).
So, what we need is something more precise than just infinitely bouncing icons. Also, it
should be more subtle, and we also need something that works for any user interface
element, as users always need feedback whether a button is finished doing its thing, or
whether it's still cranking away. So, my idea is to just hijack an effect I saw in Compact
Pro, where an icon slowly inverted from the bottom up, just like a progress bar.
In principle, something like this can be done with any kind of UI element, and if we
make sure that this goes smoothly (maybe using alpha blending), and instead of
inverting an object we just tint it in a slightly darker shade, the user needs only a single
glance to know whether it's finished, while not being distracted by jumping pixels
everywhere.
Note that this darkening must be noticeably different from that performed when the
button is clicked,so the user is aware that the click was noticed by the UI, but it's still
working on the action. And this feedback should also happen for short actions, so the
user can trust the UI to always behave the same. And the darkening should really
correspond to the actual progress going on. While easy on the programmer, progress
bars and animated cursors that are kept animating by a separate thread are next to
useless for the user when trying to determine whether an application has frozen or
crashed.
2006-11-05, merged this article with the addendum.
2003-03-31, thanks to Tilman, Sam Kington, Matthew Thomas and Reinhard Auer for their input.
2002-11-16, thanks to Matt and Reinhard for their input.
Alain F. writes:
A really radical approach to revolutionizing the FILE system
would be to NOT USE FILES at all; at least from the USER's perspective.
Behind the scenes, the OS could still resort to 'files'.
These files would be indexed for quick access by the system.
User interacts with ALIASES, as many as needed, in many contexts.
Btw, my bro works for a company where the OS is natively a relational database.
Performance screams! Two orders-of-magnitude faster than file-based OS'es! :-))
But anyway, if you want to really want to go away from traditional file systems, I'd
recommend you check out Jef Raskin's Zoomable Interface. There used to be a Flash
demo of it available. If I can find a current link I'll update my blog posting about it
with the new link.
n[ate]vw writes:
Cringely is fond of saying "What goes on the Net stays on the Net" (and that may even
have come up in his interview with Brewster Kahle). Anyway, without further ado, the
second Google result for "When good interfaces go crufty":
http://web.archive.org/web/20041111085426/mpt.phrasewise.com/stories/
storyReader$374
Enjoy! (And have you found the Jef Raskin flash demo? His was an enjoyable book.)
thanks. WebArchive will at least allow me to recover that for personal use, and people
can use your link to get there. I hope Matthew will eventually put it up again on his
new blog. And yes, the Flash demo is available. Check in the archives, I've updated
the URL on the "zoomable interfaces and Jef Raskin" article.
In the case of my ideal OS, It would just be a file that gets copied when you open it,
and then you could rename it, e.g. by changing the window title, or through renaming
it in the file browser, or whatever other means is offered. That's how creating a new
file would work as well, after all.
So, templates are effectively the means by which new files are created. Every app
would include a few templates, and there'd be a smart search window that contains all
templates, and you just drag them out of there and get a new copy to work with or so.
Coffedrone writes:
While I understand this is targetted at less experienced computer users, what about
users who are familiar with keyboard shortcuts? Personally, I very rarely use my
mouse unless I'm stuck in an interface which offers no alternative (or reasonable -
tabbing between hundreds of items is not a very good way to get things done ;) )
means of navigating. Having to let go of the keyboard to grab the mouse all the time
would drive me nuts. :S
Uli Kusterer writes:
@Coffedrone: There are keyboard shortcuts in one of the menus in my mock-ups, so you
can definitely assume that I want keyboard shortcuts to work. But you've actually
pointed out a slight difficulty: A contextual menu has a built-in focus, but a keyboard
shortcut doesn't. So, keyboard users would definitely need traditional selection and focus
indicators.