[x3d-public] X3DJSAIL: Interesting exception, but ... tableforstringconversion examples

John Carlson yottzumm at gmail.com
Wed May 24 16:32:07 PDT 2017


And here is the result with my original patches.  The Java app hasn’t changed.

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Wednesday, May 24, 2017 7:20 PM
To: Don Brutzman; X3D Graphics public mailing list
Subject: RE: X3DJSAIL: Interesting exception, but ... tableforstringconversion examples

Okay, here is the original X3DJSAIL output from your and my programs:



Sent from Mail for Windows 10

From: John Carlson
Sent: Wednesday, May 24, 2017 7:10 PM
To: Don Brutzman; X3D Graphics public mailing list
Subject: RE: X3DJSAIL: Interesting exception, but ... table forstringconversion examples

Okay, with my patches.  Here the X3D, your and my code (same filename), and the output X3D.

I will report without patches later.

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Wednesday, May 24, 2017 2:13 PM
To: Don Brutzman
Subject: Re: X3DJSAIL: Interesting exception, but ... table for stringconversion examples

I believe the reason you cannot see the problem is because you do not use arrays for MFStrings in your app code (try with both one and two SFStrings, and a quote in the SFstring at the end).

But I could be wrong. Will try to diagnose later.

John

On May 24, 2017 12:59 PM, "John Carlson" <yottzumm at gmail.com> wrote:
The only part I see left is getting the end part of an MFString correct in all cases in XML generation, both in your code and my code. but there's probably more out there.   I recall there being a problem with MFStrings in Scripts as well, but the code was equivalent, so I left it alone.

On May 24, 2017 10:22 AM, "Don Brutzman" <brutzman at nps.edu> wrote:
OK John, thanks for persisting on this one!  Agreed very important... am thinking/hoping I finally understand the mismatch.

Conceptual error: the excess backslashes come from incorrectly trying to represent the XML value in the Java and JSON, rather than trying to represent the in-memory string array that is needed in the Java and JSON.

Possible root cause: specification -> XML -> Xpath -> XSLT -> recursion <- recursion -> .java/.json dizziness!

Email text/html awkwardness coupled with escaping of escaping of escaping hasn't helped us either.

How to regain clarity... let's build an HTML table that compares equivalences for

- value
- rendering
- XML .x3d
- ClassicVRML
- JSON
- Java

Putting it on an HTML table will help us avoid email twists that occur with reply indenting, mailer issues etc.

If the result makes sense, it will help us "zero in" on specific conversion pairs that are questionable.  If it works, will probably be useful for X3D Scene Authoring Hints.

More to follow in the next day or so...  once we get clear on each curious case, calibrating the stylesheet converters will be straightforward at this point.

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 http://faculty.nps.edu/brutzman



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170524/81e4413e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: text.don.x3d
Type: application/octet-stream
Size: 1815 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170524/81e4413e/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: text.john.x3d
Type: application/octet-stream
Size: 3406 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170524/81e4413e/attachment-0003.obj>


More information about the x3d-public mailing list