Annotation of OpenXM_contrib/gnuplot/docs/old/README.nex, Revision 1.1.1.1
1.1 maekawa 1: The 3.6 version of gnuplot is proud to include a new NeXTstep
2: terminal driver. The new driver offers the following new
3: features:
4:
5: 1) Multiple windows
6: 2) Resizable windows
7: 3) Direct print interface from windows
8: 4) Titleable and re-addressable windows
9: 5) A real NeXTstep-style interface to the terminal driver
10:
11: The driver runs as a separate application, and hence has
12: it's own set of controls and interfaces. It registers itself
13: with the operating system as a distributed objects "GnuTerm"
14: server, and thereafter accepts requests from any gnuplot instances
15: on the machine.
16:
17: Nick Strobel's original single-viewport NeXTstep terminal is available
18: as an option to the next terminal. It can be invoked from the gnuplot
19: command line as:
20: gnuplot> set term next old
21: There are several reasons why one might choose the older terminal.
22: First, the new terminal will probably not work on NeXT systems
23: running a pre-3.0 version of the operating system.
24: Second, because all of the postscript must be buffered in order
25: to allow re-sizing and printing of the window's contents, the
26: new terminal can be a memory hog for very complicated plots.
27: The original README.nex file for the original next terminal is
28: included at the end of this document.
29:
30:
31: Installation
32: ------------
33:
34: In addition to enabling the #include next.trm in term.h before
35: compiling gnuplot, the GnuTerm.app application must be separately
36: built and installed. All of the source code is included in
37: the NeXT subdirectory of the gnuplot distribution. GnuTerm.app
38: can be built for the current architecture by cd-ing to the NeXT
39: directory and type "make". For more complicated installations,
40: or to build the application "FAT" (to run on more than one
41: processor architecture), it's easiest to fire up NeXT's
42: ProjectBuilder.app and open NeXT/PB.project.
43:
44: GnuTerm.app can be installed in any directory contained in the
45: WorkSpace's ApplicationPaths dwrite. For most situations,
46: this means installing GnuTerm.app in either /LocalApps or
47: ~/Apps.
48:
49: If you wish to locate the GnuTerm.app somewhere other than ~/Apps
50: or /LocalApps, you can "setenv GNUTERMPATH /newpath" to tell
51: gnuplot where to find it.
52: Example (wherein GnuTerm.app is in /LocalApps/Data):
53:
54: host% setenv GNUTERMPATH "/LocalApps/Data"
55:
56: Robert Lutwak
57: robert@amo.mit.edu
58: July 14, 1996
59:
60:
61: Following is the README.nex that accompanied the original
62: (single viewport) next terminal, which is still accessible
63: as "set term next old".
64: -------------------------------
65: This directory contains version 2 of the additional files
66: you'll need to get gnuplot3.0 to display it's postscript directly to a
67: window instead of going through the klunky process of writing the
68: postscript to a file and launching Previewer to view the file. Note
69: that all input is still done at the shell level! Fancier NeXTStep
70: interfaces will be a future project.
71:
72: This version is faster and leaner than the old method. It
73: also does not eat up swap space like the older version (this was
74: particularly noticeable when doing animation-like plots). To do this
75: I used DPS function calls instead of creating a NXImage and
76: compositing the stream of commands. I based my code on the program
77: called "epsview" in the hackkit tar file on the archive servers.
78:
79: The next.trm (next terminal) is basically the post.trm
80: (postscript terminal) with the fprintf replaced by DPSPrintf and
81: outfile by the DPSContext d. You'll also see that I also used some
82: code (with modifications) from David S. Joerg's MovieApp. Using the
83: DPS functions enabled me to slim down the EpsViewer.[hm] and
84: EPSView.[hm] files.
85:
86: No claim is made to code elegance or to it being a good example of
87: objective-c coding. This is my first (well, second, sort of) objective-c
88: program. It seems to work for me. Any constructive criticism would be
89: appreciated. I can be reached at strobel@phast.phys.washington.edu
90:
91: cheers!
92:
93: nick strobel
94: -----------------------------------
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>