[x3d-public] Chisel Codebase Again Available

[John Carlson]

It would seem very easy to create an X3D -> classic VRML conversion on
input with chisel using conversion tools in X3DJSAIL.   Perhaps more
difficult would be to add a VRML parser, but chisel or Xj3d should have one.

I would advocate for converting XML to JSON in the web browser before this.

We could probably add VRML to XML fairly easily, if we have the VRML object
model in chisel—just add toX3D() or some such.  Perhaps we could adopt a
<fill in the blank> to X3D approach.   I do not know where to start—there
seem to be many choices.

What I would advocate is developing a library of importers an exporters
that we could pass to a scenegraph.   I believe this is the best design.

So instead of set/get everywhere in the API, one would have importers that
one would pass to the X3D constructor and a method you could pass exporters
to in the X3D class in X3DJSAIL.   so there would be a method
toFile(Exporter). for example.

Thus a simple translation from VRML to X3D might entail:

VRMLImporter vi = new VRMLImporter(file or string);

X3D x = new X3D(vi);

 X3DExporter xe = new X3DExporter(file or string builder);

x.export(xe);

Let me know what volunteer positions are available for chisel.  I normally
focus on creating test cases and testing and automated testing.

John
On Sun, Jan 24, 2021 at 12:37 PM Don Brutzman <brutzman at nps.edu> wrote:

> Blast from the past: Chisel tool still works on VRML and ClassicVRML.  Can
> we upgrade it?
>
> [1]     X3D Resources, Conversions and Translation Tools: Chisel
>
> https://www.web3d.org/x3d/content/examples/X3dResources.html#Chisel
>
> "15. Chisel VRML Optimisation Tool with autoinstaller and documentation
> provided by Halden Virtual Reality Centre. Originally built by Trapezium
> and maintained by NIST."
>
> Thanks to Michael Louka's careful stewardship over many years, am happy to
> report that this Java codebase - dating to the earliest days of VRML97 and
> the Web3D Consortium - is *again available and still runs*.  Way cool.
>
> [2]     Sourceforge, Web3D Consortium open source, X3D tools, Chisel
>
> https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/tools/chisel
>
> https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/tools/chisel/test/HelloWorldScreenshotChisel.png
>
> Subversion checkout:
>
> [3]     https://svn.code.sf.net/p/x3d/code/www.web3d.org/x3d/tools/chisel
>
>  From recent evaluation email by me:
>
> > Good news: Michael has maintained this Java codebase locally, still runs
> it occasionally, and is willing to give it back for maintenance openly
> under Web3D Consortium's public infrastructure.  Am guessing this might
> take a few months to become more sharable and actionable, we'll see.  All
> of the planning and work will be reported on the x3d-public mailing list,
> hopefully attracting a contributor or two.
> >
> > I tried running this (fairly ancient) installer on my Windows machine -
> installing for invocation with a modern java failed (earlier jar files no
> longer have same structure) but installing Chisel "as is" with bundled Java
> 1.6 worked.  8)
> >
> > If you can get Chisel running on one of your systems, it is likely worth
> trying on one of the VRML your models in order to get a sense of what might
> be possible.  Model reduction workflow is (X3D -> VRML -> chiseled VRML ->
> X3D) in order to retain all original model metadata.  Chisel data-reduction
> algorithms work on model geometry (vertices and indices), colors and
> animations.
> >
> > I just ran Chisel to good effect on my second machine, reducing a legacy
> (Shay D Pixel) 1.5MB VRML model to 450K.  Not bad "out of the box" result.
> Will attach result in next message.
>
> [4]     X3D Example Archives: X3D4AM, X3D for Advanced Modeling, Shay D
> Pixel, Shay D Pixel Version 2
>
> http://x3dgraphics.com/examples/X3dForAdvancedModeling/ShayDPixel/ShayDPixelVersion2Index.html
>
> http://x3dgraphics.com/examples/X3dForAdvancedModeling/ShayDPixel/ShayDPixelVersion2.wrl
>
> > The 3D model size-reduction arena will remain a common challenge (as it
> has for over 20 years) and so continues to be worth pursuing.  I don't
> expect any quick fixes, but am optimistic that we will get Chisel
> restored.  No doubt can upgrade Chisel to .x3d XML encoding as well as .wrl
> VRML97 and .x3dv ClassicVRML encodings.  Will probably be able to make it
> part of X3DJSAIL tool chain as well.  Given our emphasis on backwards
> compatibility while evolving VRML97 through many versions of X3D, each of
> the many Chisel techniques are expected to still be viable.
>
> So this is an exciting development!  Who is interested in helping? Hoping
> we can plan a meeting to plan partnered work on renewed work.
>
> 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
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210125/4db199d4/attachment-0001.html>