On Monday, July 30, 2007, 5:23:33 AM, MenTaLguY wrote:
M> On Fri, 2007-07-27 at 17:57 -0400, Nicholas Bishop wrote:
In the UI it would show the filter name (it's an abstraction to the user) but behind the scenes it would probably be a copy of the filter structure connected to the rest of the real primitives implementing a "higher level" filter. You understand what I mean?
Certainly an interesting suggestion, but this probably falls in to the "if I have time" category.
M> I think what we'd really want for this would be an 'feFilter' primitive M> which allowed one to xlink:href another filter. That would also allow M> us to have per-object filters much the same way we have per-object M> gradients.
Both filters and gradients allow this sort of chaining (to arbitrary depth). Its supposed to promote re-use, with one filter or gradient being slightly modified (subclassed, kinda) for multiple objects.
In practice objectBoundingBox get you most of what's needed there and in 1.2 the filter region extensions also help with really reusable as opposed to subclassable filters: http://www.w3.org/TR/2007/WD-SVGFilter12-20070501/#filter-margins
SVG 1.2 filters module in fact deprecates using xlink href (on the grounds of increased implementor complexity for little practical gain); if you have views either for or against such deprecation it would be useful to hear them. http://www.w3.org/TR/2007/WD-SVGFilter12-20070501/#FilterElementHrefAttribut...