Debian Codegraph @

rfc125.html

raw
1 <pre> NETWORK WORKING GROUP
2
3 REQUEST FOR COMMENT: 125
4
5 NIC 5841
6
7
8
9
10 APRIL 18, 1971
11
12
13
14
15
16
17
18
19
20
21
22
23 <span class="h1">JOHN McCONNELL</span>
24
25 AMES RESEARCH CENTER
26 MOFFETT FIELD, CALIFORNIA
27
28
29
30
31
32 Response to RFC #86, Proposal for Network Standard Format for a graphics
33 data stream.
34
35
36
37 Category D.6
38 RFCs obsoleted None
39 RFCs updated 86
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey"> [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey">The basic approach of transmitting an intermediate, device independent</span>
55 language which is translated into specific device codes at the
56 receiving host is sound. It appears to be the only approach that will
57 allow thought to be centered on picture descriptions. Ames Research
58 Center has adopted this approach in tying its graphic facilities, of
59 various types, and on various computers together. At present, we are
60 in the design phase and expect our package to be running in about six
61 months. The main objections to the structure as it now exists, is that
62 it takes no cognizance of the many features available on graphics
63 devices. Since these features will always be changing with new
64 devices, a set of option or mode primitives should be defined which
65 are logically separate from the drawing primitives provided in <a href="./rfc86">RFC 86</a>.
66 The mode primitives will act upon the drawing primitives to modify
67 their actions. The scope of a mode primitive extends until a new mode
68 primitive resets an option. The use of mode primitives will allow the
69 network standard stream interpreter to treat them as null operations
70 if the features are missing at a particular host, or to perform more
71 detailed interpretation of the following data stream to achieve
72 results. The drawing primitives may also then keep a standard format
73 which need not be changed to incorporate new features.
74
75 Overall modes which primitives could control would be intensity
76 levels, or color selections for objects, in addition blinking of
77 objects should be provided. For vectors, the additional facility for
78 drawing dashed lines is necessary.
79
80 Character strings require another set of specification. The convention
81 for the beam is usually that it is in the center of the rectangular
82 area defining a character's boundaries. The beam position is usually
83 undefined at the finish of drawing a character string. A strong
84 exception is taken to the exclusion of form control characters from
85 strings. If included in the character string, they could provide for
86 shifting from upper to lower case, subscripting, superscripting, and
87 underscoring, as well as tab and other "carriage" motion functions.
88 The appropriate characters could be extracted at interpretation time
89 to provide the necessary information to display more complex strings.
90 To allow the facility for generating ALGOL-like delimiters, such as
91 "then", a convention for canonical character string should be adopted.
92 I believe the Multics conventions described in reference 1 will
93 suffice.
94
95 Additional options for character strings should include a size
96 specification and an orientation selection. As many devices, have
97 hardware character generators that are fixed, some of these options
98 may not be desirable to implement as subroutines.
99
100 Another area that should be looked at further is the additional
101 symbols available which are not specified in ASCII. Some means of
102
103
104
105 <span class="grey"> [Page 2]</span></pre>
106 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
107 <span class="grey">defining them should be provided within the argument string itself,</span>
108 again Multics has allowed the specification of arbitrary characters by
109 entering their octal equivalents. The convention should use a control
110 character code followed by a l6-bit list name which specifies the
111 sub-list defining the character. The other alternative is to allow
112 8-bit characters and allow the interpreter to choose a sub-list if the
113 character is not realizable with a hardware generator.
114
115 The special form control characters to be used are:
116
117 a. BS - backspace
118 b. LF - for new line
119 c. SO/Sl - shift case
120 d. DC2 - superscript following characters
121 e. DC4 - subscript following characters
122 f. DC3 - special non-ASCII character follows
123 g. Tab - position to next tab. May be predefined or specified.
124
125 Another construct should be added to those proposed in <a href="./rfc86">RFC 86</a>. This is
126 the display list pointer (NGDLP). It will have as a value the next
127 drawing primitive to be executed. The value is a displacement from the
128 head of a list. With no mode setting primitives, this value is one to
129 one with the drawing primitives transmitted in the NGDS. The NGDLP is
130 needed for consistency for execution of the nested list structure.
131 Whenever an execute list primitive is encountered, the current value
132 of the NGDLP is saved along with the list name and current origin
133 value. When execution of a list is finished, the last values saved are
134 restored.
135
136 An include list primitive would allow the treatment of a sub-list to
137 be equivalent to a macro instead of a subroutine. This would be
138 necessary to avoid changes to all sub-pictures on the screen due to
139 the manipulation of a sub-list. The include primitive should have as
140 parameters such specifications as size, intensity, orientation,
141 blinking, etc. After a sub-list has been included in another list, it
142 is no longer distinguished as a separate entity.
143
144 To cut down on the volume of data being transferred, other commands to
145 be parsed by the stream interpreter should be added. These would allow
146 the manipulation of a list by the receiving host without a
147 retransmission. The types of manipulations would include rescaling
148 the coordinates for shrinking or zooming, translation of the origin,
149 or rotation. Other manipulations to provide for displaying or not
150 displaying a list, or enabling of disabling light pen detections would
151 be desirable.
152
153 The problem of interaction with the displayed picture has yet to be
154 addressed, so this will be an attempt to elicit some more discussion
155
156
157
158 <span class="grey"> [Page 3]</span></pre>
159 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
160 <span class="grey">in this area. The use of a keyboard or function keys poses no problem</span>
161 in that both can be handled as a standard message from the graphics
162 terminal. The use of devices that interact with the picture or the
163 screen such as light pens, mice, joysticks, or tablets presents a
164 different and more complex problem. This problem is the standard one
165 of making an association between the point selected and some
166 meaningful entity such as a list or a primitive. This association
167 should be made at the receiving host since the NGDS has been changed
168 in unknown ways.
169
170 To allow the transmitting host to identify the object pointed at, the
171 stack of suspended lists and the current value of the NGDLP will
172 qualify the object to any level in a hierarchical structure. In
173 addition, normalized x,y coordinates should be returned, as well as a
174 character displacement if a string was pointed at. This structure will
175 serve a light pen device very well since the light pen mechanism
176 allows the determination of the currently executing primitive. Other
177 devices interact with the picture in an asynchronous fashion and the
178 association of an x,y pair to a structure is a more difficult problem.
179 This may require that the host generating the graphic data stream be
180 responsible for making that association. A further complication arises
181 when it is desired to use a light pen in an area where no beam motion
182 occurs, then some directive to periodically sweep the screen and
183 "find" the pen must be provided. This might be a sub-list which is
184 executed periodically for this function.
185
186
187 [ This RFC was put into machine readable form for entry ]
188 [ into the online RFC archives by Jerry Tenenbaum 4/97 ]
189
190 ---------------------------------------------------------------------------
191 Reference: Osanna, J., Sahzer, J.
192 Remote Terminal Character Stream Processing of Multics
193 Proceedings SJCC, 1970, p. 671
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211 [Page 4]
212 </pre>