|Bezaire, Benoit||Mar 12, 2008 1:39 pm|
|Lofton Henderson||Mar 13, 2008 9:42 am|
|Bezaire, Benoit||Mar 13, 2008 10:48 am|
|Lofton Henderson||Mar 13, 2008 1:56 pm|
|Bezaire, Benoit||Mar 14, 2008 6:29 am|
|Lofton Henderson||Mar 15, 2008 9:25 am|
|Weidenbrueck, Dieter||Mar 16, 2008 10:28 am|
|Lofton Henderson||Mar 16, 2008 12:59 pm|
|Weidenbrueck, Dieter||Mar 17, 2008 1:14 am|
|Weidenbrueck, Dieter||Mar 17, 2008 1:38 am|
|Bezaire, Benoit||Mar 17, 2008 6:52 am|
|Lofton Henderson||Mar 17, 2008 5:50 pm|
|Lofton Henderson||Mar 17, 2008 5:55 pm|
|Subject:||RE: [cgmo-webcgm] 'grnode' fixes|
|From:||Lofton Henderson (lof...@rockynet.com)|
|Date:||Mar 17, 2008 5:55:34 pm|
At 04:39 AM 3/17/2008 -0400, Weidenbrueck, Dieter wrote:
Should getAppStructureById work for 'grnode's?
Yes, it should. This is the only way how an external application could get a complete list of IDs used in the CGM, e.g. to provide a new unique ID for the object that will be created next.
Sounds reasonable upon first quick reading.
This whole question is getting bigger than some simple clarifications in the text -- see next message from me. It will have to be dealt with as an issue during CD01 review, I think. It may be as simple as an erratum to clarify text, or may be different functional behavior for 2.1 DOM.
From: Bezaire, Benoit [mailto:bbez...@ptc.com] Sent: Mittwoch, 12. März 2008 19:52 To: CGM Open WebCGM TC Subject: [cgmo-webcgm] 'grnode' fixes Hi All,
I think section 188.8.131.52 describes well our intent. 'grnode's cannot have any APS attribute other than the id but can contain geometry. In section 5.7.10 we say that a 'grnode' cannot be the target of an event. We say that partially because we don't want 'grnode's to be exposed too much. Ok.
But then there's the problem of tree traversal. Where we need to have access to grnodes to access child elements. And that raises a few questions about other APIs in the specification. Ex:
Should getAppStructureById work for 'grnode's? Can I apply styles to 'grnodes', they are not attributes after all?
I'd like to propose the following changes:
-remove in section 5.3: 'grnode' elements are not accessible via DOM calls. Reason: they are accessible via .nextSibling, .firstChild etc... -add to the first para of 5.7.6: The WebCGMAppStructure interface has limited impact on Application Structures of type @grnode. Please see each method for more detail. -add to getAppStructureAttr Return value: The returned value is always an empty string for APS of type 'grnode'. -add to setAppStructureAttr: This method has no effect on APS of type 'grnode'. -add to removeAppStructureAttr: This method has no effect on APS of type 'grnode'.
and now the tricky ones ;-)
-I think we should allow style properties on 'grnode'. -I think we should allow toNodeList on 'grnode' -I think getExtent should be allowed on 'grnode'.
I don't feel strongly about the last three. I simply think it is a clear model: 'grnode' can contain geometry, therefore it has an extent and you can style its content. If people don't like it, I can be convinced otherwise.