On 23.07.07, Joerg Lehmann wrote: > On 23.07.07, Michael SCHINDLER wrote: > > > > Instead of adding more features to this type of patterns, I would > > > > rather suggest to remove the feature or replace it by a more stable > > > > one (hatching "by hand": stroking many lines and then clip). In > > > > combination with parallel deformers, this can be used to create an > > > > effect such as patterning a line. > > > > > So basically we would take the bounding box of the object to determine > > > the size of the underlying "lattice" and then do it ourselves. But > > > what kind of object in the PyX class hierarchy would this then be? > > > > Right. As it takes a path and returns a canvas, it can only be a > > pyx.deco.deco. The idea is really to replace the object by the canvas > > (ornaments), thus the decoratedpath itself should be skipped (via the > > nostrokerange mechanism). > > Sounds good, so if we keep the PS/PDF native patterns, I would like this > solution.
One more thing: There have been the translateable canvases (for re-use of symbols in graphs). We might want to use that for the patterns, in order to keep the filesize small and the PS/PDF efficient. Michael. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ PyX-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyx-user
