-
Notifications
You must be signed in to change notification settings - Fork 59
/
anyplt.html
366 lines (322 loc) · 10.3 KB
/
anyplt.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
<html>
<head>
<TITLE>
ANYPLT - Simple Graphics Interface
</TITLE>
</HEAD>
<BODY bgcolor="#EEEEEE" link="#CC0000" alink="#FF3300" vlink="#000055">
<H1 align = "center">
ANYPLT <br> Simple Graphics Interface
</H1>
<hr>
<P>
<b>ANYPLT</b>
is a FORTRAN90 library which
provides an interface between a FORTRAN90 program and
a variety of graphics packages.
</p>
<p>
The idea is outdated now, but at the time, I was trying to make
it possible to define a simple graphic interface routine that
would allow me to run the same program on a variety of machines
and environments without having to worry about the details of
the particular graphics package that was available.
</p>
<p>
The interface consisted of a single subroutine, with a single
argument, whose value indicated the graphics action desired.
Any data required to carry out the indicated command was supplied
indirectly, by setting certain variables in a COMMON block.
</p>
<p>
This idea was helpful for me for a time. Once I stopped needing
to do graphics in so many environments, I quit developing the
package, and it has started to suffer 'data rot'. Nonetheless,
I keep it around in fond memory of the time when it was so helpful.
</p>
<p>
At one time or another, I had developed the following interfaces:
<ul>
<li>
<b>ANYATT</b>, a version which uses the high resolution mode of the AT&T
PC6300. (400 pixels high, 640 wide). Characters and symbols
are drawn.
</li>
<li>
<b>ANYBUG</b>, merely a debugging tool, this package records all the calls
to ANYPLT in a file. (Nominally 1 high by 1 wide).
</li>
<li>
<b>ANYCAL</b>, a flavor of CALCOMP as implemented at the University of
Pittsburgh, producing a plotfile which may then be output
on a plotter. (Nominally 11 high by 8.5 wide).
</li>
<li>
<b>ANYCGM</b>, CGM output, (Computer Graphics Metafile), as implemented
in the Pittsburgh Supercomputing Center's DRAWCGM package.
</li>
<li>
<b>ANYIBM</b>, interactive IBM graphics (200 high, 640 wide)
</li>
<li>
<b>ANYMAC</b>, Apple Macintosh graphics. Requires TOOLBX.PAR file.
(342 high, 512 wide). FORTRAN can't seem to access the
entire screen, however.
</li>
<li>
<b>ANYNCR</b>, NCAR GKS graphics output to a CGM metafile. 'Meta-screen'
is 1 high, 1 wide, but output size depends on output
device.
</li>
<li>
<b>ANYNUL</b>, a null device. This allowed you to compile a program
with graphics calls, but without supplying any graphics library.
</li>
<li>
<b>ANYP10</b>, output to interactive PLOT10 graphics (768 high, 1024 wide)
A local modification to the package allows the program
to open a PLOT10 file in which a copy of the graphics
may be stored, to be viewed later by typing it out.
</li>
<li>
<b>ANYPS</b>, output to a PostScript file.
</li>
<li>
<b>ANYTTY</b>, output to a crude terminal plotting package, which uses '*' and
blank to produce a plot. (24 pixels high, 80 wide).
</li>
</ul>
</p>
<h3 align = "center">
Licensing:
</h3>
<p>
The computer code and data files described and made available on this web page
are distributed under
<a href = "../../txt/gnu_lgpl.txt">the GNU LGPL license.</a>
</p>
<h3 align = "center">
Languages:
</h3>
<p>
<b>ANYPLT</b> is available in
<a href = "../../f77_src/anyplt/anyplt.html">a FORTRAN77 version</a> and
<a href = "../../f_src/anyplt/anyplt.html">a FORTRAN90 version</a>.
</p>
<h3 align = "center">
Related Data and Programs:
</h3>
<p>
<a href = "../../c_src/dislin/dislin.html">
DISLIN</a>,
C programs which
illustrate the use of DISLIN, a scientific graphics package.
</p>
<p>
<a href = "../../c_src/drawcgm/drawcgm.html">
DRAWCGM</a>,
a C library which
can create graphics output in CGM, PostScript or X11 format;
</p>
<p>
<a href = "../../f_src/ps_write/ps_write.html">
PS_WRITE</a>,
a FORTRAN90 library which
can be used to create PostScript image files.
</p>
<p>
<a href = "../../f77_src/ttyplt/ttyplt.html">
TTYPLT</a>,
a FORTRAN77 library which
creates simple typewriter graphics images of mathematical data.
</p>
<h3 align = "center">
The NUL Interface
</h3>
<p>
The <b>NUL</b> interface was the easiest to design. The idea
was that the <b>NUL</b> device was a fake device that did nothing,
and the interface was a dummy routine with the right name that would
keep the compiler happy. The purpose of the <b>NUL</b> device was to
allow me to compile and load a graphics program when I didn't actually
want any graphics. So the program could merrily call the ANYPLT
routine all it wanted, but the graphics information was never sent anywhere.
</p>
<p>
<ul>
<li>
<a href = "anynul.f90">anynul.f90</a>,
the source code for the interface.
</li>
<li>
<a href = "anynul.sh">anynul.sh</a>,
commands to compile the source code.
</li>
<li>
<a href = "anynul_prb.sh">anynul_prb.sh</a>,
commands to compile and run the test code with the <b>NUL</b> interface.
</li>
<li>
<a href = "anynul_prb_output.txt">anynul_prb_output.txt</a>,
the output file.
</li>
</ul>
</p>
<h3 align = "center">
The BUG Interface
</h3>
<p>
The <b>BUG</b> interface was the second easiest to design. The idea
was that the <b>BUG</b> device was a fake device that simply recorded
all the calls to the graphics interface routine by writing the data to
a file. This would allow me to debug a malfunctioning program by
intercepting the graphics calls.
</p>
<p>
<ul>
<li>
<a href = "anybug.f90">anybug.f90</a>,
the source code for the interface.
</li>
<li>
<a href = "anybug.sh">anybug.sh</a>,
commands to compile the source code.
</li>
<li>
<a href = "anybug_prb.sh">anybug_prb.sh</a>,
commands to compile and run the test code with the <b>BUG</b> interface.
</li>
<li>
<a href = "anybug_prb_output.txt">anybug_prb_output.txt</a>,
the output file.
</li>
<li>
<a href = "anybug_prb.bug">anybug_prb.bug</a>,
the <b>BUG</b> file.
</li>
</ul>
</p>
<h3 align = "center">
The CGM Interface
</h3>
<p>
The <b>CGM</b> interface was designed to interact with the <b>DRAWCGM</b>
package, a graphics package developed at the Pittsburgh Supercomputing Center,
which could output graphics in CGM format, but also in PostScript or X Windows
as well.
</p>
<p>
<ul>
<li>
<a href = "anycgm.f90">anycgm.f90</a>,
the source code for the interface.
</li>
<li>
<a href = "anycgm.sh">anycgm.sh</a>,
commands to compile the source code.
</li>
<li>
<a href = "anycgm_prb.sh">anycgm_prb.sh</a>,
commands to compile and run the test code with the <b>CGM</b> interface.
</li>
<li>
<a href = "anycgm_prb_output.txt">anycgm_prb_output.txt</a>,
the output file.
</li>
</ul>
</p>
<h3 align = "center">
The MAC Interface
</h3>
<p>
The <b>MAC</b> interface was designed to interact with (a very early model)
of the Macintosh computer, using the Absoft Fortran compiler, and an
assembly language package called TOOLBOX.SUB, which I couldn't find if I
wanted to now.
</p>
<p>
<ul>
<li>
<a href = "anymac.f90">anymac.f90</a>,
the source code for the interface.
</li>
</ul>
</p>
<h3 align = "center">
The PS Interface
</h3>
<p>
The <b>PS</b> interface was designed to output a PostScript image.
</p>
<p>
<ul>
<li>
<a href = "anyps.f90">anyps.f90</a>,
the source code for the interface.
</li>
<li>
<a href = "anyps.sh">anyps.sh</a>,
commands to compile the source code.
</li>
<li>
<a href = "anyps_prb.sh">anyps_prb.sh</a>,
commands to compile and run the test code with the <b>PS</b> interface.
</li>
<li>
<a href = "anyps_prb_output.txt">anyps_prb_output.txt</a>,
the output file.
</li>
</ul>
</p>
<h3 align = "center">
The TTY Interface
</h3>
<p>
The <b>TTY</b> interface was designed to output ridiculously crude
"teletype" or "typewrite" graphics.
</p>
<p>
<ul>
<li>
<a href = "anytty.f90">anytty.f90</a>,
the source code for the interface.
</li>
<li>
<a href = "anytty.sh">anytty.sh</a>,
commands to compile the source code.
</li>
<li>
<a href = "anytty_prb.sh">anytty_prb.sh</a>,
commands to compile and run the test code with the <b>TTY</b> interface.
</li>
<li>
<a href = "anytty_prb_output.txt">anytty_prb_output.txt</a>,
the output file.
</li>
</ul>
</p>
<h3 align = "center">
Examples and Tests:
</h3>
<p>
<ul>
<li>
<a href = "anyplt_prb.f90">anyplt_prb.f90</a>, a sample problem.
</li>
<li>
<a href = "anyplt_prb_output.txt">anyplt_prb_output.txt</a>, sample problem
output.
</li>
</ul>
</p>
<p>
You can go up one level to <a href = "../f_src.html">
the FORTRAN90 source codes</a>.
</p>
<hr>
<i>
Last revised on 29 December 2010.
</i>
<!-- John Burkardt -->
</body>
</html>