[x3d-public] Fwd: Re: PROTO Usefulness Question -- support cobweb!

[John Carlson]

Initial script support that runs after the proto expander is here:
https://github.com/coderextreme/X3DJSONLD/blob/master/Script.js It's by no
means complete. PrototypeExpander.js is currently in development but passes
many tests in same repository.    There's a client and server side
component in the same file.  I am deprecating ServerPrototypeExpander.js.
PPP.js runs the server and client prototype expanders and produces JSON
output from input JSON.  runppp.sh is an example of running PPP.js against
several files (linux and mac shell script).

I think if a proto expander were to make proper use of id and class
attributes, it could be easily be integrated into an html5 environment w/o
scripts, and html5 scripts could be added to manipulate it.  We probably
need a standard for generating id and class from @DEF @name and @USE.

The client-side prototype expander may be run here:
http://coderextreme.net/X3DJSONLD/  Server-side (extern protos) is not
included at this time.

I do think we can leverage Cobweb's script support, but I haven't looked at
it yet, so I'm no expert.  If we had JSON and Cobweb together in the same
package it might be the best of breed.   JSON -> XML -> Cobweb already
works well for prototypes and scripts without the above code.  I am looking
forward to full integration when the X3D JSON standard arrives, so inlines
are handled better.

In other words, let's support cobweb even though it's the newcomer to the
block.  Then we don't even need a proto expander and we can focus on more
important areas, like finalizing full JSON support in all packages.

My thoughts.  My intention is for my code to disappear.  It's a proof of
concept.

John
On Jun 3, 2016 2:57 AM, "John Carlson" <yottzumm at gmail.com> wrote:

I also think it's feasible to write a proto expander with script node
support.  I'm just not smart enough to do it by myself with little X3D
experience or knowledge.  I'm slowly getting there.
On Jun 3, 2016 2:48 AM, "John Carlson" <yottzumm at gmail.com> wrote:

In other words, let's leverage the advantages that the upcoming JSON
encoding gives us for V4
On Jun 3, 2016 2:44 AM, "John Carlson" <yottzumm at gmail.com> wrote:

> I think scripts can be used if the XML encoding is not preferred or we use
> a different tag for scripts.  We can use DOM without using the XML encoding
> as well.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160603/30c77c37/attachment-0001.html>