The Next Computer Interface 336
BoarderPhreak was among the several readers who pointed out "an interesting article on the various alternatives to storing your files using a 'desktop' metaphor" at TechReview.com. "New styles like time-indexing, 3D sphere ala SGI's file manager, and even a 3D virtual 'task gallery' from Microsoft. Screenshots available in the article." All of these have been floating around for a while; hopefully soon some radically different interfaces will actually gain widespread acceptance.
Great site for this stuff (Score:5, Interesting)
--LP
The users control the interface. (Score:3, Interesting)
Re:The users control the interface. (Score:2, Insightful)
perhaps a key that represents the desktops confiuration.. it might be too big to remember though. *shrugs*
What I Use For General Navigation Stuff (Score:4, Interesting)
Re:What I Use For General Navigation Stuff (Score:4, Informative)
After looking through the site, it reminds me a bit of Ted Nelson's ZigZag [xanadu.com], only with a much prettier user interface.
ZigZag basically lets you set up arbitrary "axes" of meaning and drop nodes on them. Any node can contain anything, and be a member of any number of axes. All axes are orthogonal to all other axes. The user interface lets you move along any axis from any node. Thus, information is locally coherent but, if you step back, it's a rat's nest.
For example, for organizing things on your computer, you might create an axis named "Games," and link Quake, Starcraft, and Solitaire to it. Solitaire is published by Micros~1, so you might also set up a Micros~1 axis, which contains Solitaire, IE, Word, Excel, Outlook, etc. Solitaire would be a member of both "Games" and "Micros~1", but not of the "Network-aware" axis, which would contain Quake, Starcraft, IE, Outlook, etc.
ZigZag is very primitive right now, but the concept is very intriguing. Written in Perl and runs under Linux. Check it out.
Schwab
Re:What I Use For General Navigation Stuff (Score:2)
Sometimes it's frustrating how many people keep reinventing the wheel over and over again, except they usually do it worse the second time.
Re:What I Use For General Navigation Stuff (Score:2)
I've been using The Brain, which treats documents, programs, shortcuts, program groups, etc as "thoughts" which you can link to any other thought.
I saw this ages ago and wanted a nice linux interface back then... or at least the algorithms for how they moved back and forth, very appealing.
Yikes!!! (Score:2, Funny)
Run for your lives!!! =)
I thought it meant "next" as in NeXT ... (Score:2)
It should have meant NeXT... (Score:2)
Plus, will all the cool effects of windows zooming on to the screen (this is a new one), and windows zooming off the screen, I the interface looks bad-ass and I look productive.
Hehe, fooled them didn't I?
-Peter
3D, voice and why its NOT a good idea... (Score:5, Insightful)
All of these gimmicks tend to miss out on the fact that a simple linear system is much better for _people_ than the fancy gimmicks which developers think are cool. Voice interaction is a classic example of something that can be thought of as "cool" until you have an open plan office with 30 people talking at their computers.
3D is another dead end. IBM's Home project found that people would "lose" things in a 3D environment and in fact the visual cues of the 2D desktop were better suited to the task.
At the end of the day the mantra should be KISS. These break that mantra and add very little except cool graphics. It looks nice but doesn't function well. An everyday example of why simple is better are the icons used to denote things like "radiation", "poison" etc etc they don't actually represent the thing themselves but provide a simple shorthand for the thing. This simplification makes them much better at describing and classifying than attempting a "realistic" presentation.
Good examples of 2D simple interfaces are things like Google. Why would 3D make Google better ? It wouldn't.
Pretty != better. More Gimmicks != simpler
KISS
Re:3D, voice and why its NOT a good idea... (Score:2, Funny)
It is 3D. How do you call it when you hide your pr0n search behind a slashdot window? Background. That's 3d.
Re:3D, voice and why its NOT a good idea... (Score:2)
Why don't you guys (and the genius moderator) do a little web search for "time fourth dimension" and read what the current theories are...
(mumble, mumble, pissant moderators, mumble, pet theory, mumble, mumble, closet Luddites)
Re:3D, voice and why its NOT a good idea... (Score:2)
Rubbish. They would point it out as an oversimplification of a purely theoretical concept.
VI (Score:5, Interesting)
I agree about offices, the technology to make voice interfaces work is here today, but the applications is not, however but Voice Interfaces offers a lot of potential for much more personal environments, like the car home & SOHO.
VI offers a number of advantages over conventional interfaces, biomentric security, easy of use & accessability, even for your technophobic mother/granny.
Imagine a home entertainment gateway accessed by voice, no worries about little Johnny snooping your adult PIN. The inherent Biometric security, will make no difference, if he overhears your PIN.
Imagine re-tuning you IP Radio Alarm, by voice, without opening your eyes.
Imagine switching off your security alarm, by saying 'Hello House', and then following up it up with the query "Messages?" without having to log in and remember your password.
Or change channels without having to figure out which of those six seperate remote you need to use, simply by saying 'TV, select channel 4', or 'TV, News' or any number of other scenarios.
I think the killer application for VI is Home Automation.
Re:VI (Score:2)
And if you think VI offers advantages, you should see EMACS!
Bah dah, boom... Thank you... Thank you very much...
Solutions (Score:2)
A Protocol based solution, might require you to complete a challenge, i.e.
Computer say 'Blue' You say 'Sky'
Computer says 'Red' You say 'October'
It could require you to name the content.
It is also possible to distigush natural voice from even high quality recordings, in the same way you can tell the difference between a CD and a live performance/gig.
Re:VI (Score:2)
It defies me to believe that anybody could feel that typing was easier than talking, I'm a trained touch typist yet I can talk at 3-4 time my rate of typing.
I would argue it's easier because verbalisation of abstract ideas (Talking) is a more natural communication method. The only communications methods that predate verbal communication are the non-verbal forms such as body language, and biological forms such as touch/smell. Typing is a derivative of writing, which is a derivative of speech and consequently is probably our least developed (evolved) communications skill. I accept that pointing [a mouse] is an effective technique, but easier than talking ? I don't think so.
The levels of ambiguity are simple astounding.
Ambiguity is a characteristic of all communication forms, however speaking is less ambiguous than typing as witnessed by all the flame wars that could have been avoid by addition of tone of voice tags such as .
The ambiguity of saying 'head to the top of the street and turn right' is massively less than pointing down the street followed by point right. Pointing (a mouse or a finger) fails this ambiguity test, indeed it's is also more ambiguous than speech, but this does not preclude using mouse or finger, within a GUI.
classic example "I had to reinstall all of my software because I told my computer to delete windows. Hey! It did it again!"
I'm talking about a Voice Interface paradigm, not a specific implementation. By various clicks or typing various command you can do the same with Windows, Linux or OS, so what stops it happening by accident ? The UI Design!
The specific usage protocols required to avoid this type of issue in a VI are best left as an exercise for the reader.
All the 'flaws' you point out are flaws in the specific implementations you suggest, they are not flaws in the concept.
Or to use another metaphor, just because I feel that Windows is a bloated piece of junk, does not invalidate the concept of GUI or just because I hate vi, does not invalidate the command line prompt.
In the end, I think it all boils down to the fact that humans often get confused by voice comunicaton
Perhaps you do, but I usually say what I mean, and mean what I say
However seriously most 'ambiguities' are actually errors of omission, and a VI can resolve an ambiguities' in the same way a GUI does, via an error, or even better suited to the paradigm a challenge. 'Did you mean X or Y'.
Re:Google is simple, desktops are not (Score:2, Informative)
Re:Google is simple, desktops are not (Score:2, Informative)
PC/human interaction is vastly different from real-world physical interactions in many ways. Trying to force them into being analogous is often a
The future lies in places like the Xerox PARC of old, and in usability labs, where people can simply brainstorm interface ideas, and fitness/evolution will take care of the rest.
Note, however, that there _isn't_ a single solution. People have many different prefered ways of arranging data not just in their head, but externally too.
THL.
Re:Google is simple, desktops are not (Score:2)
3D Doesn't Work So Well... (Score:2)
In that context, 3D and a voice interface both make sense.
Voice recognition in the office (Score:4, Insightful)
I don't understand slashdotters sometimes.
Have you ever been in a callcentre? Okay, they're generally not exactly open plan, but they don't give the drones huge walls, and there's way more than 30 of them in there.
What they do give the drones are headset mics.
This isn't rocket science, folks. Kate Bush, not exactly a hardcore techie, came up with wireless mics in the '70s (well okay she forced her engineer boyfriend to come up with them, but you know how it goes :)
Wireless headsets. That's how you do voice recognition in an office.
Re:3D, voice and why its NOT a good idea... (Score:2, Informative)
the thing is...... (Score:3, Insightful)
a) a tried and tested system which works, and is already fairly* well established in the minds of billions of well-organised people, and was evolved over hundreds of years of trial and error by people who actually NEEDED to organise stuff
b) outmoded and ready for the trash heap.
take your pick.
I applaud the effort to find something better, but really, i think "natural selection" would have found a better real-world parallel if it existed.
relationships between files in the structure is a brilliant idea, but that's just metadata and cross-referencing.
- says the man with the cluttered desk - at least my machines don't have virtual beer bottles leaving ringmarks on my HTML documents.
*irony
Desktop metaphors were supposed to scale (Score:2)
Of the options listed in the article, Scopeware is the only one that looks remotely intuitive to me -- and that's only because it's basically a search engine for your computer. Call it a diary metaphor all you like, but it's basically a combination of two things: the "Recent Documents" history that my browser uses, and a database-driven search engine that indexes every document as I create or modify it. Sounds a lot like my web browser to me. Nothing too revolutionary there, it seems to me.
command line (Score:2)
(Meta: Slashdot problems) (Score:2)
You weren't the only one; there seemed to be some sort of glitch last night.
Anyone Use VRML? (Score:2, Insightful)
The major problem is that the computer is a 2D display device, so whenever moving to a 3D representaion, you are really getting a 2D representation of a 3D represenation of information, with only 2D tools to use to get at that info (i.e. mouse, keyboard).
I tried to use a 3D file manager for about a week, once, and found it unintuitive, silly, and a general pain to try to use. Why? Because I don;t want to wander through virtual galleries of items before finding the one I want: I've got a memory/filing system that makes it easier for the 2D computer system I use.
Unless the peripherals and OSes become 3D oriented, I don;t really see that changing. The desktop metaphor works for the type of information we store on our computers.
Replacing the Desktop methaphor (Score:2, Interesting)
why don't we replace the usual desktop metaphor by a game metaphor?
Just imagine: To delete a file you don't have to drag it to the trashbin but you can shoot at it. And depending on the type of weapon you are using there is a chance to recover the file if you (of course accidentially) hit the wrong file...
From my point of view a computer was designed to take work away from the user and not to put extra work on him by applying some stupid metaphors. Every metaphor that requires interaction like mouse movement and klicking is wasting the users time because its hard to make it automatically. But that's what the computer should do, doing the jobs automatically. I don't enjoy a copy job that requires me to push and pull a mouse and gives me as a sort of reward a stupid animation of flying papers.
Re:Replacing the Desktop methaphor (Score:2)
Look for PS-doom or daemon doom or whatever it's called today.. on the net. the monsters in the room are your daemons and by using a weapon from 1-9 when you shoot the "demon" you issue that process that kill command.
the biggest problem with it was that if you didnt hit the daemon you were aiming for the dang things would start fighting and daemons killing daemons makes a hell-uva(tm) mess out of your linux box.
I think it was mentioned on slashdot back a few years.
Hmmm... (Score:2)
Picture this:
You've got a large stone wall with ~65,000 entrances, a machine gun, boiling oil and a six-pack of beer.
Sounds like a lot more fun than how I spent the last few days...
When you get a really solid firewall going, you can pick off valid packets just for fun...
Re:Replacing the Desktop methaphor (Score:2)
You're missing the point of "metaphors." The idea is that things are made more intuitive (more like something that's already known). A good metaphor is certainly *not* wasting the user's time. The example you cite (dragging a file to the recycle bin and getting a picture of papers being thrown out) is meant to give the user a concrete picture of what's going on inside her computer box. It's surely much easier to remember than "rm -rf ", and easier to grasp than a screenful of "Deleting " scrolling faster than any human can hope to process (or worse, getting zero feedback because you didn't use verbose). I prefer the command line for deleting things anyways, but more because the pretty pictures are wasting precious, precious clock cycles.
Look at how many metaphors even a command-liner is being subject to. You've got the keyboard, which is an input metaphor. If you wanted a non-metaphorical interface, you'd have a '1' key, a '0' key, and nothing else. Emacs performs the same sort of abstraction when you read a file off of it. In reality, ASCII itself is simply a metaphor for the English alphabet, designed to save us from having to deal with 1's and 0's directly -- and before you argue, remember that this is exactly what the first computer builders had to do.
Not all metaphors are equally valuable or useful. So take whatever metaphor suits you best. But until you've mastered two-key, don't expect anyone to believe that you're living some sort of 1337, metaphor-free existence.
Getting seasick? (Score:3, Interesting)
Re:Getting seasick? (Score:2)
It's natural for people to feel disoriented when introduced to a new viewing environment, such as staring at a computer all day, FPS games, 3D interfaces, or 3D goggles. However, at least as far as computer monitors and FPS games have shown, this disorientation does not last, and as these things become ubiquitous enough to be shown on television in things like TV shows about video games or computers, people that are freshly introduced to these things don't even feel disorientation the first time they use them.
The disorientation people feel when using things like 3D interfaces is nothing more than the shock of literally seeing things in a different way. It is not indicative of anything inherent in the interface itself.
Re:Getting seasick? (Score:2)
My guess is that those people who suffered from nausea, etc, don't play first person shooters any more-- thus, few complaints.
I think we can all agree that when it comes to 2D interfaces, clarity, speed, and refresh rate are all very important. However, in the 3D world, artifacts are much more common. Card have gotten much more refined since the days of my Trident 975AGP (A real POS, btw, compared to most if not all of the cards of its time), which habitually stuttered, rendered textures incorrectly, and generally detracted from my gaming experience, but some modern cards (Radeon 7500/8500) still sacrifice accuracy for the sake of framerate. Even the latest GForce isn't 100% accurate.
Until 3D quality is indistinguishable from today's 2D quality, the use of 3D windows for most work will provide an inferior user experience.
Some ideas (Score:3, Interesting)
One of the main problems today is that the OS doesn't make the best use of the information available to it. The OS can know the file type, the application(s) associated to those files, when the file was created etc. but in general, it doesn't do much with that information. Sure, if you double-click on your file, it can find & launch the application associated to the file type, but you're still left with the problem of finding that file.
My own proposal would be to make better use of the file information that the OS has available to it. Its theory, but basically you place a database layer over the filesystem. We should also make use of MIME types for each file, and create a hierachical directory structure, one for each MIME type inside the users "home" directory. As a simple example, you may have something like:
user1/
files/
image/
jp eg/
pn g/
x- bmp/
audio/
x- mp3/
Now we have this, we can put the information we have to good use. Whenever a file is created, rather than asking the user for a directory and a filename, we ask them for a description of the file. Create the file in whichever directory suits the files MIME type, with a system generated filename, and add an entry for the file into the database which is layered above the FS. The record should include the users long description, type, creation date etc.
Now when the user wants to find & open a file, they can easily find their file by e.g the decription, using a wildcard if they wish. Or the creation date, using a range is they want to. The major advantage is that they don't need to navigate through a heirachical directory structure, nor do they need to remember what type of file their looking for, as the OS can present all of the files that the user can open as a flat list in the dialog.
O.K, it's a clumsy description, but the basic premise is that a) The OS can handle placing the file on the FS instead of forcing the user to decide & b) We know have a flat list of files to manage, instead of a possibly very complex heirachical tree. We do retain the advantages of the hierachical tree for the filesystem, however.
Re:Some ideas (Score:4, Interesting)
1. Computers organise things hierachically because we like it that way. We haven't been conditioned into it by computers. Remember the game where you pick a number between 1 and 100 and somebody tells you higher or lower? Remember how much easier it was when you learned to start in the middle? It's the nature of things.
2. 98% of the time, you don't need to "search", if you organise things properly. No matter how great the search is, it's always going to be more efficient if you stick things in relevant folders (/documents/biz/2000-2001/invoice110.doc)
Personally, I think the biggest problem with the wimp interface is modal windows (this should not happen ever ever ever amen), and a decent way to keep track of more than 10 open windows/programs.
Didn't se an old one mentioned (Score:2)
files were organized as cities on a 3d landscape, files that were not for you (permissions set so you couldnt access them) would run away from your avatar and other file types would quiver, grow, etc...
Directories or cities that were off limits would grow walls as you approached and system files (Like logs would change color depending on errors contained inside.) would change according to what was happening.
I remember seeing this on television back in the early 90's but I cannot find it anywhere on MIT's webservers. anyone know if it's stored in the archives? or maybe moved from MIT?
This is dumb. (Score:3, Insightful)
These people should really learn that the desktop is the best way to handle a two dimensional computing environment. The only possible ways to make the current computer interface better is to either add new hardware to interact with the computer (3D goggles, hand sensors, microphone, what have you) or to tweak the current desktop interface to make it just a tiny bit better.
These people are trying to reinvent the wheel by making it a square or a triangle. My wheels are fine the way they are, thank you very much.
Not another one! (Score:4, Interesting)
And yet none of them have taken off. Why's that? Maybe (heretical thought!) it's because the current model actually works quite well for most people.
I don't want a system where the computer organises things for me. I can organise them better myself. (Occasionally I might lose something, but probably less often than if the computer was filing stuff for me. Anyway, we have good 'find' tools on Windows and Unix.)
I don't want a 3-D interface. It's much harder to visualise and navigate than a 2-D one. (A set of 2-D interfaces, as in Mozilla's tabbed browsing or many window managers' virtual desktops, is good. This is perhaps one of the real UI advances in recent years. Windows could do with virtual desktops.)
The article says: "Conceivably, an inference engine can be made so intelligent that [...] machines would automatically present information to you as you need it." Well, maybe when that's true I'll change my mind.
Re:Not another one! (Score:2)
-generation- of users to grow up with the new GUI.
Real People are going to hate any interface if it's not 'like Windows' and it'll bomb horribly. Witness every new-and-superior-but-different technology from MS BOB to the Amiga to electric cars for proof. Incremental change is about all that'll be acceptable.
Re:Not another one! (Score:2)
wrong concepts (Score:3, Interesting)
My point is that these attempts at deciding the future of GUI are pathetic as they don't even take the current GUI's limitation in consideration:
(Note: if you don't agree with the following then you had to adapt yourself to these. Take anybody who doesn't use computers and just observe him.)
Future GUI concepts should take the problem the reverse way:
I am actually working on a GUI concept which will *not* be 3D. This will be Open Sourced.
good use for 3d (Score:2)
For file management, maybe as was mentioned above, using icons/objects that vary in virtual size with the actual size of the file, maybe with a hyperbolic file manager.
3D will really come in useful in more futuristic applications, mostly dealing with non-local entities... talking to people, viewing data on other servers, etc. I think that entertainment and communication will be the two largest areas to be able to exploit 3D interfaces (that means *with* VR glasses and various sensors and such)
Re:good use for 3d (Score:2)
really, except for specialized things like CAM and 3D modelling, it already IS communication and entertainment (gaming right now) that are the leaders in use of 3D
Task oriented computing (Score:2, Interesting)
But that's not the reason of this post.
the real reason of this post is to say that the solution to the desktop mess may already exist, living right in our POCKETS... yes, I am talking about PalmOS.
Palm os is task oriented. you want to type a text ? fire the text editor. all your texts will be registered as belonging to that app, and will be an inseparable part of it.
Want to draw a picture ? same thing.
The job of organizing files by date, size, content, name, category, etc will be handled by THE APPLICATION, in a way that best matches the type of aplication you're using. Keep in mind that organizing AutoCAD drawings is completelly diferent than organizing texts or bitmap images.
Re:Task oriented computing (Score:2)
Perhaps more on-the-fly arbitrary ways of grouping the data would be good... by date, file type and so on already exist... good metadata for each file would allow more flexible grouping methods.
I dunno (Score:3, Insightful)
Anyways, I think the problem is this. We all have a shitload of files - on my 100gb drive, I have 85,120 files taking up about 80GB. This is my "extra storage" drive, I got 45,920 files on my C drive. Ok, perhaps I'm extreme, I have a shitload (about 40,000) of text files, books in pdf, etc etc..
Now, how the hell are you going to make it easy for me, or anyone, to access a good 120,000 files, preferably within less than 5 user interactions (clicks, speaking something, etc..)
OK, a new gui, cool, but if it is going to succeed it will essentially be a sytem based on "Organisational units that hold things" i.e. Folders / directories / objects.
A Chronological system won't work for a situation like this, it'd take too much of a mental effort -answer this - what did you have for dinner 1 week ago? I think that would be a perfect question, because things on the computer tend to be "routine" - did I work on this or this? It doesn't take a psyc major to tell you that humans suck at remembering what happened in the past.
With a hierarchical structure, it is painfully easy, and it scales well.
i.e.
e:\asdf (ok, ok, its easy to type and a throw-back to my 286 days, wee didnt have no stinkeen gooey)
e:\asdf\music
e:\asdf\music\Rock
e:\asdf\music\Rock\Prodigy - minefields.mp3
Moreover you can actually communicate the location to someone else, not "a file from sometime last week", or "the file in the Blue gallery on the right wall in the clipboard". Ever try to explain over the phone how to get to your house? Ever get lost becuase the directions sucked?
I can't argue with the article too much though - clippy the annoying mother fucker gets bashed on
Re:I dunno (Score:2)
I almost always know about when I last worked on something. I once (when I got it working) found MS Outlooks 'Journal' feature to be very useful. It's keep track of when you accessed MS documents on a calendar timeline. Even if I did not know an absolute date I'd know something like 'Oh yeah, I create that document a few days after I create that spreadsheet'. Time is very important metadata and in the current hierarchical metaphor it's relatively difficult to use.
e:\asdf (ok, ok, its easy to type and a throw-back to my 286 days, wee didnt have no stinkeen gooey) e:\asdf\music e:\asdf\music\Rock e:\asdf\music\Rock\Prodigy - minefields.mp3
Yeah, that works, but you are essentially building meta data into the directory structure. Seems to me we have better ways of creating and using metadata. Many of your MP3s might already have the metadata you encoded in the directory structure, stored internally in the file. It seems a waste to duplicate that data.
Your method also can fail if you forget how you organize things, or perhaps slip up and misorganize, or work in a common directory structure you share with others who might think a little differently. 'Gee did my boss put that project plan in "IT\Projects\ERP\New" or "ERP\New Projects"?' Anyone who has worked on a shared lan drive knows what I am talking about.
With some sort of unified meta data scheme I could just search for a project document with key words, 'ERP Project', created in the last few days and most likely find the file my boss had just created for me.
There is a definite need for creating a universally recognized way of storing file meta data that is not specific to a given file system or file format. It need not be complex or 3D, it just needs to allow me to easily enter and search on meta data and quickly create customized views of my files based on the meta data I have entered.
Examples: "All word documents sorted by name" "All documents created in the last week" "All excel spreadsheets for project "Jupiter" sorted by size" "All documents about dogs"
You can do some of this today with content indexing and local search tools, but think about expanding this to an entire enterprise, encompassing all data on a network. The location of the data becomes irrelevant. The idea of a 'share' becomes meaningless. You just submit a file with appropriate meta data to the operating system and it worries about the details of physical storage.
-josh
Re:I dunno (Score:2)
Yeah, that works, but you are essentially building meta data into the directory structure. Seems to me we have better ways of creating and using metadata. Many of your MP3s might already have the metadata you encoded in the directory structure, stored internally in the file. It seems a waste to duplicate that data.
I would go even farther and say that ID3 tags are themselves a waste, as they lock the metadata into the file in a proprietary format instead of making it available for wider adoption using some generalized mechanism. Of course, it's the poor metadata handling of the current crop of file managers that's really to blame.
Your method also can fail if you forget how you organize things, or perhaps slip up and misorganize, or work in a common directory structure you share with others who might think a little differently. 'Gee did my boss put that project plan in "IT\Projects\ERP\New" or "ERP\New Projects"?' Anyone who has worked on a shared lan drive knows what I am talking about.
Exactly why imposing a hierarchy on the metadata is a mistake, as I pointed out when this [slashdot.org] came up. The original poster probably has only one file on his entire system called "minefields.mp3", yet he has to dig down through the hierarchy to get to it. A system with proper metadata handling will essentially do that digging for you, and I look forward to the day users can take advantage of that. I'm doing it today, myself, because that's just the type of software I'm working on.
There is a definite need for creating a universally recognized way of storing file meta data that is not specific to a given file system or file format. It need not be complex or 3D, it just needs to allow me to easily enter and search on meta data and quickly create customized views of my files based on the meta data I have entered.
My software is being developed on Mac OS X and so far a modified browser/column view seems to work just fine for navigation. The major interface element that is needed is a text entry field (shades of the command line) for times when it's faster/easier to essentially search for an object instead of navigating to it.
Storing the data is another issue, and we've already gone through 3 different methods of persistence. The object layer hasn't changed, however, and the metadata is still easily represented as named and unnamed attribute values.
Examples: "All word documents sorted by name" "All documents created in the last week" "All excel spreadsheets for project "Jupiter" sorted by size" "All documents about dogs"
That's really just scratching the surface based on current metadata handling and indexing techniques. In a world where structured metadata isn't locked into the file itself, it would be possible to do even more advanced queries like "all invoices that are overdue" or "all movies shorter than 1 minute" or "songs where Sting is an artist". The limits become the limits you're willing to represent in metadata and not the limits of the system itself. Computers are just at the edge of where they need to be for this kind of advanced processing, but I predict that in 5 years the idea of a hierarchical file system will seem quaint.
Imagine this... (Score:4, Insightful)
Incidently, I am this }{ close to losing the GUI alltogethor. With the fantastic (but slightly unwiedly)mplayer [mplayerhq.hu], and Q3 now working from the CLI, I see little purpose (personally) for those quaint little GUIs.
A mouse is what you play Quake with.
The Bob Metaphor (Score:2)
Could it be that Mrs. Gates (former Bob project leader) is using her influence to get a second chance to screw-up?
Any ideas for a better 'Clippy' (Score:4, Interesting)
The article mentions how annoying Clippy is, but says that MS researchers still think a 'helpful' interface is a good idea if done properly. Can anybody think of a good way to do this without it becoming annoying?
One thing that I really hate about those little characters is that they get in the way and take control of the computer away from me. But what if a little box on the task bar showed the three 'most likely' things you wanted to do and you could activate them (complete with little wizards if the task is complex) by clicking?
Re:Any ideas for a better 'Clippy' (Score:2)
As an interesting sidenote, I'd say a slight majority of my users here actually like having the assistant available and visible (the cat is the most popular one, an informal walking-around survey shows). They ignore it most of the time, but people seem to like watching it cavort on screen. We turn it off by default when we do system builds, so users have to actually turn it on - many do so.
The reason that's interesting is because most of "us" (the
Re:Any ideas for a better 'Clippy' (Score:2)
Do know if the users who start out liking the little beast start to get annoyed with it later on?
If so, then one could imagine a Clippy that not only learns your habits, but also notices when you're likely to be annoyed with it and hides.
Yes, take away it's pop-up nature. (Score:2)
Instead of using up valuable screen real estate, though, I'd make it an ever-present part of the right-click menu.
Jon Acheson
Re:Need a hammer? (Score:2)
Heh heh. I noticed that too. Too bad I can't really claim credit for my sig :-).
zooming windows (Score:2)
OK, so I use a text console most of the time, easier on the eyes, etc, but when I do use a GUI (one does what one must, when supporting CAD users) I sometimes wish I could zoom windows in or out. You know, use shift-scrollwheel or something to zoom the active window out so it takes up less space, the fonts are smaller, etc, but you can still see it. (Perhaps two modes, one which resizes only the borders as is already possible, the other also zooms the window contents....) This wouldn't replace the 'normal size', 'maximise', and 'minimise' commands, of course - in fact, 'normal size' would be even more useful than it is at present, as it would snap back to normal zoom factor.
Shouldn't be all that hard - scalable fonts were probably the trickiest bit and they've been around a long time now. An application would have the option of scaling or not scaling other elements of a window.
SGI almost did this - many of their IRIX desktop apps let you zoom stuff in and out by dragging a graphical "volume control" thing on the left side of the window. I believe this was primarily their way of showing off their vector-based icons. But this didn't resize the window itself, only its contents. And those were the days before mouse wheels.
Another idea.. (Score:2)
The best sys admin interface (Score:2)
Argh! Just say NO to alternative interfaces. (Score:2)
There was this supposedly state of the art revolutionary 3D Virtual Reality immersive file system they were using (enough mid-90's buzzwords in there for you?)
So anyway, there's Michael Douglas and he's looking for a file. He's on some techno-trampoline with clunky VR goggles on. They show his visual perspective, and he's jogging down what appears to be a library hallway, looking at virtual books on the shelves. After several minutes of jogging he finds the book he wants, selects it from the virtual bookshelf, and opens it to find the file he wants.
That scene always cracked me up. What are these people thinking? We have computers to store information so we don't HAVE to jog down hallways to locate a book.
I'm not saying that the interfaces in the article were nearly as convoluted as that, but researchers keep beating up on the desktop for no apparently good reason. People make all kinds of emotional claims about how much the desktop sucks, but every system that gets proposed (for example, this weird-ass filecard system) appear to suck more.
Whatever. As long as I can still get to a command prompt, I'll live.
Mindmapping desktop (Score:2, Interesting)
However, the file-cabinet view of the desktop have lots of nice alternatives. I really want a system that treats my desktop like a giant mind-map. Every project that I work on, and all the little notes that I find myself writing all the time would fit great in a mindmap structure. Also having the entire map in a zoomable format would be a better way to use the background than just putting the standard Manga/Astronomy/Softcore/Whatever-floats-your-boat pic there.
Furthermore such a desktop would interface nicely with remembrance agents [mit.edu]. Imagine having an interactive system (perhaps integrated in emacs, like the one in MIT) that monitors what you write and suggests related nodes, that you have written before.
And it doesn't stop there! If you have a little checkbox for 'public' on each node/note, a mindmap maps well to a html-site (like MindMan [mindman.com] does), so you could easily transform a set of loose thoughts on a subject to something that the entire world can benefit from. The RA could perhaps also interface with something like Everything [everything2.com] and the mindmap desktop could have an easy function for uploading nodes/groups of nodes to the community. The entire hivemind of such a network would have an enormous potential.
Got interesting incoming mail? Tag it with a few keywords and give it a place in the hierarchy and the RA will pop it up when you need it again. The mindmap structure is immensely powerful. Got a whole slew of files in a programming project? Using the same system as you do for all the rest of your documents, you could easily arrange them so as to get a nice visual overview of their interdependence.
Can you tell that I've been thinking about implementing a desktop (probably in scheme for that schweet scriptability) that does something like this, for a while? ;)
Re:Mindmapping desktop (Score:2)
Can't speak for anyone else, but you lost me here. Please, for the love of all humanity, if you do this, use a normal language so that we ALL can script it?!?!? please?!?!?!
Just one catch... (Score:3, Informative)
Although the idea of chronological storage is intriguing, and will work well for small groups of files, it breaks down completely once the user starts manipulating many files. This can be mitigated by storing them hierarchically, but this then ceases to offer much advantage over a desktop list view that's sorted reverse-chronologically by date.
3-D has two main disadvantages, both stemming from this notion of "space" as a way of managing files, as opposed to a flat "surface". The first is speed. Because there is more area (or, to be more accurate, volume) to navigate, the user has to spend more time looking for stuff. Second, as the article points out, things become easier to lose in 3-D space. You can alleviate some of this if you add the notion of "hallways" and "rooms" in which to organize things, but if you do, then you're still thinking in hierarchical terms, and that puts you right back on the Desktop.
Then, there's that funky sphere idea. Somewhat less of a problem than true 3-D, because you're still dealing with only one surface rather than a space Less easy to lose things. However, with all the spinning and zooming that you'd need to do, you lose speed, big time.
Microsoft's task-oriented stuff just doesn't work out. It's well-suited to carrying out actions, but not for organizing files. You just get dumped onto the Desktop.
It's true that the desktop metaphor has its flaws. In fact, truth be told, it's pretty bad. But it's like democracy in that regard: the only thing worse is everything else we've come up with so far.
NEXT had a great interface (Score:2)
But the interface lives on as "Afterstep"!!
Long live Afterstep (untill something better comes along...)
3D Metaphor is wrong tangent (Score:2, Informative)
Currently, disk contents are arranged in a nested heirarchy. This fits nicely into a desktop-folder-file metaphor. Each file may be enclosed in one folder (which may be enclosed in more folders) which is contained by the desktop. A 1-1-...-1 relationship. Aliases are currently used to sidestep this structure and randomly access files outside of this struture.
It seems to me the next step is a relational file system. In this system, the physical location of a file is mostly irrelevant. Just like in a relational database, all files may be displayed by search criteria. An OS would have default views which would show "all user created data", "all system applications", etc. Each view is merely a database report which could be further refined.
A XML-ish standard structure for embedding attributes about each file (metadata) would be very useful. File type, creator, preferred editor, preferred viewer, and other user defined attributes, as well as some content-based indexing would make this possible. Users could have their own file system views based on search criteria of file attributes. It would then be trivial to view "all html documents containing meeting notes from last week" (files matching 3 attributes).
Files would no longer merely be viewable by heirarchial location, although you could still view by directory structure for maintenance, housekeeping, and organization.
Window management is another big deal I'd like to resolve. Layering of windows places the burden of managing the display on the user. Why can't my OS handle much of that for me?
I applied at Apple for a senior UI design position several years prior to OSX , presented many of these ideas in the interview, and was told, in essence, they were more interested in animated widgets than reinventing the desktop. Now Apple has undermined use of metadata in OSX. It's sad to see a company once so keen in user interface to take a step backward, instead of some forward direction.
It's also sad to read about such crap as in this article being presented as the next step. Geesh. What a maroon! I've been hearing about 3D interfaces since at least 1990 and have yet to see one with any promise. At best they are eye candy. At worst, they are a counter-intuitive kludge from forcing a concept onto functional need. (Ahem. It flows the other way, fellas...)
-c!
The concept of "files" is the problem... (Score:3, Interesting)
When I write something in a notebook I don't have to "save" it, or give a special name etc.
For example, I've used a wordprocessor, called "YeahWrite", that does away with files. You simply open new pages and write. Everything is automatically saved and you pages are arranged in time order. This works great for people who are not computer expersts and are not interested in learning about computers.
In "The Humane Interface" Jef Raskin describes an interface that's based on plain text. There are no documents, just one big text stream that contains separators. The user interface just manipulates this text.
Finally, do these usibility experts actually watch people work? One of the most useful UI features is the idea of "Virtual Screens" (as implemented by Unix window managers). Each virtual screen keeps the context of a particular task and makes it easy for me to switch between them. Why hasn't this become a standard feature of Windows is beyond me!?
Re:The concept of "files" is the problem... (Score:2)
Re:The concept of "files" is the problem... (Score:2)
Re: text only interfaces - you should read Raskin's book. He describes the interface and the experiments they performed using it. It was quite eye opening for me. BTW, why do you think that Emacs still has such a large following - after all it's just a text interface. Check Raskin's pages [jefraskin.com] out.
P.S. My notebooks are just piled up on my desk in time order (most recent on top). :-)
Re:The concept of "files" is the problem... (Score:2)
Furthurmore, this document-less interface... how do I go back to a previousd docu^D^D^D^D separator? I key some reverse-search command and type... what? A file name? How is that different?
But virtual screens do rule.
Re:The concept of "files" is the problem... (Score:2)
That's why I use a Wiki [whttp] to keep my notes on my computer. It's a simple interface, I can rearrange it as I like and I can search it.
Re:The concept of "files" is the problem... (Score:2)
That seems easy enough. But what if I write a note that's related to a software project I'm working on, and I want to store in a place related to the place of my source code? What if I have some notes, written at completely unrelated times together with some drawings or anything and want to pack it all together and mail it to someone?
I realize that the current hierarchical system of directories and files might not be the best possible way of organizing things, but at least it allows me to store related stuff together in the same place.
Re:The concept of "files" is the problem... (Score:2)
Try working in SmallTalk (try Squeak for an open source implementation) and see how code and comments are organized. SmallTalk work is done inside it's own environment, without the need to step out to the base O/S file system. In fact Squeak has been used as the O/S on some small devices.
Re:The concept of "files" is the problem... (Score:2)
It's really not a standard feature of 'X' either. If you want virtual desktops on windoze, just replace the interface with something like this [stardock.com]
User interfaces can only go so far... (Score:4, Insightful)
This is especially obvious to anyone who's worked in teams of more than, ooh, one person who have had to share a single file structure. What one person perceives as a logical structure (/docs/reports/outgoing/date) another would view as being totally redundant (/docs/date/out/reports). You end up with a compromise that suits neither party, and by the time you move up to >100 people sharing a file structure you're in real trouble...
You also get into real trouble when a document has to exist in more than one place within the heirarchy. F'rinstance documents that need to be organised by Date or by Customer or by Author or by Cost code etc etc.
Shortcuts and/or logical links can help some of these problems, but they're both pretty messy solutions.
I have seen, and worked with, several database driven document management systems which show a lot of promise. Whether this is the way forward is a debatable point, certainly having to host a database complicates the implementation for the average desktop user.
Until some form of document management can be incorporated into the operating system all that a new GUI can do is to further obscure the core organisation.
What I want is a document management system which allows me to look at my files in the way that I choose, allows my co-workers to look at the same files in the way that they choose and hides the files completely from people who have no interest in them. The organisation of the files on disk shouldn't be something that I (as a user) have to even care about - slap them in a flat structure for all I care.
Fer [insert deity here] sake, if we were designing a file system from the ground up we wouldn't seriously contemplate a heirarchical model for more than five minutes. There must be a better way!
Cheers
Chris
Re:User interfaces can only go so far... (Score:2)
Re:User interfaces can only go so far... (Score:2)
FYI, I was pointed to an experimental file system based on MySQL engine. Wich may be an overkill. What we need is not to store file system _contents _in a database(like), but only the file system _indexes_ (i.e the set of directory tables).
Pity none of us is a kernel developer (or you are?).
No, there must be organization first! (Score:2)
OK, maybe it's my inner German getting out, but really in situations like this what you need is to set some basic ground rules in place at the beginning and make people stick by them.
So you decide on a few basic rules and STICK TO THEM. Ex: doc directories organized by workgroup, project, release version, type of document, and containing the date in the file name. Otherwise, you quickly get chaos, which people try to fix with search engines, and you wind up with Microsoft.com.
For a search engine approach to ever work, you have to have the system of organization in place first BEFORE the documents are created, so that people can tag the docs with the right search terms so that people can find them later on.
This is why you can find things in libraries or, to a lesser extent, on USENET. There is a system in place that makes at least some sense, and forces people to categorize docs as they are created (or as they enter the system from outside).
You can't throw the docs in an unorganized pile and have your computer magically make sense of it, since your computer CANNOT READ FOR CONTENT. Word searches don't work if the keywords appear in every document (see microsoft.com). You can have people go in afterwards and read for content and tag for organization, but that's a losing battle, because the doc specialists are always outnumbered 10 to 1 or worse, and the docs are constantly changing and being replaced.
Putting everything into a database without figuring out a working system of organization only makes things worse, because not only are the docs still unorganized, they're also hidden away from the user and "owned" by whoever is maintaining the database, and that person is probably a DBA, not a librarian. Even if they are a librarian, you still have the problem that they're outnumbered 100 to 1 and didn't create the docs. Plus, this approach tends to give you lots of smaller databases that can't be searched globally. And, it's much more expensive and more prone to breakage than the original document directories were.
The same document should NEVER be stored in more than one place, or else how do you know which copy is the most up to date? I would accept having more than one way to find a document as being a good thing, though, as long as the underlying organizational structure is put in place first, and both ways to find the document actually WORK. Two broken search engines are not the equivalent of one good hierarchy, IMHO.
Jon Acheson
Messy? (Score:2)
In fact, my desktop's backdrop image is a picture piles of paper, magazines, and coffee rings... it's a photo of my desk.
Hmmm.... time for that spring-cleaning I keep procrastinating about...
Microsoft BOB... (Score:2)
And then there was that insane navigation screen used in Jurassic Park. The girl managed to use it easily enough in the movie, but it didn't look like the easiest system in the world.
In short - there have been plenty of attempts to come up with something better than the desktop, but although they're all very pretty and innovative, most of them have been pretty useless to actually use.
Why? (Score:3, Insightful)
why not all of them? (Score:2)
frozen 17 years ago (Score:2)
in the early 1980s. However as much I admire
Apple in bringing the Desktop metaphor (developed at Xerox) to the masses, it had the counter effect of freezing this metaphor. Especially when MicroSoft with the inventive creativity of a dead fish copied it and put it on every desktop.
Temporal and social context are the key (Score:2)
Dual advantages of heirarchical filesystems (Score:2)
2) *Hiding* files is also easy. If your workstation/home PC is not secure, it's dead easy to conceal your {warez/pr0n/job application letters to competing companies} from your {significant other/boss} by burying them in a folder where nobody would think to look for them (eg. "c:\program files\the microsoft network\setup files"). I know that "security through obscurity" doesn't really work, but I suspect this system works very well for many thousands of people.
XYZ is dead (Score:4, Insightful)
Whenever I hear someone* declare something to be dead, it's a good indication that it'll be around for another hundred years or so. Yeah, the desktop metaphor is dead, just like paper is dead.
* Someone refers to the researcher who's inevitably researching what he thinks will supercede what he's declaring dead.
Re:XYZ is dead (Score:2)
The revolutionary human-computer interface ... (Score:2)
Just read a couple of White Papers from software vendors - next version is always announced as supporting "Read My Mind Computing"
Searching for metaphors is ass-backwards. (Score:2)
There are two aspect to the desktop metaphor: the overlaying of documents on the window (very good -- we should keep this), and the hierarchical storage of documents (very weak). The hierarchical storage of documents is precisely how you are not supposed to handle physical files. Physical files are supposed to be organized one of two ways: chronologically or alphabetically. There is a one to one correspodence between hanging folders and inside folders which immediately tells you whether a file is missing. Files are never ever nested. This is a kind of discipline which is imposed to make filing systems comprehensible between people; they also reflect physical limitations (a file can't be in two places at once; a file can refer to another file but won't necessarily help you find it).
The very image of "files" being stored in a "tree" is so incongrous it is funny.
The storage of files in an unique tree shaped hieararchy is itself a metaphor; we all know that on disk storage looks nothing like this, but we accept the hiearchical structure unhesitatingly. This is an obstacle in people cooperating with each other, except when certain hiearchies are so engrained they are second nature (e.g.
I think a good system would allow users to do the following (concepts poorly supported currently are italicized):
The more I think of it, the better it would be to organize files around the needs of project and task management. I was going to add above things like "prioritize" files because people often do -- segregate their "hot" files from the rest. However , this doesn't really make sense. It's a task that is priortized; when that task is back burnered, then all the files associated with that task lose their hot status. In a sense, this complements a post I made earlier in an article about "groupware". Groupware shouldn't just be e-mail or e-mail and calendaring. It should be about managing the flow of information between people. In some sense the same things are needed by an indivdual working alone. The big problem is that they way I think about things (and how they need to be organized) may change as I change my focus between tasks, or as I change my thinking over time.
I think a system that supports these kinds of tasks could be done with a special shell or even a web client, with metadata stored in hidden files or in a database. Ideally, we would have a file system with extensible and well indexed metadata, version tracking and cryptographic signatures.
More pointless daydreaming... (Score:2)
There are just so many things wrong with this statement... Do you want "radically different interfaces" just for the sake of being different, or do you want them to be functional too? And of course, "radically different" and "widespread acceptance" very rarely go together. Most people accept what is familiar, so none of these new interfaces are going to take off overnight. While we're at it though, why don't we have radically different automobile interfaces, or radically different food packaging interfaces, or radically different building access interfaces?
The whole point of an interface is that it is accessible. The key here is to make it work for the users and not make the users work for it. When you start having the interface share some of the work of organizing files (as Scopeware does), you may take some work away from the user, but now you've essentially got a co-worker you need to deal with whenever you want a file. Imagine two people sharing a cubicle (yes, this is a desktop metaphor for a non-desktop metaphor replacing a desktop metaphor), using the same files and reference materials. Even if one is only tasked with organizing everything, there's still a gap between the brain of the user and the brain of the organizer. If there isn't a perfect match between how the two think, you'll hit an endless cycle of problems. The only solution is to either force the user to conform to the organizer, or customize the organizer to the exact specifications of the user. Neither is likely to be better than just giving the user the task of organizer.
All of these nifty high-tech interfaces may be fun to play with and may succeed at getting funding, but their final test is always the typical user. Now, I know the typical user is held in low regard around here (we are the elite after all, or at least we like to think we are), but at some point you have to interact with reality. The desktop metaphor just won't die for a reason - people can use it. As an IBM researcher said in the article, "We wanted to find people who didn't understand the function of file folders, how to open files, how to delete files. We couldn't find anyone." Throw some weird abstract 3-D creation at people, and some won't understand. A lot of people can't even handle the concept of multiple ways of completing a given task; increasing the complexity of the interface would actually make things more difficult for them.
The real solution to this problem won't come from the interface side - it will come from the user side. You can't design an interface until you can understand what the user wants to do. This may not be as attractive a project for venture capital, but reality seldom is. In the end, I have a feeling that there will be no general agreements between users, making a single unified advanced interface impractical.
Yet again, the solution is on the user end. The desktop metaphor is a lot more useful than many people give it credit for. For example, the paragraph describing Scopeware really describes a generic file search program that already works perfectly well in a desktop metaphor. However, expanding it to fill the entire GUI is pointless. If you want to be able to find something, just put it somewhere that makes sense. In a year or two, will you really remember what day, or even what month you last used a certain file? If you file it away in a logical place though, you can use that same logic to locate the file again. Instead of file-specific knowledge, all you need to know is how you think. Sure this requires you to think in the first place, but that is the key issue here. In any interface, usefulness will be determined by how well files are maintained by the user. The current desktop metaphor requires very little from the user, just moving files around. Linked interfaces or fancy 3-D interfaces require more from the user, otherwise there will be no benefits - you still have to create the links or move files around spatially. If managing a system of files and folders is too much work for some people, will these new interfaces be any better?
So for those of you who survived this entire comment, I will sum up how to improve the computer interface for the masses. Teach them how to get the most out of the existing interface, based on their individual needs. Learn where they run into problems caused by the interface. Refine the interface to the point where the user is truly in control and isn't restricted by how the interface thinks things should be done - leave the thinking to the humans. We don't need any fancy interfaces on a general purpose computer. And yes Apple, that means cut it out with all the prettying up/cluttering up of the GUI. Just make it work and leave it alone.
Yeah! Just like the movies! (Score:2)
OS X? (Score:2)
honestly, though, it would be really nice when some of the mainstream OSes adopt the option to use alternative file browsers, whether for the cutting edge geeks to see their files as quake maps, or for more specialized users to see things as they are more properly arranged, or, and this is where i think the research ought to be going, handicapped users being able to "see" their data in ways that are more appropriate for those without certain assumed abilities.
the real "next interface" will be here when there is an interface that a blind user can use to browse his hard drive as fast or faster than a sighted person can use the current stock of file browsers - instead of using some kludgy add-on or adaptive technology working with a file browser built for a sighted person.
Allright, i'll weigh in on this one. (Score:3, Interesting)
1) What difference does it make how you represent a heirarchical filesystem and its contents? Zippo. Infact, organizing them by document and folder is probably the most condusive way to go, since most people arent like us. The rest of the world thinks in real world terms. Only programmers are accustomed to thinking about such things in highly abstract terms. Grandma shouldn't need to develop a mental picture of a binary search tree in order to find her cookie recipe. The desktop metaphor is boring in most implementations, yes, but its certainly not dead
2) 3D interfaces are rediculous. Take the screenshot that accompanies the article -- Three desktops are presented to the user in the form of a room, with a screen on each wall. What the hell difference does it make if they're on the walls? Youre STILL USING a flat, two dimensional surface to interact with! And so long as you're still using a flat, two dimensional space to interact with, representing them in 3D is pointless. Workspaces need to follow a design similar to channels on a television. You'll notice that your living room has one TV in it, capable of displaying hundreds of different workspaces. You don't have hundreds of TVs mounted all over your walls, each tuned to a different channel. 3D workspaces may have a future, but as a modus to display was essentially amounts to a 2D workspace floating in a 3D scene, they are beyond pointless. They're ridiculous. As in, its ridiculous to improve the design of UIs by "pulling a CueCat." You're inventing a tool to solve a problem that doesn't exist by pushing "2D in 3D" interfaces.
3) The 2D GUI isnt dead. It just needs refinement and rationality in its design. Speaking of irrational and unrefined ideas, take your common everyday scrollbar. You have a device (a mouse) capable of smoothly vectoring along a curved path, and communicating that movement to the computer. However, your damn UI still wants to alter your view of a workspace or document according to explicit X or Y axes. You can scroll up and down, OR, you can scroll left and right.. But never both, an act which would be far more intuitive to the common user. It takes fine adjustment of two separate widgets (a vertical and horizontal scrollbar) to accomplish a task that could be easilly encompassed within one...while wasting a disproportionately large amount of screen real estate in the process. So, rather than whine about it, I decided to do something about it a few years back.
Scrollbars are dead, and we killed them. Been working with someone for the past week or so on (finally) delivering a proof of concept model for the infamous "scrollball" whitepaper I released 3 years ago after InSight collapsed. The model looks fantastic so far (hi Dibos!) and will probably be dumped on Savannah or Freshmeat in a week or so once we fumigate the code to drive the last of the bugs out.
Cheers,
Great.. (Score:2)
Most programmers can't program GUI worth a damn to begin with, now we want to make it more complicated? please.
I can think of sverel model that are technically superiour, but they would fail in the real world when other programmer started writting apps for them, because they would not adhere to standards.
which they woiuld claim wasn't there fault because they didn't know there where standards.
Information Overload (Score:5, Insightful)
No one has proposed eliminating my car radio in any meaningful way. In fact, during the dot com rush, the radio was supposed to be replaced by a satellite fed computer that would do essentially the same thing - stream content. Why change what something that already worked fine *without* a satellite?
I was also supposed to tank my televison for a computer that would play mp3s, surf the web, stream video, and cook my dinner. Why change that interface when all I want to do is watch "6 Feet Under" or "The Sopranos"?
I like the systems the way they operate now. If the researchers were to study how people conduct their daily lives, they might learn that humans use a variety of interfaces to gather information. To use the metaphor of Gelernter, these people seem to be armed with a hammer and view every information problem as a nail.
A pox on themselves (Score:2)
"Smart quotes". Not.
Pearls of 'wisdom' (Score:2, Informative)
The problem isn't the desktop metaphor at all--it's that we're trying to use our personal computers for tasks they weren't meant to perform. Peel those tasks away to specialized devices--music to MP3 players, films to movie players, news and information to specialized readers--and you've solved the desktop metaphor problem. Each device will evolve its own best interface, depending on its specialized use.
I can't really see how this person is supposed to be seen as 'forward-thinking'. I mean, just how many various failed 'appliances' have we seen offered at discount/clearout, with X number of Linux hacks in recent months? For the current time, appliances have been tried and have been found wanting.
Another snippit: ;)
You could verbally ask your Web browser to go to CNN Online. While you're there, the browser might observe where you look on the page and offer pages with related content for viewing--in theory making it virtually effortless to get what you want from your computer at all times without having to stop at the desktop.And at the same time, make it virtually effortless to get what we don't want. You think pop-ups are bad now, imagine it they did things if you just look at the buggers ("the user is looking at the icon, therefor he/she has an interest in the product!"). Only one good thing I could see from it: the replacement for click-through banner ads. Advertising is for getting the attention of the consumer, in getting the company's/product's name/image/whatever out there for people to look at (think billboards, magazine/newspaper spreads, television spots, they don't require any action comparable to a banner ad 'click-through'). Just imagine what would happen to all those companies if they had to pay site owners 'per eye view' of their ads, for the site owner renting out part of their space for the ad.
My Big Brother can beat up your Big Brother any day!
WIMP interfaces (Score:2)
Each thread has a different window, each file has a seperate icon, etc. There is really not much one can do to improve the metaphor without changing the operating system.
Object oriented filesystems would make content-based retrieval and end-user programming a little easier. You could build a "class" of presentations for various data, and "instances" would be special folder structures with "buttons" or menus on the "browser" to initiate various actions, for example.
Escaping from a windowed interface would actually be a step backwards, as it stands now. Escaping from the Windows User's "No, really, Microsoft invented computing" mindset might help, but that is a slow progression at best.
The best solution using existing technology would be something like X11. Imagine Xwindows, only where your Windowmaker GUI has only Windowmaker widgets, look and feel, and your GNOME GUI has only GNOME widgets, look and feel, even if you're using applications from different GUI interfaces.
While it is nice to say the WIMP metaphor is dead, it is a LOT safer to say there are a lot of well-established implementations of the WIMP GUI that are on their way out, because of pressures from the unwashed masses.
Re:What are the negatives of the desktop? (Score:2)
I am wondering if there's a really good explination of why the desktop metaphor is, to borrow a phrase from "1984", un-good.
This is only my opinion, but...