Hi Tuomas--
>1. I thought at some point you were removing the word "cursor" and
>starting to use "frame".
>
>2. do these cursors contain the dimensions also?
Oops, "frame" is the better term, since the frame *does* contain
the dimensions.
>3. CHUG*, SHEAR* etc are not defined clearly enough here. We talked about
>you defining them about a year ago but you never got back to us on that,
>unfortunately.
Right. Well, I think they're clarified by now, but I can only get out
about one memo a month ... Sigh.
>> whichcur CURSORFORK [ creates a new first-class cursor in the same
>> location ]
>>
>> whichcur KILLCURSOR [ evaporates the current cursor ]
>>
>> whichcur SUBCURSOR [ creates a subordinate cursor managed by another
>> cursor, to be used in some sub-operation ]
>>
>> whichcur KILLSUBCURSOR [ evaporates the current subcursor, but only if
>> it is a subcursor in some current set. Killing the last subcursor of a set
>> is effectively a return-from-subroutine to a parent cursor above ]
>
>These are rather unclear as well, as you have not properly defined cursors
>and subcursors yet.
Subcursors I know are new. I'm not sure what definition you want
of cursors. I know the geometry of cursor-wheels and whatnot
that I presently have in mind, but I don't have any metaphysical
or mathematical definition ...
>> == VIEW OPERATIONS
>>
>> whichcur RASTER [ sends out the current raster list, somehow
>> linearized-- how linearized to be dealt with later ]
>>
>> whichcur REFRESH [ sends out the current raster list, with contents,
>> somehow linearized-- how linearized to be dealt with later ]
>
>This means that the back-end has to be completely aware of any views.
>I don't think that's necessarily a good thing.
Correct in the best cases. But if you're talking to a dumb
screen, it does.
>> whichcur VIEWMODE typeno [ selects a view type ]
>>
>> whichcur CELLVIEWMODE typeno [ selects a cellview type ]
>
>Ditto.
Ditto.
Best, Ted
At 11:04 PM 11/11/01 +0200, you wrote:
>1. I thought at some point you were removing the word "cursor" and
>starting to use "frame".
>
>2. do these cursors contain the dimensions also?
>
>3. CHUG*, SHEAR* etc are not defined clearly enough here. We talked about
>you defining them about a year ago but you never got back to us on that,
>unfortunately.
>
>> whichcur CURSORFORK [ creates a new first-class cursor in the same
>> location ]
>>
>> whichcur KILLCURSOR [ evaporates the current cursor ]
>>
>> whichcur SUBCURSOR [ creates a subordinate cursor managed by another
>> cursor, to be used in some sub-operation ]
>>
>> whichcur KILLSUBCURSOR [ evaporates the current subcursor, but only if
>> it is a subcursor in some current set. Killing the last subcursor of a set
>> is effectively a return-from-subroutine to a parent cursor above ]
>
>These are rather unclear as well, as you have not properly defined cursors
>and subcursors yet.
>
>> == VIEW OPERATIONS
>>
>> whichcur RASTER [ sends out the current raster list, somehow
>> linearized-- how linearized to be dealt with later ]
>>
>> whichcur REFRESH [ sends out the current raster list, with contents,
>> somehow linearized-- how linearized to be dealt with later ]
>
>This means that the back-end has to be completely aware of any views.
>I don't think that's necessarily a good thing.
>
>> whichcur VIEWMODE typeno [ selects a view type ]
>>
>> whichcur CELLVIEWMODE typeno [ selects a cellview type ]
>
>Ditto.
>
> Tuomas
>
_________________________________________
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
_________________________________________