On Sun, 2008-05-04 at 09:02 -0400, Ales Hvezda wrote: > [snip] > >Just thought I'd share a couple of screen-shots of a feature hopefully > >targeted for gEDA 1.6.0, support for closed / filled polygons. > > > > Questions, why didn't you use gdk's simple polygon API for this? > > (http://library.gnome.org/devel/gdk/2.12/gdk-Drawing-Primitives.html#gdk-draw-polygon) > > Wouldn't using that gdk call be *magnitudes* faster (during > rendering) and easier to implement (as the rest of gEDA/gaf uses gdk > quite extensively)? I am quite sensitive to users who use gEDA/gaf on > older machines and maintaining the existing rendering performance is an > important goal.
I'd not be opposed to rebasing this patch onto the existing code head, so it doesn't rely on the cairo branch. For a first approximation, we should just drop support for the Bezier path segments. I see the first applications of this code as support for reading, writing, perhaps manipulating an exiting object. That is still useful (for making a pretty symbol library), even if gschem can't do arbitrarily fancy things when editing them. (It is still useful even if we have to hand-edit the symbol files to add polygons). BTW... open path sections may give a speed win for gschem's fonts too. Still TODO: Figure out how this maps to postscript output. Presumably it is possible to translate pretty easily, but I'm no postscript guru. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user