[x3d-public] Deleting portions of X3DJSONLD. Anyone using them? Request for subdividing sphere in X3D standard.

[Don Brutzman]

you know best John.  certainly eval() is dangerous.

On 12/31/2017 3:32 PM, John Carlson wrote:
> Don, frankly I am concerned about abuses of the code.   I do not want to run others Scripts.   This may seems a bit obtuse with the browser sandbox, but I also run within node.js.   likely I could turn off eval on the server side in separate code, but since others are using my code, I don't want to open them up to attack without their knowledge.
> 
> On Dec 31, 2017 4:26 PM, "Don Brutzman" <brutzman at nps.edu <mailto:brutzman at nps.edu>> wrote:
> 
>     John, thanks for asking.
> 
>     I recommend not summarily deleting per se, but rather consider moving into an archive tree or "parking lot" side tree for potential consideration (or even use) in the future.  As we've each seen, often our comprehension and understanding deepens as we work through problems.
> 
>     As you think best - you are closest to the source code and have best perspective on potential future value of partial efforts.
> 
>     On 12/30/2017 9:24 PM, John Carlson wrote:
> 
>         I am considering deleting portions of X3DJSONLD, particularly X3DJSONLD/src/main/node/Script.js, and the portions of X3DJSONLD/src/main/node/loaderJQuery.js which use Script.js to convert X3D ECMAScripts to HTML Scripts for X3DOM—This only partially worked anyway, on several of my scripts. I suggest looking towards how X3DOM already handles scripting, or perhaps using X_ITE.  I do not like eval’ing externally provided script code—it makes me dang nervous—and pushing a CDATA section into a X3D XML Script element is preferable to me (handing off the issue I guess), thus I will try to continue to support X_ITE.   This likely means we will never see Protos fully implemented in X3DOM (Is anyone crying?). Thus we will have an X3DJSONLD based X3DOM ProtoExpander without X3D ECMAScripts fully implemented.
> 
> 
>     uh we've been crying vainly for X3DOM prototyps a long time!  certainly someone can be trying in 2018.  There are many implementations out there, notably including X_ITE (thanks Holger!) so multiple existence proofs plus a grunch of examples show it isn't impossible.
> 
>     Inline Script profiles/components IMPORT/EXPORT and Prototypes all provide the X in X3D: Extensibility.
> 
>         Any feedback on this? I fully support Declarative Graphics, and suggest we get someway to generate pseudorandom numbers declaratively.   They are useful in my scripts, and I don’t know how to do it outside a script yet.  I am pretty much limited to X_ITE for Protos and Scripts on the web.  Now that X_ITE implements shaders, I have less use for X3DOM, but subdividing a surface like a sphere in various ways (ala Blender) would be useful in the X3D standard to me.   I would use it as a shortcut to defining an IFS which estimates a sphere.  Which I probably need to do to unify my shader code.  I don’t really want to store the IFS in code.  Thanks.
> 
>         John
> 
> 
>     Sphere tessellation is a perennial interesting graphics challenge.  You can find some Icosahedron examples (with lots of meta links) produced by Meshlab at
> 
>              X3D Example Archives: X3D for Advanced Modeling, Geometric Shapes
>     http://x3dgraphics.com/examples/X3dForAdvancedModeling/GeometricShapes <http://x3dgraphics.com/examples/X3dForAdvancedModeling/GeometricShapes>
> 
>     Meanwhile there is a lot of example code out there (X3D open source players, Graphics Gems, etc. etc.) so if you find a generative routine of particular merit then that may be worth adding there.
> 
>     I'm looking forward to exploring JavaScript adaptations from X3DJSONLD within X3DJSAIL capabilities in the coming year, using Java nashorn jjs as an apparently similar/equivalent alternative to node.js execution.  Not right away... am squaring away some HAnim and BVH motion-animation import first for upcoming Korea Chapter meeting... but it will be great to pursue eventually.
> 
>     We have had a wonderfully productive year advancing X3D capabilities, with much more goodness to follow.  Thanks for your many contributions to this stellar group endeavor.
> 
>     Happy 2018 with X3D!  8)
> 
>     all the best, Don
>     -- 
>     Don Brutzman  Naval Postgraduate School, Code USW/Br brutzman at nps.edu <mailto:brutzman at nps.edu>
>     Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 <tel:%2B1.831.656.2149>
>     X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman <http://faculty.nps.edu/brutzman>
> 


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