Niels Hald Pedersen wrote:
> Well, the gurus may smile (or worse), but for me, some (basic) un*x
> features still appear to me as visions from God. So when I came upon
> this way of solving some graphics problems, I decided to waste list
> bandwidth on it, in hope of somebody finding it useful. So here goes:
>
> Problem:
> to produce advanced (but not dynamic, not moving, animated or so)
> graphics output, graphs, reports and so, for viewing and optional
> printout, without having to make a full blown X program.
>
> Solution:
> Generate graphics inside program as PostScript source, use both for
> display and printouts.
>
> How:
> Postscript is basically an ascii text, Forth-like (reverse (perverse)
Some would dispute that "perverse" adjective. Some of us have
reverse Polish minds, and deserve fair treatment. (I never could
get any other kind of calculator to work right.)
> polish notation) language for describing the graphical appearance of
> something, invented by Adobe. Possibilities are stunning and in full
> colors. Pointers to two comprehensive Postscript pages (random, there
> are many):
> http://www.geocities.com/SiliconValley/5682/postscript.html
> http://www.cs.wisc.edu/~ghost/
>
...
Well, this has its merits, reminding me of batch graphics techniques
used in the ancient days. About the only drawback i see is the
inability (true?) of modifying the image without starting the rendering
from scratch.
I will now exhibit a laughable ignorance of Postscript: Suppose
the application were a strip chart. As data become available, could
commands to draw the next line segment be sent to gs and have it draw
on the screen in ~realtime? Or is it "page granular"?
Dave
--
<----. mail-to: [EMAIL PROTECTED]
<----|===================================
<----' Zber Qnrzbaf, Srjre Qrivyf!
