<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 replacing this code.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think working on the to typescript is the best approach. Will continue pursuing that.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>FYI.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</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:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Friday, June 2, 2017 6:33 AM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>RE: X3DObjectUtil for X3DJSAIL</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>To see what is happening my repository is here:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>git clone <a href="https://github.com/coderextreme/JavaSceneAuthoringInterfaceLibrary">https://github.com/coderextreme/JavaSceneAuthoringInterfaceLibrary</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Run run.sh to start Jetty, etc.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You can edit run.sh to see what is going on. Then run<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>sh run.sh<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>You need maven3, shell (or run by hand) and perl for a good compile and run. Everything else will be installed by maven3.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></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<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Sent: </b>Friday, June 2, 2017 6:14 AM<br><b>To: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>RE: X3DObjectUtil for X3DJSAIL<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As an example of the problem I’m having when compiling with Dragome, I include this exception.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Here is my main code:<o:p></o:p></p><p class=MsoNormal> ConfigurationProperties.setXsltEngine(ConfigurationProperties.XSLT_ENGINE_nativeJava);<o:p></o:p></p><p class=MsoNormal> X3DObject exampleObject = new abox().getX3dModel();<o:p></o:p></p><p class=MsoNormal> String validationResults = exampleObject.validationReport();<o:p></o:p></p><p class=MsoNormal> label.setValue(helloWorldService.getGreetingsFor(validationResults));<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I will check in my changes for you to look into. I think the problem may be with xmlvm’s XSLT stylesheet. Hmm.<o:p></o:p></p><p class=MsoNormal><br>Dragome compiles bytecode to JavaScript and I am including saxon in the classpath.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Not quite sure what the issue is at this point. Will investigate xmlvm. I may not have the latest release.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Compiling classes: .............................................................................................................Exception in thread "Thread-15" java.lang.IncompatibleClassChangeError: Implementing class<o:p></o:p></p><p class=MsoNormal> at java.lang.ClassLoader.defineClass1(Native Method)<o:p></o:p></p><p class=MsoNormal> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)<o:p></o:p></p><p class=MsoNormal> at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)<o:p></o:p></p><p class=MsoNormal> at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)<o:p></o:p></p><p class=MsoNormal> at java.net.URLClassLoader.access$100(URLClassLoader.java:73)<o:p></o:p></p><p class=MsoNormal> at java.net.URLClassLoader$1.run(URLClassLoader.java:368)<o:p></o:p></p><p class=MsoNormal> at java.net.URLClassLoader$1.run(URLClassLoader.java:362)<o:p></o:p></p><p class=MsoNormal> at java.security.AccessController.doPrivileged(Native Method)<o:p></o:p></p><p class=MsoNormal> at java.net.URLClassLoader.findClass(URLClassLoader.java:361)<o:p></o:p></p><p class=MsoNormal> at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:427)<o:p></o:p></p><p class=MsoNormal> at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:389)<o:p></o:p></p><p class=MsoNormal> at org.xmlvm.plugins.javascript.XsltRunner.runXSLT(XsltRunner.java:98)<o:p></o:p></p><p class=MsoNormal> at org.xmlvm.plugins.javascript.XsltRunner.runXSLT(XsltRunner.java:69)<o:p></o:p></p><p class=MsoNormal> at org.xmlvm.ClassToJs.transformFile(ClassToJs.java:57)<o:p></o:p></p><p class=MsoNormal> at org.xmlvm.ClassToJs.transformClassFileToJs(ClassToJs.java:72)<o:p></o:p></p><p class=MsoNormal> at com.dragome.compiler.type.TypeResolver.compile(TypeResolver.java:96)<o:p></o:p></p><p class=MsoNormal> at com.dragome.compiler.type.TypeResolver.visit(TypeResolver.java:44)<o:p></o:p></p><p class=MsoNormal> at com.dragome.compiler.Project.visitSuperTypes(Project.java:286)<o:p></o:p></p><p class=MsoNormal> at com.dragome.compiler.Project.resolve(Project.java:464)<o:p></o:p></p><p class=MsoNormal> at com.dragome.compiler.writer.Assembly.resolveNoTainting(Assembly.java:338)<o:p></o:p></p><p class=MsoNormal> at com.dragome.compiler.DragomeJsCompiler.execute(DragomeJsCompiler.java:276)<o:p></o:p></p><p class=MsoNormal> at com.dragome.compiler.DragomeJsCompiler.compile(DragomeJsCompiler.java:190)<o:p></o:p></p><p class=MsoNormal> at com.dragome.helpers.serverside.DragomeCompilerLauncher.compileWithMainClass(DragomeCompilerLauncher.java:44)<o:p></o:p></p><p class=MsoNormal> at com.dragome.serverside.compile.watchers.WatchDir.compile(WatchDir.java:261)<o:p></o:p></p><p class=MsoNormal> at com.dragome.serverside.compile.watchers.WatchDir.main(WatchDir.java:247)<o:p></o:p></p><p class=MsoNormal> at com.dragome.serverside.servlets.CompilerServlet$1.run(CompilerServlet.java:83)<o:p></o:p></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<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a><br><b>Sent: </b>Friday, June 2, 2017 2:11 AM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: X3DObjectUtil for X3DJSAIL<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Am trying to think this through.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All of the subclass/superclass relationships in X3DJSAIL are related to the X3D Abstract Spec and SAI relationships. Am reluctant to change something so fundamental into variable, it no longer seems clear.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Integration of a variety of other capabilities is expected in the future?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Why is it hard to include a .jar when you are doing development? Because of compilation of the other codebases is trying to include them in the 'transpilation' ??<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Possibly we could include a switch in the autogeneration XSLT that avoided (or commented out, or substituted) certain code in the output.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for further explanations to help understand what precise problem/goal we are dealing with.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 6/1/2017 10:22 PM, John Carlson wrote:<o:p></o:p></p><p class=MsoNormal>> You could call the superclass X3DObjectBase.java perhaps. A true service provider interface (SPI) to XSLT would be better though, I believe (not sure).<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> John<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> *From: *John Carlson <mailto:yottzumm@gmail.com><o:p></o:p></p><p class=MsoNormal>> *Sent: *Friday, June 2, 2017 12:21 AM<o:p></o:p></p><p class=MsoNormal>> *To: *Don Brutzman <mailto:brutzman@nps.edu><o:p></o:p></p><p class=MsoNormal>> *Cc: *X3D Graphics public mailing list <mailto:x3d-public@web3d.org><o:p></o:p></p><p class=MsoNormal>> *Subject: *RE: X3DObjectUtil for X3DJSAIL<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> Additionally, if I comment out the import and change the name of the exception, I get the attached errors.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> It doesn’t work without XSLT/Saxon. I would like to make the dependency optional, perhaps in a separate extension, or better SPI interface, so I can replace Saxon with something else if I want to. For example, I may want to plug in my javaSerializer, JavaScriptSerializer or PythonSerializer once converted to JavaScript (replacing to the toFile* methods).<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> I think the least invasive change is to move everything but the stylesheet stuff to a superclass.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> John<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> *From: *Don Brutzman <mailto:brutzman@nps.edu><o:p></o:p></p><p class=MsoNormal>> *Sent: *Thursday, June 1, 2017 11:39 PM<o:p></o:p></p><p class=MsoNormal>> *To: *John Carlson <mailto:yottzumm@gmail.com><o:p></o:p></p><p class=MsoNormal>> *Cc: *X3D Graphics public mailing list <mailto:x3d-public@web3d.org><o:p></o:p></p><p class=MsoNormal>> *Subject: *Re: X3DObjectUtil for X3DJSAIL<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> The x3djsail.classes.jar only has X3DJSAIL classes and stylesheets, not Saxon... in fact, not finding Saxon in the full.jar either<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> http://www.web3d.org/specifications/java/X3DJSAIL.html#Downloads<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> X3DJSAIL.3.3.classes.jar (~8MB)<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> http://www.web3d.org/specifications/java/jars/X3DJSAIL.3.3.classes.jar<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> X3DJSAIL.3.3.full.jar source, documentation, etc. (~24MB)<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> http://www.web3d.org/specifications/java/jars/X3DJSAIL.3.3.full.jar<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> If you try to invoke Saxon without classpath, you get some sort of "class not found" exception.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> We could make the code a bit smarter to give an informed exception "Saxon not available, cannot apply XSLT stylesheet transformation" instead, acting more gracefully.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> Anyway that is fine tuning. You should be good to go without saxon already.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> p.s. G'day mate! 8)<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> On 5/31/2017 4:26 PM, John Carlson wrote:<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > What we could do is subclass X3DObject and put all XSLT/Saxon related stuff in there...probably too late now. Sorry I didn't mention it sooner. Or we could superclass X3DObject and move all non-XSLT/Saxon stuff up. Basically, I'd like to create a distribution without Saxon.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Thanks!<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > John<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > John<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > On May 29, 2017 11:41 AM, "John Carlson" <yottzumm@gmail.com <mailto:yottzumm@gmail.com>> wrote:<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > I am just trying to think what to do before release, and Saxon is a big stumbling block for jsweet.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > John<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > On May 29, 2017 1:39 AM, "Don Brutzman" <brutzman@nps.edu <mailto:brutzman@nps.edu>> wrote:<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > On 5/28/2017 8:02 PM, John Carlson wrote:<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > I wonder if It would be good to create an X3DObjectUtil.java and put the conversions in there.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > There is a utility class called org.web3d.x3d.jsail.ConfigurationProperties that collects a number of capabilities.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/ConfigurationProperties.html <http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/ConfigurationProperties.html><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > "Concrete class that enables developers to set custom configuration properties when using X3D Java SAI Library (X3DJSAIL). Output serialization support is provided for indentation, X3D Canonicalization (C14N) and showing default attributes. TODO more to follow!"<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > That way we can deploy X3DObject.java with just the XML output and not the stylesheet(s).<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > New methods handleArguments and validationReport were put in X3DObject because they would tend to be used there.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Will thinking about splitting off a separate utilities class if needed at some point. So far am getting good traction by figuring out when/where functionality is needed and positioning it appropriately.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > That would make it easier to deploy to a browser, and browsers can offer alternate implementations of X3DObjectUtil.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Not sure there are any impediments or blockers at this point?<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Not sure how many HTML browsers support Java, and existing X3D players with Java support tend to have their own concrete classes. (Xj3D has three actually, can be pretty confusing.)<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > I've tried to keep X3DJSAIL as consistent as possible with X3D Java SAI, which is pretty old. Suggested changes for future specification work are collected at<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > http://www.web3d.org/specifications/java/X3DJSAIL.html#SpecificationChanges <http://www.web3d.org/specifications/java/X3DJSAIL.html#SpecificationChanges><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > http://www.web3d.org/specifications/java/X3dJavaSpecificationChangesAndIssues.txt <http://www.web3d.org/specifications/java/X3dJavaSpecificationChangesAndIssues.txt><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Let me know what you think. I think it’s a good idea to be able to not be totally reliant on the stylesheets. Plus we can put other Utils there.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Other implementation is always welcome. I'll keep adjusting the stylesheets and checking results.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Before working on duplicative functionality, it would be good to work on things that are needed. STL/PLY comes to mind, also X3D Projects Wish List.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > http://www.web3d.org/projects/wish-list <http://www.web3d.org/projects/wish-list><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > For your patches, I'd like to keep iterating on representative content problems and adapting/integrating those corrections directly into the X3DJSAIL code autogeneration.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Other utilities also welcome in this open-source asset. X3DJSAIL wish list is found at<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > http://www.web3d.org/specifications/java/X3DJSAIL.html#TODO <http://www.web3d.org/specifications/java/X3DJSAIL.html#TODO><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Future libraries will include Efficient XML Interchange (EXI) compression (OpenEXI and EXIficient), XML encryption and signature, X3D Canonicalization (C14N), etc. etc. It would be good to apply jgeom.jar for NURBS too.<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > all the best, Don<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > --<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu <mailto:brutzman@nps.edu><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 <tel:%2B1.831.656.2149><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> > X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman <http://faculty.nps.edu/brutzman><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> ><o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> all the best, Don<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> -- <o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal>> X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman<o:p></o:p></p><p class=MsoNormal>> <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don<o:p></o:p></p><p class=MsoNormal>-- <o:p></o:p></p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<o:p></o:p></p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>