[x3d-public] C# opportunities, X3DJSONLD/JS or XSLT

[John Carlson]

https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/content/examples/HelloWorld.x3d

Nothing to prove, just trying to provide people with well documented
examples of c# SAI.  Obviously, we don’t actually need 3900+ files
converted from XML to C# except as test cases/examples for the C# SAI.

X_ITE does scripts very well, last I checked.   Please file bug reports as
necessary.

I am not an X3d player vendor nor am I a SAI vendor.   My focus is
primarily on JSON validation, loading and export from DOM to other
encodings and bindings, primarily.

I am not sure how I got into Cwhatever, except by opening my mouth too much.

Doing Cwhatever can hopefully bring in a large community who are not going
to be doing X3D otherwise.

I will remain focused on c/c++ seriizing with JavaScript as I am able, and
hope someone after me can do the c#.

My approach is mostly a test-driven approach.

John

On Mon, Mar 21, 2022 at 1:21 PM Joseph D Williams <joedwil at earthlink.net>
wrote:

>
>    - perhaps starting with HelloWorld.x3d is a tradition?
>
>
>
> If that simple, then list it here, Please.
>
> Whatever it is, I don’t see much difference between proving ecmascript or
> java and proving Cwhatever works. In any case, the proof is that  in the
> environment in which the Cwhatever can be executed, that it can use the
> full set of SAI abstract interfaces in the complete life cycle of a browser
> and scene.
>
>
>
> Level 1a: Seems like the first step might be finding an example .x3d file
> that includes an internal script node and replacing with code to be
> evaluated, run the thing in the target aspiring x3d browser, and document
> the result. Should be same as ecma or java.
>
> One is the original Boxman that uses script to move the skin. This would
> prove that the x3d browser can support an official x3d script node encoded
> using Cwhatever.
>
> I think this testing should work in free-standing browsers that support
> the whatever script language but Note, this might be complicated or
> impossible to do with an ‘internal’ script when x3d user code is embedded
> in html dom(?).
>
>
>
> Level 1b: If it is a .x3d file containing canonical, validated x3d xml or
> classic syntax,  then the converted file might be the .x3d file that
> contains a scene initialize script node that creates the scene by
> generating the xml or classic user code to create the scene, and runs it.
>
> In freestanding x3d browser, for me, you wouldn’t even need to have the
> init script generate anything but the absolute minimum xml or classic user
> code, just that the scene gets built by the init script.
>
>
>
> Level 2: scene interface with host xnl dom or javascript host hosted by
> xml dom where external and/or internal sai is not fully supported. Here
> there be questions that have been asked over the ages. Interface structures
> and behaviors between xml dom and x3d sai
>
>
>
> Thanks and Best Funs,
>
> Joe
>
>
>
>
>
>
>
>
>
> *From: *John Carlson <yottzumm at gmail.com>
> *Sent: *Monday, March 21, 2022 8:05 AM
> *To: *Joseph D Williams <joedwil at earthlink.net>
> *Cc: *X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject: *Re: [x3d-public] C# opportunities, X3DJSONLD/JS or XSLT
>
>
>
> Pick any XML you like, but perhaps starting with HelloWorld.x3d is a
> tradition?
>
>
>
> Thanks!
>
>
>
> John
>
>
>
> On Sun, Mar 20, 2022 at 7:15 PM Joseph D Williams <joedwil at earthlink.net>
> wrote:
>
>
>
>    - The goal is to convert 3000+ xml documents to c#.
>
>
>
> Please show me the first one you wish to convert.
>
>
>
> Thanks,
>
> Joe
>
>
>
>
>
> *From: *John Carlson <yottzumm at gmail.com>
> *Sent: *Sunday, March 20, 2022 12:52 PM
> *To: *X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject: *[x3d-public] C# opportunities, X3DJSONLD/JS or XSLT
>
>
>
> There is an opportunity for a C#/JavaScript/XSLT programmer to contribute
> to X3D.
>
>
>
> We would like to serialize SAI C# code from DOM documents, using
> JavaScript.  There are examples to follow, including Java, C and C++
> serializers (perhaps c/c++ are incomplete)
>
>
>
> Alternatively, we could write XSLT instead of JavaScript.  We have many
> examples to follow, including Python.
>
>
>
> Alternatively, we could write C# instead of XSLT or JavaScript.
>
>
>
> The goal is to convert 3000+ xml documents to c#.
>
>
>
> John
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20220321/729fd7c7/attachment.html>