RFC 398 UNKNOWN GRAPHICS · SERVICES

UCSB Online Graphics

A directory of UCSB graphics sockets for IMLAC, TEKTRONIX and Level 0 users.

On rfc-editor.org ↗
PUBLISHED
September 1972
AUTHORS
J.R. Pickens, E. Faeh
STREAM
Legacy
IMLAC SPECIAL-SOFTWARE SOCKET
x'701'
LEVEL 0 GRAPHICS SOCKET
x'705'
TEKTRONIX SOCKET
x'801'
DOI
10.17487/RFC0398

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
NWG/RFC #398                                        John R. Pickens
UCSB Online Graphics                                Edward D. Faeh
NIC 11911                                           UCSB
                                                    22 Sept 72

At present, users with TEKTRONIX or IMLAC terminals or with systems
that support the proposed level 0 graphics protocol can access UCSB
graphics.  Listed below are the ICP sockets for the currently
supported terminals and protocols.  Any detailed questions about or
problems with a particular protocol should be directed to Ed Faeh
(805-961-4047).

   Socket                       Supports

   x'701'               IMLAC with special software designed
                        by Jerry Powell (MITRE Corp.).
                        Graphics is sent over a simplex
                        connection to the IMLAC.  Alphanumerics
                        are sent over a TELNET-like connection
                        to a separate device.  The IMLAC
                        software can be loaded from MIT-DMCG.

   x'703'               IMLAC with 80x80 display grid
                        and Standard Text and Edit Package.
                        Some IMLACs have a 64x64 display grid.
                        Therefore, the choice may be made in
                        the near future to format the
                        graphics output from this connection
                        for the smaller grid resolution so
                        that both terminal types may be handled.
                        Display resolution is limited with
                        this terminal configuration as
                        normal UCSB terminals have 1024x1024
                        grid.  Nevertheless, meaningful
                        displays are obtained even at the
                        lower resolutions.

   x'705'               Current Level 0 graphics protocol.

   x'707'               Same as x'701' but with special
                        UCSB online keyboard as input.
                        This configuration averts the
                        necessity of spelling out online
                        operators.

   x'709'               Same as x'705' but with special
                        UCSB online keyboard as input.

NWG/RFC# 398                        JRP EDF 22-SEP-72 16:25  11911
UCSB OnLine Graphics


   x'801'               TEKTRONIX terminals.  Models 4002-A
                        4010, and T-4002 have been tested
                        successfully.  Presumably all other
                        4002 compatible terminals will also work.

The primary problems that will be encountered by the network user
center about display formatting.  For historical reasons (i.e.  only
one type of terminal in house ) no means were included in the system
to facilitate terminal independent random positioning of alphanumeric
output.  Thus, a program which draws and labels a graph neatly on one
terminal might label like a kindergartener on other terminals.
Nevertheless, this problem can be minimized with careful programming
and efforts are underway to provide at least minimal alphanumeric
device independence.

Users interested in experimenting with online graphics should contact
John Pickens (805-961-3454), Glen Davis (805-961-2462), or Mark
Krilonovich (805-961-3454).  Suggestions and criticisms of all aspects
of the UCSB OnLine - Network User interface are desired.






       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by BBN Corp. under the   ]
       [ direction of Alex McKenzie.                      1/97 ]

ISO Plain Language

On this page
PROBLEMUsers needed to know which ICP socket to use for the graphics terminal or protocol they had.
MECHANISMThe RFC lists UCSB graphics sockets and describes the terminals, software and protocols supported at each one.
USING THE SERVICEIt warns that alphanumeric display formatting may vary across terminals and invites user feedback.

§1UCSB Graphics Connections

UCSB users with TEKTRONIX or IMLAC terminals, or systems supporting the proposed Level 0 graphics protocol, can access UCSB graphics. The RFC lists ICP sockets for the supported terminal and protocol configurations.

Questions about a particular protocol are directed to Ed Faeh.

Different terminals connect to UCSB graphics through different sockets. This RFC gives the socket for each supported configuration.

§2Supported Configurations

Socket x'701' supports an IMLAC with special software; graphics use a simplex connection and alphanumeric data a separate TELNET-like connection. Socket x'703' supports an IMLAC with an 80x80 display grid and a standard text and edit package, though some IMLACs have 64x64 grids.

Sockets x'705' and x'709' support the current Level 0 graphics protocol, with the latter using a special UCSB online keyboard. Sockets x'707' supports the special-software IMLAC configuration with that keyboard. Socket x'801' supports tested TEKTRONIX models 4002-A, 4010 and T-4002.

The socket list distinguishes IMLAC setups, Level 0 graphics and TEKTRONIX terminals. Some configurations add a special online keyboard or use a separate text connection.

§3Display Formatting

The RFC says the main problem for network users is display formatting. The system had no mechanism for terminal-independent random positioning of alphanumeric output because it had originally been built around one terminal type.

A program that labels a graph neatly on one terminal may place labels poorly on another. The authors say careful programming can reduce the problem and that work is underway on minimal alphanumeric device independence.

Text labels may appear differently on different terminals. The RFC says programmers can reduce the problem and that work on device independence is underway.