- From: Nikos Andronikos via GitHub <sysbot+gh@w3.org>
- Date: Sun, 07 Aug 2016 11:09:56 +0000
- To: public-svg-issues@w3.org
nikosandronikos has just labeled an issue for https://github.com/w3c/svgwg as "DoC_positiveResponse": == Use a single-case name for meshGradient == As explained in #140, we've opted to separate out the paint server aspect of mesh gradients from the renderable graphics aspect. Currently, the draft uses `<meshGradient>` and `<mesh>` respectively, but the camelCased `<meshGradient>` contradicts with the working group's commitment to not introduce new camelCase names (as discussed in #161). @nikosandronikos has argued against the name `<meshgradient>` *without* camelCase (and I agree with him), because of inconsistency with the existing `<linearGradient>` and `<radialGradient>`. It's confusing enough that we have some camelCase and some single-case names, without having them so similar as well. So we need a new name. Again, we're using the name `<mesh>` for an element that creates a painted shape on screen, the missing name is for the element that defines the shape and color stops. My best recommendation: `<meshgrid>`. I think that makes clear that this is the element that contains `<meshrow>`s of `<meshpatch>`es. See https://github.com/w3c/svgwg/issues/181
Received on Sunday, 7 August 2016 11:10:05 UTC