Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!think!ames!ucbcad!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt)
Newsgroups: comp.windows.misc
Subject: Re: Better Windows? (stolen from another newsgroup)
Message-ID: <8705190042.AA14664@cogsci.berkeley.edu>
Date: Mon, 18-May-87 20:42:50 EDT
Article-I.D.: cogsci.8705190042.AA14664
Posted: Mon May 18 20:42:50 1987
Date-Received: Tue, 19-May-87 06:37:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: boring!jack@cogsci.berkeley.edu (Jack Jansen)
Organization: AMOEBA project, CWI, Amsterdam
Lines: 27


The idea of selecting multiple files, and then double-clicking
the application to act on them is something I've been thinking
about quite a bit.

I think the idea can be generalised even further.

If you view every icon as an object that can be activated, there
are only two primitives that you need to do almost everything:

- Activating an object (double clicking). This works like it currently
  does: when you activate a disk/folder, it opens, when you activate
  a program, it starts running, etc.
- Feeding an object (dragging one or more other objects onto it).
  For disks and folders, it does the same as usual: the objects get
  stored there. If you feed a program, it starts running with those
  objects as arguments.

The nice thing is a lot of things that are handled in a 'funny' way
currently can be incorporated in the general scheme. For instance,
to print a file, you move it to the printer icon. It remains unspecified
wether this icon represents the device itself (i.e. the OS knows
about the printer) or a program that knows how to drive the printer
(and that might do spooling, reformatting, etc).
-- 
	Jack Jansen, jack@cwi.nl (or jack@mcvax.uucp)
	The shell is my oyster.