Use native SVG objects when possible

Bug #548619 reported by David Douard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aafigure
Confirmed
Wishlist
Unassigned

Bug Description

For its SVG backend, aafigure should make use of "native" objects when possible. I am thinking mainly about:

- use arrows instead of "building" them with lines (use "marker-xxx" style attribute)

- use rectangles instead of building them with lines ("<svg:rect >")

Revision history for this message
Oliver Joos (oliver-joos) wrote :

What is the benefit? Smaller SVG files? Or are there visible errors with the current implementation?

Revision history for this message
zsquareplusc (zsquareplusc) wrote :

i see it would be an advantage when the files are processed with other software, e.g. a vector editing program.
however this is not easy to change.

arrows: possible, but protocol between parser and the rendering backends needs to be changed.

rectangles: this is would require something like a "optimizer", a processing after the images has been parsed. it would need to implement some algorithms to detect common shapes. rectangles are one example, fills would be an other (they are now made of many short lines even when they could be replaces by one long line).

Changed in aafigure:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
David Douard (david-douard) wrote :

I see many advantages. I explored the code a bit, and I also realized that this require to change protocols between parser and rendering backends. However I think it make sense to delegate to backend the task of knowing how to draw a basic shape.

I will eventually dig into that direction, if I find a bit time for it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.