'grnode' fixes

["Bezaire, Benoit" <bbezaire@ptc.com>]

Hi All,

 

I think section 3.2.1.5 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.

 

Thoughts?

Ben