[x3d-public] Discussion: containerField for x3d.py XML export

[Michalis Kamburelis]

I see John submitted a ticket,
https://github.com/castle-engine/view3dscene/issues/69 . As I
mentioned there, please attach or link there a testcase.

CGE/view3dscene follow the containerField specified in X3D XML
specification, https://www.web3d.org/documents/specifications/19776-1/V3.3/Part01/EncodingOfNodes.html#HAnimJoint
. Maybe the testcase just misses containerField="xxx" usage at
respective "<USE ...>" elements.

Regards,
Michalis


wt., 26 wrz 2023 o 08:01 Joe D Williams <joedwil at earthlink.net> napisał(a):
>
> > The problem is with X3DJSONLD and view3dscene assuming that children is a field of HAnimHumanoid.
>
>
>
> HAnimHumanoid includes fields.
>
> The skeleton field defines a hierarchy of Joint nodes.
>
> The first joint of the hierarchy, root, names the container field, skeleton, for the hierarchy, and is the ancestor of all other children nodes in the hierarchy.
>
> x3dv
>
>  skeleton
>
>   Joint
>
>     children
>
>       Joint ...
>
> skeleton is the container for the joint hierarchy.
>
>
>
> x3d
>
>  Joint containerfield skeleton
>
>    Joint containerfield children
>
>     ...
>
> skeleton is the containerfield for the joint hierarchy
>
>
>
> Just a guess at what you are concerned about.
>
> What is not happening? If in doubt, check the schema.
>
> Joe
>
>
>
> -----Original Message-----
> From: John Carlson <yottzumm at gmail.com>
> Sent: Sep 25, 2023 10:36 PM
> To: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> Cc: Peitso, Loren (CIV) <lepeitso at nps.edu>, X3D Graphics public mailing list <x3d-public at web3d.org>
> Subject: Re: [x3d-public] Discussion: containerField for x3d.py XML export
>
>
>
> The problem is with X3DJSONLD and view3dscene assuming that children is a field of HAnimHumanoid.
>
> That's not right!
>
> John
>
> On Sun, Sep 24, 2023 at 2:47 PM Brutzman, Donald (Don) (CIV) <brutzman at nps.edu> wrote:
>>
>> Thanks for continued troubleshooting.
>>
>>
>>
>> Please do not do anything with containerField handling in x3d.py since it is unique to XML encoding.
>>
>>
>>
>> If you encounter any incorrect handling, please provide a regular issue report that notes
>>
>> Model, in .x3d/.x3dv and also .py
>> Error or warning that was encountered, relevant tools, etc.
>>
>>
>>
>> I can then isolate the problem and fix it.  When errors do occur, it is usually an error in the scene, but sometimes a simple omission of some sort somewhere deep in the code autogeneration of the library.
>>
>>
>>
>> p.s. also thanks for your recent issue reports on X3DJSAIL, very helpful.  I have made a number of improvements this weekend, hoping to publish tonight.
>>
>>
>>
>> all the best, Don
>>
>> --
>>
>> Don Brutzman  Naval Postgraduate School, Code USW/Br        brutzman at nps.edu
>>
>> Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA    +1.831.656.2149
>>
>> X3D graphics, virtual worlds, navy robotics https://faculty.nps.edu/brutzman
>>
>>
>>
>> From: John Carlson <yottzumm at gmail.com>
>> Sent: Sunday, September 24, 2023 11:34 AM
>> To: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>; Michalis Kamburelis <michalis.kambi at gmail.com>; Peitso, Loren (CIV) <lepeitso at nps.edu>; X3D Graphics public mailing list <x3d-public at web3d.org>
>> Subject: Discussion: containerField for x3d.py XML export
>>
>>
>>
>> First of all, great work on x3d.py, Loren and Don, I feel like I am polishing a diamond.
>>
>>
>>
>> I am considering adding the containerField attribute (not field) to XML output in x3d.py. This is mainly to support requirements of view3dscene.  It complains if I don’t add the containerField attributes in HAnim (skeleton and joints containerFields, maybe more)—the default, children, is not an acceptable to view3dscene.  Also, not having a skin containerField is weird when dropping arbitrary Shape nodes into a HAnimHumanoid.
>>
>>
>>
>> Does adding the containerField attribute seem like a good idea, or should I push back on browser vendors?
>>
>>
>>
>> I plan to do something like I do for VRML when printing out joints and skeleton fields etc.  I won’t print out the containerField for obvious fields, i have a list of these somewhere…geometry, appearance, material, etc
>>
>>
>>
>> Should I allow the x3d.py app programmer to add a containerField attribute, or should I compute it as best i can, and save browser vendors the pain?
>>
>>
>>
>> I think what this means is passing an optional parameter to some each.XML() method calls.
>>
>>
>>
>> After writing this message, the answer seems obvious.
>>
>>
>>
>> Comments?
>>
>>
>>
>> John
>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org