
On Fri, 2012-08-31 at 11:27 +0200, Tavmjong Bah wrote:
What I propose, is that as new features become stable, we modify the internal Inkscape code to use them while at the same time adding an option to export to SVG 1.1. In many cases, this will have the side benefit of simplifying our code. For example, matching marker color to stroke color now requires some rather complex code to create new copies of a marker for each different colored path as well as monitor changes to stroke and fill color.
What do others think?
I think that's a good idea. What I had started on a long time ago, and never finished (and it probably won't even merge today) was looking it from the perspective of profiles. I guess what I'm unsure of is "2.0 vs. 1.1" enough. Or are designers/developers of web stuff thinking more "I need to target Firefox X to Y and IE version so and so", etc. In the end that might end up dropping some features of 1.1 but adding others from 2.0. Or SVG Tiny, etc.
I realize that it makes the whole thing much more complex, but it seems like relying on the standards to version things might turn out to not be useful in the real world.
--Ted