How To Deal With The Spatial Paradigm
PostThis writes that there's been "a lot of talk about Gnome's spatial Nautilus lately and so Christian Paratschek puts everything into perspective weighing in the pros and cons of this particular user interface paradigm. In any case, there are always alternatives."
Is how NOT to deal with SPatial paradigm..
m e. htm
Apple's Quicktime is a great (horrible) example.
http://homepage.mac.com/bradster/iarchitect/qti
Care of the "Interface Hall of Shame"
It should point here.
Direct-access user interfaces, like Apple's Spotlight, Black Tree Software's QuickSilver, ObjectiveDevelopment's LaunchBar (all for Mac OS X) and Candy Labs' AppRocket (for Windows), are the future of file management interfaces.
The spacial vs. browser-style debate isn't worth winning, because either way you're sticking to metadata-ignorant heirarchies that humans just aren't very good at dealing with beyond a certain point.
As far as I am concerned file managers like Nautilus, Windows, and Mac OSX can put as much effert into their work as they please, but they can never get the functionability of a "two plane" file manager like Gentoo:
http://www.obsession.se/gento o
There are many of this sort, but Gentoo is by far the best. Sadly doesn't the author like GTK2, so he won't port it=(
... and it's sweet desktop (notice the unix screenshots?) metaphor. Spatial is good, but it's counterpart is metadata driven virtual folders; extended attributes aren't only for acls... A userland daemon, fam monitoring and a berkleydb hanging around. It's not that the pieces aren't there...
Mi domando chi à il mandante di tutte le cazzate che faccio - Altan
..is all the hooplah over this issue. It's not like this is a new paradigm. Even windows used to be spatial - win95 before they came up with the whole browser integration thing.
:) To me, "mv * ../foo" requires less effort than the GUI equivalent.
:) Side-by-side lists of files, each navigational, but a lot more useful that the web-browser-like navigation. People are forgetting that we used to use file managers to manage the files and only sometimes open them - most of the time files were opened from the program that we were wanting to use them in. When was the last time you launched an application and THEN opend the file with the 'Open' option in the File menu?
In Linux, I still prefer to use the command line. I'm just a keyboard whore.
My first real computer (trs-80's don't count) was an Amiga and it used a spatial interface - tho I preferred to use Directory Opus, an ol' midnight commander style file manager, for my hardcore file management.
Even on my dad's DOS machine, I primarily used Stereo Shell (another of the MC style).
So, whatever happened to that paradigm?
-Major Kusanagi, Section 9
It's bad enough to change default behavior on a user (at least it was during a major release) but all they had to do was add a preference to "open new folders in the same window" .. the same way windows does, and a lot less people would be upset.
Personally, I think the spatial idea is pretty useful when you have multiple monitors, and lots of space to spread out the "remembered" window locations. On a single screen the benefit just isn't as big.
--Cycon
Your Brain + EEG + LEGO Robots = Brainstorms
I will start to take "spatial" interfaces seriously when "news" articles stop telling people that they are wrong for disliking it and start describing the advantages. I have yet to see an article do this.
So, I read the article. And the author makes a reasonable point about newbies being more accustomed to the spatial metaphor. I'm not going to dispute that. It might or might not be a valid claim.
The question I want to ask is: what about those of us that are NOT newbies? The author states early on that he tries to avoid anything that would expose the filesystem tree abstraction to the end user. Maybe you could argue that it is good for newbie users, maybe not. But it DEFINITELY isn't good for non-newbie users.
Look, the filesystem is a TREE. That's what it IS. Any metaphor that you try to make the filesystem fit some other pattern will only take you so far. A tree is a very nice, clean structure. A lot of its expressive power is lost when you try to impose some strange alternate metaphor on it. When you deal with the filesystem as a tree, any operation that maps well onto trees, you can map well onto filesystems. It's a powerful abstraction.
And quite frankly, don't we WANT newbies to be learning the actual behavioural properties of the tools they use, rather than an artificially constructed interface which we deem them more able to use? Won't this lead to more intelligent users?
Personally, I think it's insulting to people to say that they can't "deal" with basic abstract structures. It's not THAT complicated guys. And we're not that smart for knowing how filesystems work. MOST people in the world can grok the concept perfectly fine, you just have to teach them. Perhaps some people feel threatened by that?
I was an avid gnome user. I stopped using it once I noticed the clear trend for gnome to assume that I'm dumb. That I can't deal with certain choices - which are better made by the developers than by me. Limiting excess in choice is fine.. but there is a fine line between reasonable limits, and top-down control. I think gnome crossed the line a ways back.
Keep your spatial browser. I'll keep my trees.
-Laxitive
I dislike spatial for the same reason I hate websites that pop up new windows for every link.
...if you don't mind changing the way you have been doing everything effectively for the past decade or two. David Gelernter, in Machine Beauty , derides this situation, reminding us how bad it is to deal with "a complex or weak program that forces you to bend to its worldview instead of accomodating yours."
From the article: First, I wanna tell you what I usually do to make a computer easy and consistent to use for a newbie...
The Grim Reaper replies: Shut up, you American! You Americans, all you do is talk and talk, and say "let me tell you something," and "I just wanna say..." Well, you're dead now, so shut up!
Ahhh, I feel better now. :)
BH
Fools! They laughed at me at the Sorbonne...!
There are not many alternatives left.
If there really is a need for all these articles that explain what spatial file browsing is, how it works, and how it should be used -- then there is something seriously wrong with spatial browsing.
The ordinary tree structure has worked for millions of users, most were of them newbies when they got introduces to file browsing. I wager that there are no one (or very close to no one) who'll complain about the idea of a tree structure.
If people can use an ordinary index in a book, they can understand a tree structure. Most people will think in a manner that is similar to a tree structure; Let's see, pictures, vacation, 2003..
People like having multiple views of the same information. Why are virtual folders in e-mail applications so popular? Because they provide simple, logical views of the same date, used in different context!
Here we go AGAIN. Lets cut to the chase. Those who want to understand it, will understand it. Those who do not, will give all the reasons not to.
That's no different than the Vi vs Emacs, KDE vs Gnome, or Linux vs Windows discussions we've been having for the past couple years.
Eugenia is chubby and Greek. She likes BeOS, which is dead. Her husband is gay. She is fat. OSNews is a troll site. F* Slashdot editors for posting anything from there.
Eugenia is fat.
Just my personal opinion, but the whole reason I use a computer instead of a hundred Post-It notes lying on and around my desk is because the computer supposedly organizes things better. Now they want to have the computer deliberately and faithfully mimic desk clutter? That's so damn stupid, I want to scream.
Patrick Doyle
I mod down every jackass who puts his moderation policy in his sig. Oh, wait a sec....
*sigh* I'm getting a headache from you "I don't understand spatial" guys.
The spatial metaphor works better when it's sitting on top of a meta-rich environment. That's were the GNOME storage project comes into play. Maybe one of these days, you'll all realize that developers aren't stupid (doesn't stop you from using their software I noticed). You all chewed and spit out the Mozilla team for XUL and other decisions (Surprisingly no one left because of it). Now it's the GNOME teams turn.
The main usability gain of spatial Nautilus (and that demonstrated in the article) is having flatter trees. Your example is one where there is already a flat tree. So your example actually becomes one advocating flat trees (and therefore spatial Nautilus).
I bought a car recently. The manual contains a page of contents, which lists 5 sections. At the start of each section (within the manual) is a page of contents, which lists what I can find within the section. That is an example of a deeper tree, and that was much harder to navigate.
Spatial Nautilus will suck if you use deep trees. But you're only using deep trees now because the tools you have are suited to deep trees. It is designed for flatter (and easier to navigate, thanks to spatial memory) trees.
It's regarded as NEWS that somebody actually likes spacial browing and can find a few reasons to justify it! This article proves that spatial browing has not convinced the majority of people.
What we really need is better file metadata and indexing tools...
I have 16000 files in my documents tree... how exactly am I supposed to arrange those in a two-level directory hierarchy?
I am more comfortable with a tree-oriented system as the default, but there are times I want a new window. Both metaphors are natural and easy to comprehend. They both have their uses. I find navigation to be much easier in a tree-structure, but drag-and-drop seems to work much better in a spatial structure. Why not make it easy for me to do both? Another thread here mentions old MacOS 9 behavior of allowing either way... why shouldn't we have something like that? If I single-click, keep me in the same window. If I double-click, open up a new window. Best of both worlds, easy to use, easy to understand.
Getting tired of Slashdot... moving to Usenet comp.misc for a while.