[x3d-public] FW: X3DJSAIL update: toGZIP and toZIP export

[John Carlson]

Has this patch been applied (minus the source path changes) to X3DJSAIL? I haven’t checked the source code repository yet.

Thanks,

John

Sent from Mail for Windows 10

From: John Carlson
Sent: Wednesday, November 1, 2017 4:44 AM
To: Don Brutzman; x3d-public at web3d.org
Subject: RE: [x3d-public] X3DJSAIL update: toGZIP and toZIP export

Here’s a better patch (same, but up to date).  The patch still doesn’t fix the description of the JavaScript methods, but it should work with a proper installation, running the exported JavaScript  code in X3DJSONLD/src/main/nashorn.

I have a shell script growl.sh in X3DJSONLD/src/main/nashorn that should run once X3DJSAIL is installed in ~/pythonSAI and X3DJSONLD is built so the jar containing the app is installed under X3DJSONLD/target (should be done in the build).  I just tested it.  One may need to run sh donlocal.sh in  X3DJSONLD/src/main/shell to get an up to date app, but the one checked into the java folder should work.  Growl.sh produced a JS and X3D file from a Java app which is part of X3DJSONLD (abox, I think).

What I mean was developing an equivalent source code base on source forge, so JavaScript applications can get created, If you don’t want to support a JavaScript stylesheet.

Should I put everything under the stylesheets/javascript folder?   We need to figure out which JavaScript code to take from X3DJSONLD.

But if ultimately, this is all replaced by a stylesheet, I am not interested in doing the work.  I don’t think that creating a stylesheet from the X3dToJava.xslt is that much work, I’ve done that work before, but haven’t gotten it accepted yet.  Perhaps I need to work on getting it accepted?  Do I need to sign something?  The work is plainly derivative of yours, so it would be best if it was covered under the same license.  I don’t need to add any additional license.

Apologies for the name of growl.sh.  It got that name when the code wasn’t working.  I found a bug in java.util.Scanner where it doesn’t have a token returned bigger than 4096 bytes (should be the entire JavaScript file), so I had to stop using that class.  Different regular expressions were causing a StackOverflow error (\A didn’t work).

IMWTK.

John
Sent from Mail for Windows 10

From: Don Brutzman
Sent: Tuesday, October 31, 2017 11:24 PM
To: John Carlson
Subject: Re: [x3d-public] X3DJSAIL update: toGZIP and toZIP export

On 10/31/2017 8:18 PM, John Carlson wrote:
> Should I put an example of JavaScript output from X3DJSAIL in HelloWorld?

makes sense.  is this a feature/capability to get integrated into the build?  am happy to work together on that.

or waitaminute perhaps X3DObject.toStringJavaScript() method?  Hmmm the description doesn't sound right:

http://www.web3d.org/specifications/java/javadoc/org/web3d/x3d/jsail/Core/X3DObject.html#toStringJavaScript--

"Serialize scene graph using X3dToX3dom.xslt stylesheet to create a new X3DOM html page as a string."

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/20171103/efb024c9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CreateX3DJSAI.patch
Type: application/octet-stream
Size: 2854 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20171103/efb024c9/attachment-0001.obj>