[x3d-public] [x3dom-users] Whither protoexpander in X3DOM? umm, just define input-to-output and write code

[John Carlson]

I think the big monster in the closet is whether we have to rewrite
DEF/USE/name values (for ROUTEs at least), or if we can use X3DOM's
namespaces. If we have to rewrite the values, I don't see value in
using X3DOM's infrastructure--we just hand it an expanded DOM.

John

On Wed, May 27, 2020 at 9:50 AM John Carlson <yottzumm at gmail.com> wrote:

> I see one issue with approach, but it is a good first step:
>
> In current ProtoExpander, name values, DEF/USE values are rewritten.  So
> Scripts attributes, ROUTE attributes, etc. need to be rewritten as well.
> That's only the second step.  So really, the whole scene needs be
> examined.  It will become difficult, I think, to extract the non-Inlined,
> non-ExternProtoDeclare items from the existing DOM.  So we are limited to
> Inlines, or how X_ITE does it with the URL in X3DCanvas tag. JSON is
> limited to Inlines, so limiting to Inlines is probably OK.  But we'll need
> to ask Don about his examples and converters.  Note that X3DJSONLD is not
> limited to Inlines though, but it loads JSON from files, which is
> equivalent.
>
> Suggestions?  It's good to think simple cases, but we need a holistic
> approach to design if we're going to solve this.
>
> So we have
>
> 1.  Use Inlines
> 2.  Rewrite DEF/USE/name.
>
> John
>
>
> On Tue, May 26, 2020 at 10:00 PM Don Brutzman <brutzman at nps.edu> wrote:
>
>> As discussed Monday: Prototype Expander may have general value, but
>> primary need is adding Prototype support to X3DOM.
>>
>> Recommend scrapping all options as distracting alternative future work.
>>
>> Simply focus on the X3DOM prize in JavaScript.  Path to get there is a
>> straight line:
>>
>> 1. Concept: ProtoDeclare is a template definition, ProtoInstance creates
>> a scene subgraph.
>>
>> 2. Thus the only resulting code of interest looks like X3DOM scene
>> subgraph.
>>
>> 3. Collect and create corresponding pairs of (a) inputs
>> (ProtoDeclare/ProtoInstance) and (b) outputs (X3DOM scene subgraph).
>>
>> 4. The ProtoExpander is native X3DOM javascript code reads 3(a) and
>> creates 3(b).
>>
>> ====================
>>
>> That's it.  No really.
>>
>> Recommended first model for input/output inventory: ArtDeco00, which is a
>> simple Material node.
>>
>> *
>> https://www.web3d.org/x3d/content/examples/Basic/UniversalMediaMaterials/ArtDecoPrototypesIndex.html
>> *
>> https://www.web3d.org/x3d/content/examples/Basic/UniversalMediaMaterials/ArtDecoPrototypes.json
>> *
>> https://www.web3d.org/x3d/content/examples/Basic/UniversalMediaMaterials/ArtDecoExamplesIndex.html
>> *
>> https://www.web3d.org/x3d/content/examples/Basic/UniversalMediaMaterials/ArtDecoExamples.json
>>
>> JSON input
>>
>> { "ProtoDeclare":
>>    {
>>      "@name":"ArtDeco00",
>>      "@appinfo":"UniversalMediaMaterials prototype",
>>      "@documentation":"
>> https://www.web3d.org/x3d/content/examples/Basic/UniversalMediaMaterials
>> ",
>>      "ProtoBody": {
>>          "-children":[
>>            { "Material":
>>              {
>>                "@ambientIntensity":0.25,
>>                "@diffuseColor":[0.282435,0.085159,0.134462],
>>                "@shininess":0.127273,
>>                "@specularColor":[0.276305,0.11431,0.139857]
>>              }
>>            }
>>          ]
>>      }
>>    }
>> },
>>
>> JSON result of interest:
>>
>>            { "Material":
>>              {
>>                "@ambientIntensity":0.25,
>>                "@diffuseColor":[0.282435,0.085159,0.134462],
>>                "@shininess":0.127273,
>>                "@specularColor":[0.276305,0.11431,0.139857]
>>              }
>>
>> First draft of converter: extract everything inside ProtoBody, ignore the
>> rest.
>>
>> So you are now halfway to first example.  If that is how JSON says it in
>> JavaScript, how does X3DOM say it in JavaScript?
>>
>> If still puzzled, here is a second-opinion point of comparison: how does
>> X_ITE say it?
>>
>> Have fun with X3D JavaScript, I hope...
>>
>> On 5/26/2020 9:29 AM, John Carlson wrote:
>> > There's also choice of data structure
>> >
>> > 1.  Mostly DOM/JDON, relying on functions
>> > 2.  Full X3DJSAIL-like data structure
>> > 3.  Just the Proto classes.
>> >
>> > On Tue, May 26, 2020 at 2:59 AM John Carlson <yottzumm at gmail.com
>> <mailto:yottzumm at gmail.com>> wrote:
>> >
>> >     1.  Keep current implementation, debug it
>> >     2.  Add XML -> JSON -> XML to current implementation.  Code is
>> written, but not tested extensively
>> >     3.  Write a new version in XML
>> >     4.  Copy and port X_ITE's Proto code.
>> >     5.  Write a new XML based proto expander.
>> >
>> >     We *do* want at least an XML proto expander.
>> >
>> >     Anyone want to help with any of these?  There are a lot of options.
>> >
>> >
>> >
>> > _______________________________________________
>> > X3dom-users mailing list
>> > X3dom-users at lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/x3dom-users
>> >
>>
>> 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/20200527/e5f389ad/attachment.html>