On Thursday, October 4, 2007, 3:05:51 AM, bulia wrote:
bb> On 10/3/07, Jon A. Cruz <jon@...18...> wrote:
So there is long-term intention to leverage that SVG feature, but it won't become user visible until a new UI is working. So to an end user it might appear that one feature goes away and then a new feature shows up after.
bb> Can you name a user-visible feature that can only be enabled by bb> gradient sharing and not by CSS style sharing? In other words, why bb> spend time on gradients when we can work on something more general and bb> powerful instead?
SVG Tiny 1.1, and SVG Tiny 1.2, don't use CSS selectors and don't support the style attribute, style element, or external style sheets. Instead they use presentational attributes. So an SVG Tiny file can share gradients.
However.
From an authoring perspective, there is nothing wrong with creating named, shared styles, and then (at save/export time) choosing between exporting them as CSS or as presentational attributes, just like one chooses between pure SVG and inkscape-roundtrippable SVG now.
(An option to use presentational attributes would make inkscape usable for mobile web development, and I would strongly encourage adding that feature. Since inkscape doesn't seem to use any tricksy features of the style attribute like repeated property assignments, mixing shorthand and non-shorthand versions of the same property, inline comments, etc it should be straightforward).