[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
:zz,virt: Another way to think of s.0 (was Re: [zzdev] Re: [zzdev] d.masterdim and slices
- To: zzdev@xxxxxxxxxx
- Subject: :zz,virt: Another way to think of s.0 (was Re: [zzdev] Re: [zzdev] d.masterdim and slices
- From: Ted Nelson <ted@xxxxxxxxxx>
- Date: Wed, 26 Jul 2000 21:36:20 -0700
- Cc: ted@xxxxxxxxxx
- In-reply-to: <20000725190100.D9836990@xxxxxxxxxxxxxxxxxxx>
- References: <Pine.HPP.3.96.1000725215125.29542D-100000@xxxxxxxxxxxxxxxx>
Think of slice 0 as being like the "desktop"--
the stuff the user wants to see ordinarily.
But it has docking stations for various things that
come in, and different items can dock at the same
station, depending on what's called in.
I really appreciate all the thoughts people are putting into
the heavier technicalities of the system, but it's important
to remember also that the easy visibilities are a crucial
aspect of the ZigZag idea from a user's point of view.
Then the *sneaky* part of the design is the way we
overload its simple visible concepts with system structure.
But the design trick is to stay always faithful to the easy part.
At 10:00 PM 7/25/00 +0300, you wrote:
>On 25 Jul, Tuomas Lukka wrote:
>> On Tue, 25 Jul 2000, Tuukka Hastrup wrote:
>>> On 25 Jul, Tuomas Lukka wrote:
>>> >> If s.0 is non-empty, then one would like to see the difference between
>>> >> getSpaceHome and getSliceHome(s.0) - if there's something to do with
>>> >> slices, why not with s.0 too?
>>> > Sorry, now I don't understand... why can't the Space home be
>>> > the home cell of slice 0?
>>> If there's (and it seems there is) some cases we want to distinguish
>>> between a slice and the compound place, then we should make the
>>> difference visible somehow.
>> The point is that s.0 is *always* there. So think of the compound place as
>> s.0 with other things (slices) loaded in. That's why s.0's home is the
>> whole hog's home.
>Still, if we were to do something to s.0, like export new default
>settings, then how do we distinguish between exporting s.0 and
>exporting the compound space as a whole? (Another example: you want
>the slice's d.masterdim rank or the space's d.masterdim rank)
>OK, s.0 is special. It might be it's not a problem if it has special and
>normal slice role at the same time. I guess we'll see as we go on.
Theodor Holm Nelson
Project Professor, Keio University SFC Campus, Fujisawa, Japan
Visiting Professor, University of Southampton, England
? e-mail: ted@xxxxxxxxxx ? world-wide fax 1/415/332-0136
? http://www.sfc.keio.ac.jp/~ted/ ? http://www.xanadu.net
? Coordinates in USA Tel. 415/ 331-4422
Project Xanadu, 3020 Bridgeway #295, Sausalito CA 94965