Path: utzoo!utgpu!jarvis.csri.toronto.edu!daemon
Newsgroups: comp.lang.postscript
From: thomson@hub.toronto.edu (Brian Thomson)
Subject: Re: Drawing lots of triangles
Message-ID: <9001191633.AA17445@beaches.hub.toronto.edu>
Sender: <daemon>
Organization: University of Toronto
References: <9561@batcomputer.tn.cornell.edu>
Distribution: na
Date: 19 Jan 90 16:39:19 GMT
Lines: 33

In article <9561@batcomputer.tn.cornell.edu> eric@geology.tn.cornell.edu writes:
>/NP {newpath} def /SD {setdash} def /SG {99 div setgray} def /MT {moveto} def
>/LT {lineto} def /CP {closepath} def /GS {gsave} def /FL {fill} def
>/GR {grestore} def /SK {stroke} def /LW {setlinewidth} def
>[... other graphics stuff deleted, triangles follow]
> NP 8761 6576 MT
>8781 6584 LT
>8782 6574 LT
>8761 6576 LT
>CP GS 99 SG FL GR
>... about 180,000 times

I don't think anyone has yet suggested another way to lower the
transmission costs: the triangles are all small, so use relative motion 
when drawing them.  Combined with other suggestions, we get

 NP 8761 6576 MT
 8781 6584 LT
 8782 6574 LT
 8761 6576 LT
 CP GS 99 SG FL GR

turning into

/SG { 99 div setgray } bind def
/T { newpath moveto rlineto rlineto closepath fill } bind def
...
99 SG
1 -10 20 8 8761 6576 T
etc.
-- 
		    Brian Thomson,	    CSRI Univ. of Toronto
		    utcsri!uthub!thomson, thomson@hub.toronto.edu