<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I am not being clear perhaps. I would replace a constructor().setUSE() pair with a variable, where a lookup symbol table is constructed from DEF nodes and variable names. The variable would refer to the DEF node instead of the using a USE. I think your explanation (1) below is incomplete? What I am implying is we don’t need setUSE() in programs in most cases, we can use a symbol table for code generation to look up DEFs. I need to look up how you implemented setUSE.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You wrote: “- no apparent need to wrap SFString() in python syntax.” Yes, we do need that to avoid AttributeErrors in HelloWorld.future.py (your HelloWorld.py). See a previous email (I will reforward to the list). We are conflicting with typical SAI usage doing that however. SAI alone doesn’t work. Sorry, I haven’t been clear on my fixes. Wrapping strings, arrays, etc. stop AttributeErrrors.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You have wrapping in Java, but you don’t need it. That is the difference between Java and Python. I think you’ll discover this when you rerun perhaps, if you’ve modified or replaced my Python serializer.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If my previous email does indeed work on your system, I need to adapt my system somehow. Hmm.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Sent: </b>Monday, May 6, 2019 2:18 AM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a>; <a href="mailto:aono@tut.jp">aono@tut.jp</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: questions on X3DJSAIL usage.</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 5/4/2019 4:15 PM, John Carlson wrote:</p><p class=MsoNormal>> I’m waiting for a response on whether I should stop using setUSE() (except in cases where > 1 fields are used in a node) in programs using X3DJSAIL.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Thanks!</p><p class=MsoNormal>> </p><p class=MsoNormal>> John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hmmm, perhaps I'm not understanding your question... but here is an attempt at a simple answer. Plus some additional syntactic sugar.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1. I think a programmer utilizes setUSE() whenever you need to set a USE value on a node.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Example excerpts:</p><p class=MsoNormal>http://x3dgraphics.com/examples/X3dForWebAuthors/Chapter01TechnicalOverview</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>HelloWorld.x3d</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> <Transform translation='0 -2 0'></p><p class=MsoNormal> <Shape></p><p class=MsoNormal> <Text DEF='TextMessage' string='"Hello" "world!"'></p><p class=MsoNormal> <FontStyle justify='"MIDDLE" "MIDDLE"'/></p><p class=MsoNormal> </Text></p><p class=MsoNormal> <Appearance></p><p class=MsoNormal> <Material USE='MaterialLightBlue'/></p><p class=MsoNormal> </Appearance></p><p class=MsoNormal> </Shape></p><p class=MsoNormal> </Transform></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>HelloWorld.java</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> .addChild(new TransformObject().setTranslation(0.0f,-2.0f,0.0f)</p><p class=MsoNormal> .addChild(new ShapeObject()</p><p class=MsoNormal> .setGeometry(new TextObject("TextMessage").setString(new MFStringObject("\"Hello\" \"world!\""))</p><p class=MsoNormal> .setFontStyle(new FontStyleObject().setJustify(FontStyleObject.JUSTIFY_MIDDLE_MIDDLE)))</p><p class=MsoNormal> .setAppearance(new AppearanceObject()</p><p class=MsoNormal> .setMaterial(new MaterialObject().setUSE("MaterialLightBlue")))))));</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>HelloWorld.py</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> .addChild(Transform() \</p><p class=MsoNormal> .setTranslation(SFVec3f([0,-2,0])) \</p><p class=MsoNormal> .addChild(Shape() \</p><p class=MsoNormal> .setGeometry(Text() \</p><p class=MsoNormal> .setDEF(SFString("TextMessage")) \</p><p class=MsoNormal> .setString(MFString(["Hello","world!"])) \</p><p class=MsoNormal> .setFontStyle(FontStyle() \</p><p class=MsoNormal> .setJustify(MFString(["MIDDLE","MIDDLE"])) \</p><p class=MsoNormal> ) \</p><p class=MsoNormal> ) \</p><p class=MsoNormal> .setAppearance(Appearance() \</p><p class=MsoNormal> .setMaterial(Material() \</p><p class=MsoNormal> .setUSE(SFString("MaterialLightBlue")) \</p><p class=MsoNormal> ) \</p><p class=MsoNormal> ) \</p><p class=MsoNormal> ) \</p><p class=MsoNormal> )</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. Note that if we start putting field adjustments on the same line, the structure for .java and .py are nearly identical.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Other syntax tightening is further possible in .py version:</p><p class=MsoNormal>- no apparent need to wrap SFString() in python syntax</p><p class=MsoNormal>- I suspect that MFString() wrapping is also superfluous, hopefully we can just use ["Hello","world!"]</p><p class=MsoNormal>- Similarly might try replacing SFVec3f([0,-2,0]) with [0,-2,0] - we're getting more Pythonic now!</p><p class=MsoNormal>- indenting with two space characters makes scene-graph structure more evident.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>3. Spent the day refactoring the X3D Examples Archive projects from Netbeans plain-old freeform projects to Netbeans Java freeform projects. This doesn't limit any functionality but it does make Java experimentation much simpler... menu items now include Compile/Run/Debug options.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>4. Am further noticing from above that the following single-string .java construct</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> .setString(new MFStringObject("\"Hello\" \"world!\""))</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>is more readable as a String array instead:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> .setString(new MFStringObject(new String[] {"Hello","world!"}))</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>or even more simply as:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> .setString(new String[] {"Hello","world!"})</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Have improved X3dToJava.xslt conversions to simplify accordingly. Will rerun all java conversions tonight and hopefully redeploy Web3D example archives tomorrow. Then retest python build tomorrow night.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Also will redeploy X3DJSAIL with this improvement tonight. Have also added initial PointProperties validation for X3Dv4, included source in full.jar for IDE javadoc/debugging, and fixed a number of X3DLoaderDOM geospatial errors.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>