|
From: Ethan M. <merritt@u.washington.edu> - 2003-12-20 00:46:06
|
On Thursday 18 December 2003 17:15, Hans-Bernhard Broeker wrote: > I've now created a new pair of routines > > polyline3d_start() #may be renamed to *_move() > polyline3d_next() #may be renamed to *_vector() > > and use those in cntr3d_lines, instead of draw3d_line().=20 [...] > Besides the hidden3d limitation, all's looking fine so far. Just as a point of reference, here are the output sizes of=20 postscript files produces by base 3.8k before your patch, the current cvs version, and the current cvs version with my patch for post.trm from the other day. [47] wc *.ps 107936 232574 860642 3.8j.ps 63070 161130 566356 hbb.ps 44492 133191 430013 hbb+eam.ps Test command sequence was in each case: set term post color dash set output '...' load 'contours.dem' I don't know if the patch to post.trm is fully safe, but in any event this shows that there is some room left to further optimize the postscript output over and above the changes you made to the core routines. --=20 Ethan A Merritt merritt@u.washington.edu Biomolecular Structure Center Box 357742 University of Washington, Seattle, WA 98195 |