🚀 go-pugleaf

In article <973@riddle.UUCP> domo@riddle.UUCP (Dominic Dunlop) writes:
#sorry, wrong metaphor) I maintain it should be seamless.  The UNIX
#analogue to moving a file between folders is the mv command.  This indeed
#sometimes has to copy the file from one physical device to another behind
#the scenes.  But it never results in there being two copies of a file
#where before there was only one.  I suppose it could do, but to do so
#would be inconsistent with UNIX' metaphor of an hierarchical file system
#that is as seamless as possible.  You really want a copy?  OK.  Use cp. 
#(Yes, yes, I know that you can get bit if you try to use the other alias
#for mv, ln, across physical devices -- sorry if you were expecting
#perfection.)

Ah but isn't copying an Inherent function that is importantly different
from the idea of "moving"?  I think it would be VERY nice if you could
simply turn the pointer into something and VOILA', you pull out "copies"
and set them whereever the heck you please to.  If they are on the same
disk let em be!  It would be nice if the mac could work up its own
scheme for "backup" and leave symbolic duplication for us to play with.

The idea of "moving/dragging" is overloaded with that of copying.  This
is a hole in the paradigm that the mouse provides.  I still think that putting
a "copy" to the printer would be a VERY appropriate and intuitive idea, unless
the printer is a xerox machine which takes it and hands it back to you.  

There are LOTS of VERY logical and intuitive ways to use the mouse-as-hand
paradigm.  I personally think that nearly NONE of the system stuff should be
left to the user.  (i.e. if you take a file to the trash, warn you if its the
ONLY "link" left because the system knows where it keeps its duplicates.  Maybe
even make a FORMAL diff-format for each application and use that as a 
compacted version of "duplication/modification".

Anyone got any ideas one how to show pipes?  How about having a palatte or 
something made up from pull-down/over/across/out panels and "snapping"
their icons together?  How about putting files on either end?  Putting
it in the background by closing up *all* the outlets, or finding a place
to put them that would allow them (something like standard error could
have a window to spooge in).  In this case a window is ONLY a way
of "opening" a file and the format coming out from a pipeline could
determine what kind of window stuff gets put in (graphics, text, readouts etc..)

I think that there are only too many ideas that people haven't thought about
that *AREN'T* just cute (like moving/bouncing windows!!) but are utile and
finding *specifically* what the problems are with using the more promising ones.

I notice that too few people talk about the *exact* problems they have with
stuff except for the good old keyboard/mouse stuff.  These are certainly
valid areas to pursue.

#I guess life could be worse: the Mac disks might be called A:, B:...
#(Probably one of Digital's better ideas for the 1960s.  Just a pity that
#twenty million users are still living with it because CP/M appropriated it
#in the 1970s.)

I DO hate it when that happens.

#-- 
#Dominic Dunlop
#domo@sphinx.co.uk  domo@riddle.uucp

### C>H> ###