[x3d-public] x3d.py roundtrip for Metadata nodes in v.3.3 and v.4.0

Tue Oct 31 23:43:30 PDT 2023

I suggest we stick to the python links on the pages you provided in this
thread, since they match this thread better.  This thread is about missing
containerFields in Metadata fields in XML output from x3d.py examples.  We
can address LOA* on another thread.  Is that ok with you?

The problem is that any XML output from x3d.py historically has not
contained containerFields.  That is what Andreas and Vince are talking
about.  If you have new result XML Metadata* output from generated python
programs+x3d.py, please share links to those python programs and the new
x3d.py, so we can generate XML and see for ourselves that x3d.py now
creates containerFields in XML.

There are no containerField’s outside of XML. x3d.py generates XML that
does not contain containerField’s especially in critical areas like HAnim,
Metadata and CubeMaps, where browsers like view3dscene may require it.
HAnim discussion are elsewhere, but related.  Understanding Vince and
Andreas say may lead to an aha moment.

There are container fields on JSON and VRML, but that is another issue.

If you have an issue with what I am saying, please read the subject of this
thread, and you will understand Andreas’ intention and Vince’s support of
Andreas.

I can look at the HTML output of the stylesheet you mention, but I would
have to create a whole new routine for processing that stylesheet or use
X3D-Edit if it embeds your changes.  Is there an  Besides, we are speaking
of XML output from x3d.py on this thread, or at least the strings returned
from the x3d.py XML methods.

We are not talking about containerField which have never been in any output
from X3dToPython.xslt that I know of.   We do not want programmers to put
an containerFields in their python programs that use x3d.py.  We want
x3d.py to put containerFields in the XML output it generates.

The problem was not with HTML output that I know of, the problem is with
XML returned by x3d.py.

I have already done the testing and Andreas and Vince have done the
testing.  You are the one who has not done the testing.

On Tue, Oct 31, 2023 at 11:33 PM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:

>
>    1. John, you are silent on whether you think the online HTML
>    pretty-print versions examples are now OK, as the email thread was
>    exploring.  Confusing.
>
>
>
>    1. John, I do understand your concern that “python links on these
>    pages producing incorrect XML output.”  The precise problem with the output
>    is unstated, however.  What is incorrect?
>
>
>
> Of course those converted python programs do not themselves produce XML
> output, that takes a little modification and testing by you in your
> preferred python programming environment.
>
>
> Once again: do not patch any of the stylesheets.
>
>
>
> Once again: outside of XML, do nothing with containerField entries.
>
>
>
> Once again: suggest you modify the provided Python for LOA 0 example model
> (for best simplicity) to diagnose what is incorrect.  Then look at the
> difference between original correct XML and your python-produced XML.  If
> the new result is invalid, then please show what is wrong and then I have
> something repeatable that can be fixed.
>
>
>
> Once again: If we get LOA 0 confirmed working, you can try LOA 1 and
> repeat process.
>
>
>
> Not sure that I’ve said anything new or different for lo these many
> responses I’ve provided.  Hope this is making sense.
>
>
>
> 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:* Tuesday, October 31, 2023 7:29 PM
> *To:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> *Cc:* Andreas Plesch <andreasplesch at gmail.com>; X3D Graphics public
> mailing list <x3d-public at web3d.org>; Peitso, Loren (CIV) <lepeitso at nps.edu
> >
> *Subject:* Re: [x3d-public] x3d.py roundtrip for Metadata nodes in v.3.3
> and v.4.0
>
>
>
>
>
> On Tue, Oct 31, 2023 at 8:01 PM Brutzman, Donald (Don) (CIV) <
> brutzman at nps.edu> wrote:
>
> Rather than constructing a new example, we have some existing models for
> X3D3/X3D4 Metadata nodes already in the X3D Example Archives.
>
>
>
> I looked at the HTML5 pretty-print documentation for our two sets of
> X3D3/X3D4 metadata examples.  Found a problem in X3dToXhtml.xslt conversion
> stylesheet, was able to fix it.
>
>
>
> The following examples should now all show the correct defaults:
>
>
>
>    - X3D Example Archives: X3D4WA, X3D for Web Authors, Chapter 15
>    Metadata
>    -
>    https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter15Metadata/index.html
>
>
>
>    - Metadata Node Examples X3D 3
>    - Metadata Node Examples X3D 4
>    - World Info Example Metadata Set X3D 3
>    - World Info Example Metadata Set X3D 3
>
>
>
>
>
> Don, we are concerned about the python links on these pages producing
> incorrect XML output.  Can you provide updates to x3d.py, if there are
> updates?   Otherwise, I'm afraid Andreas' and Vince's points still stand.
> We really need updates to x3d.py.  We would like to try to patch it with
> your permission. We would like to add containerFields as best as we can to
> the output of x3d.py. It's not that we can't patch output from x3d.py.  I
> hope you understand that we don't want to hand edit x3d.py output as that
> would look bad for the Web3D Consortium to produce files from x3d.py that
> required hand editing. Especially if someone is downloading x3d.py from a
> website and does not have these threads handy to to read.
>
>
>
> If you like, I can download the XML, convert to python, then produce XML
> from the python code (using x3d.py off the shelf).  But I'm afraid I will
> get the same results as Vince and Andreas.
>
>
>
> Andreas did address some of the solution.  See his link to the stylesheet
> in question, which I provide here:
> https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/X3duomToX3dPythonPackage.xslt
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fx3d%2Fcode%2FHEAD%2Ftree%2Fwww.web3d.org%2Fx3d%2Fstylesheets%2FX3duomToX3dPythonPackage.xslt&data=05%7C01%7Cbrutzman%40nps.edu%7C40be062991d041aeb27208dbda825f9d%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638344025726602652%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Hd2UVX30Ha5iQseoEGpixC5cnp1x1PvgOf5MTfaexJU%3D&reserved=0>
>
>
>
> Thanks,
>
>
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231101/ba47143f/attachment.html>