- From: Bezaire, Benoit <bbezaire@ptc.com>
- Date: Thu, 8 Jan 2009 09:43:12 -0500
- To: "WebCGM WG" <public-webcgm-wg@w3.org>
- Message-ID: <D4B91172BD39D64E8799BE7ECB329A5D890FDF@HQ-MAIL3.ptcnet.ptc.com>
I remember that this was discussed... my main concern is that the current wording (or our previous decisions) seem inconsistent. ________________________________ From: public-webcgm-wg-request@w3.org [mailto:public-webcgm-wg-request@w3.org] On Behalf Of Lofton Henderson Sent: Wednesday, January 07, 2009 7:17 PM To: WebCGM WG Subject: RE: Typo in stroke-type style property One preliminary comment/observation: There is actually a direct contradiction about stroke-type. The table [1] says stroke-type can be a name or a negative integer. The text says valid values are the defined integers (and it omits negative integers.) [1] http://www.w3.org/TR/2008/WD-webcgm21-20080917/WebCGM21-DOM.html#setStyl eProperty There is some history to this issue, and I'll try to dig it out. I remember us discussing the name-versus-integer issue. And I remember extensively re-editing all of the new SP table/text stuff to reflect our resolutions. (**I think** that our intention was to go towards the simple integer-only solution, for those new SPs for which integers make sense. If that's true, any contrary implication is due to my bad editing, and the stroke-type is clearly an editing goof. I recall inserting the "corresponding to..." wording, and recall the intent as simply explaining the valid-value list [integers] in more user-friendly terms, so that one did not have to pick up a copy of CGM:1999 to understand the integer valid values.) More later. -Lofton. At 10:59 AM 1/7/2009 -0500, Bezaire, Benoit wrote: I'm reading the on the new style properties, and I see some inconsistencies. It's unclear with the current spec which style properties are set by a name or integer value. At the moment it seems like stroke-type can be set using "solid" or "1". But other style properties like interior-style and hatch-index only seem to be settable using it's integer value. I think some clarification and consistency is needed. While it's still unclear if PTC will implement getStyleProperty(), I wonder if the implementation has to return the exact same string that was used to set the attribute. Example for stroke-type: setStyleProperty("stroke-type", "solid"), getStyleProperty("stroke-type") returns 1. Example for stroke-weight: setStyleProperty("stroke-weight", "200%"), getStyleProperty("stroke-weight") returns 0.5 (assuming original was 0.25). Thoughts? Benoit. ________________________________ From: Bezaire, Benoit Sent: Wednesday, January 07, 2009 10:26 AM To: WebCGM WG Subject: Typo in stroke-type style property Current wording says: "[...] Valid values are: integers 1-6 (which correspond to solid, dash, dot, dash-dot, dash-dot-dot)", the "1-6" should be replaced by "1-5". Benoit.
Received on Thursday, 8 January 2009 14:44:17 UTC