🚀 go-pugleaf

In article <50851@bbn.COM> cosell@BBN.COM (Bernie Cosell) writes:
>I'm a pretty rotten PostScript programmer: although I can get my stuff work
>and it isn't too hard to read or debug, it is invariably BEASTLY slow.
 ....
>Anyhow, how best to speed it up?  I've played with the following ideas.
>
 ....
>    3) The UNIX program knows what the entire "gray palette" that it'll need
>       is before it starts out.  Is there some way to "prebuild" a
>       'sample square' of each shade of gray and have "box" just become
>       "dump the square <there>", instad of having to calculate and fill
>       the square each time?

This looks like a case for building a font with a few square "characters"
and letting postscript cache them.

It seems that with an alphabet of boxes in various shades of gray, you
would be able to do what you want and let the most optimized part of
postscript do the work for you.


-- 
Kevin O'Gorman ( kevin@kosman.UUCP, kevin%kosman.uucp@nrc.com )
voice: 805-984-8042 Vital Computer Systems, 5115 Beachcomber, Oxnard, CA  93035
Non-Disclaimer: my boss is me, and he stands behind everything I say.