- From: Cameron McCormack <cam@mcc.id.au>
- Date: Wed, 12 Jan 2011 09:35:53 +1300
- To: Brad Kemper <brad.kemper@gmail.com>, www-style list <www-style@w3.org>, public-fx@w3.org
Cameron McCormack: > I think we need to carefully think about what parameters the filters > are allowed to expose; we obviously don’t want this to turn into a > general templating solution. Having said that, it might be worth looking at all of the SVG definition- like elements to see whether they would fit well with a simple value parameterisation like this, or whether SVG Parameters would solve this problem. My concern about parameterised content is that it stays simple enough that implementations don’t need to basically clone the whole subtree for every different instantiation, resulting in high memory usage. I think this is why the SVG <use> element has had slow adoption: its content is parametric in all of its inherited style, and the simple implementation is one that clones the subtree and keeps it in sync with the original. Part of the reason for <use>’s existince was to allow symbols to be drawn without their DOMs being duplicated for each instance, but its implementation complexity holds this back. If our parameterisation works only on a very focussed set of values, then that could help implementors avoid the naive solution. -- Cameron McCormack ≝ http://mcc.id.au/
Received on Tuesday, 11 January 2011 20:36:33 UTC