[x3d-public] X3DJSAIL updates

[John Carlson]

I've been working in the www.web3d.org/x3d/Stylesheets folder with
HelloWorldProgramOutput.java from the test-nashorn build target.   See
outputs in nashorn/examples.   Please remember to patch the code if you
haven't.   I haven't checked if you've patched or not.  I can provide
another patch if necessary.

The intermediate file has an issue once you run the build target.   I have
not reproduced it anywhere else.

John
John

On Dec 16, 2017 11:44 PM, "Don Brutzman" <brutzman at nps.edu> wrote:

> Detoured today to fix some discovered problems:
>
> - bug fixes for proper handling of ProtoInstance USE and containerField,
> - do not wrap CDATA blocks around input script text to .setSourceCode(),
> fixed in several places,
> - detailed debugging and additional tests when "smoke testing",
> -comments precede children nodes in XML encoding for readability,
> - rename level -> indentLevel,
> - improved project description.
>
>         X3D Java Scene Access Interface Library (X3DJSAIL)
>         http://www.web3d.org/specifications/java/X3DJSAIL.html
>
> Sorry not able to work on X3dToJson.xslt debugging yet... these fixes took
> all day.  Rather than working within big codebase, might we focus on
> stylesheet conversion of one or more prior example .x3d scenes?  That is
> how X3DJSAIL produces .json outputs.
>
> Inspection of X3dToJson.xslt didn't reveal any use of backslashes for path
> separators.
>
> Please identify one or two or three .x3d scenes that illustrate the
> general quoting and backslash issues that you've identified for JSON.
> Focusing on those should help us resolve these gotchas. Thanks John.
>
>
>
> On 12/10/2017 7:25 PM, John Carlson wrote:
>
>> Issue 2 is the folder separator specification which becomes \ in the
>> JavaScript, which isn’t acceptable JavaScript it appears.
>>
>
> On 12/9/2017 10:02 PM, Don Brutzman wrote:
>
>> On 12/6/2017 5:38 AM, John Carlson wrote:
>>
>>> So I would like to port X3DJSAIL to the web.   To do this, I need to
>>> identify pain points in porting Java to the web, namely File, Properties,
>>> advanced stylesheet usage, and perhaps others not yet available on the
>>> web.  In those cases, I would like to create another version of X3DJSAIL
>>> which is more portable.   Then I would like to use Jsweet or J2TS to
>>> convert from Java to TypeScript and then JavaScript.
>>>
>>> Does anyone else want this eunucized X3DJSAIL and can help?
>>>
>>
>> John thanks for asking and your persistent tracking of
>> issues/improvements, am definitely interesting to keep progressing.  Thanks
>> also for the discussion this morning.
>>
>> Am back from 2 weeks travel, will be able to slowly get sorted out back
>> at work.
>>
>> Priorities for X3DJSAIL over the next week: finish EXI support (adding
>> OpenEXI as alternative to already-working EXIficient) and integrating your
>> recommended patches.
>>
>> Today added fromZIP and fromGZIP load methods on X3DObject.
>>
>> Topics for the upcoming meeting should include how X3DJSAIL, X3DJSONLD
>> and X3D JSON/Java/Python development can continue to progress in a
>> complementary, mutually beneficial fashion.  This work also helps SAI and
>> X3D Unified Object Model efforts.
>>
>> For anyone else interested, we have scheduled a meeting to follow up on
>> John's suggested inquiry.
>>
>>      X3DJSAIL review, issues, planning
>>      Tuesday December 19, 1030-1200 pacific
>>      Web3D teleconference line
>>      http://www.web3d.org/member/teleconference-information
>>
>> Community participants interested in joining us are welcome.  If so, then
>> please advise and then can provide connection information... as well as an
>> enthusiastic suggestion to
>>
>>      Join the Web3D Consortium
>>      http://www.web3d.org/join
>>
>> Thanks for all interest and activity with X3DJSAIL.
>>
>> ============================================================
>> =================
>> X3D Java Scene Access Interface Library (X3DJSAIL)
>> X3DJSAIL supports programmers with standards-based X3D Java interfaces
>> and objects, all as open source.
>>
>> X3DJSAIL, the X3D Java Scene Access Interface Library is a set of
>> strongly typed Java application programming interfaces (APIs) providing
>> programmer access to an X3D scene graph. Two open-source Java packages are
>> included that contain X3D SAI interfaces and support the X3D Standards for
>> Java programmers.
>>
>>      org.web3d.x3d.jsail provides concrete implementation-oriented
>> classes for building X3D scenes using standalone Java objects.
>>      org.web3d.x3d.sai    contains standard X3D SAI interfaces to
>> independently compile Script-node source for use in X3D players.
>>
>> Available products include Javadoc, source code, build support, run-time
>> jar archives, several thousand self-validating examples, and draft
>> specification annexes for both node interfaces and abstract-node type
>> interfaces.
>>
>> Goals include making it easy to create an X3D scene graph using Java,
>> while also making it hard to create an incorrect or invalid X3D model.
>> That design goal is successfully met with further progress continuing.
>>
>> Multiple uses are intended for these libraries.
>>
>>      Create high-performance standalone Java applications using a Plain
>> Old Java Object (POJO) implementation for X3D.
>>      Compiling Java source code used in X3D Script nodes.
>>      Future: serve as a design template for planned autogeneration of
>> similar codebases using ECMAScript, C++/C# and Python programming languages.
>> ============================================================
>> =================
>>
>> Have fun with X3D programming!  8)
>>
> 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/brutzma
> n
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20171217/a961da71/attachment.html>