2014-03-28 0:00 GMT+01:00 Martin Owens <doctormo@...400...>:
My concern is that I can open an old svg file with flowed text, I can save it, I can open it, I can edit it, I can save it again and have those changes track. That at each save the file was presentable to a web browser and librsvg.
There are 2 possible approaches to this: a) compute the fallback text as a postprocessing step when saving b) compute the fallback on every write to the XML
a) will be significantly faster, especially for large text, but b) allows one to inspect the fallback in the XML editor in real time and reduces the chance of crashing during save.
The branch implements option a), but it is missing an essential piece. Currently switches are treated as groups. The switch that contains the flowtext fallback should be treated as transparent and editable as a flowtext object. This can be done by adding a sodipodi:type attribute to it and modifying some code in SPFlowtext, but in general I think this should be the default behavior for switches.
Regards, Krzysztof