<div dir="auto">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.<div dir="auto"><br></div><div dir="auto">Thanks!</div><div dir="auto"><br></div><div dir="auto">John<br><div dir="auto"><br></div><div dir="auto">John</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On May 29, 2017 11:41 AM, "John Carlson" <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">I am just trying to think what to do before release, and Saxon is a big stumbling block for jsweet.<div dir="auto"><br></div><div dir="auto">John</div></div><div class="gmail_extra"><br><div class="gmail_quote">On May 29, 2017 1:39 AM, "Don Brutzman" <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 5/28/2017 8:02 PM, John Carlson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I wonder if It would be good to create an X3DObjectUtil.java and put the conversions in there.<br>
</blockquote>
<br>
There is a utility class called org.web3d.x3d.jsail.Configurat<wbr>ionProperties that collects a number of capabilities.<br>
<br>
<a href="http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/ConfigurationProperties.html" rel="noreferrer" target="_blank">http://www.web3d.org/specifica<wbr>tions/java/javadoc/org/web3d/x<wbr>3d/jsail/ConfigurationProperti<wbr>es.html</a><br>
<br>
"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!"<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That way we can deploy X3DObject.java with just the XML output and not the stylesheet(s).<br>
</blockquote>
<br>
New methods handleArguments and validationReport were put in X3DObject because they would tend to be used there.<br>
<br>
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.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That would make it easier to deploy to a browser, and browsers can offer alternate implementations of X3DObjectUtil.<br>
</blockquote>
<br>
Not sure there are any impediments or blockers at this point?<br>
<br>
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.)<br>
<br>
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<br>
<br>
<a href="http://www.web3d.org/specifications/java/X3DJSAIL.html#SpecificationChanges" rel="noreferrer" target="_blank">http://www.web3d.org/specifica<wbr>tions/java/X3DJSAIL.html#Speci<wbr>ficationChanges</a><br>
<br>
<a href="http://www.web3d.org/specifications/java/X3dJavaSpecificationChangesAndIssues.txt" rel="noreferrer" target="_blank">http://www.web3d.org/specifica<wbr>tions/java/X3dJavaSpecificatio<wbr>nChangesAndIssues.txt</a><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
</blockquote>
<br>
Other implementation is always welcome. I'll keep adjusting the stylesheets and checking results.<br>
<br>
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.<br>
<br>
<a href="http://www.web3d.org/projects/wish-list" rel="noreferrer" target="_blank">http://www.web3d.org/projects/<wbr>wish-list</a><br>
<br>
For your patches, I'd like to keep iterating on representative content problems and adapting/integrating those corrections directly into the X3DJSAIL code autogeneration.<br>
<br>
Other utilities also welcome in this open-source asset. X3DJSAIL wish list is found at<br>
<br>
<a href="http://www.web3d.org/specifications/java/X3DJSAIL.html#TODO" rel="noreferrer" target="_blank">http://www.web3d.org/specifica<wbr>tions/java/X3DJSAIL.html#TODO</a><br>
<br>
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.<br>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA <a href="tel:%2B1.831.656.2149" value="+18316562149" target="_blank">+1.831.656.2149</a><br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzma<wbr>n</a><br>
</blockquote></div></div>
</blockquote></div></div>