[x3d-public] X3D V4 Draft Requirements Proposal -- Only Scripting

[Joe D Williams]

>  The key is to look for solutions, not problems.

Right, and the sollution is to have a level of interaction with the 
dom but also to not need to depend on dom for basic animations and 
sensors. Your comment shows that more than just some htmlized and 
domified syntax and scenegraph structures, and really, the signs that 
there is no need to leave anything good behind. As for browser 
built-in vs a scripting platform, I just hate to download the big 
batch of .js that approaches the size of a plugin every time. Maybe a 
web browser should be able to cache a 'standard' set of .js 
capabiities. Right now, for webgl a giant problem is that shaders need 
to be compiledevery time, thus sloiwng upthle loading. Same for 
downloaded .js.

Thanks and Best,
Joe


----- Original Message ----- 
From: "John Carlson" <yottzumm at gmail.com>
To: "Leonard Daly" <Leonard.Daly at realism.com>; "X3D Graphics public 
mailing list" <x3d-public at web3d.org>
Sent: Tuesday, March 28, 2017 1:56 PM
Subject: Re: [x3d-public] X3D V4 Draft Requirements Proposal -- Only 
Scripting


>I am not sure what the hoopla is, as far as I know, vrml scripts work 
>in
> Cobweb without changing the tagname or Inlines.   You just have to 
> load the
> file with SAI or similar.
>
> If you want to code x3d just like HTML, good luck.   Make a real 
> case for
> it.  I think there are too many examples of stuff not being 
> hard-coded into
> the browser.   While you are worried about X3D in HTML, Three.js 
> will run
> away with  a your cheese.  You might argue performance, but I would 
> say
> move towards shaders.
>
> Quit being whiny babies and work with the technology.   If you can't 
> debug
> scripts right now, you may be able to in the future.   Or use 
> Browser.print
> or console.log.   It's old school, but it works.
>
> Working with the technology may allow you to see additional 
> solutions.
>
> I have somewhat working Protos and scripts with X3DOM now (by no 
> means
> perfect, just one working example :-), because I spent the time in 
> the
> technology.  The key is to look for solutions, not problems.
>
> If you are stuck in the C++ world, work on something like jsasm.js. 
> Yes, I
> do believe that people are compiling C++ to work in webpages.
>
>
>
> John
>
> On Mar 28, 2017 1:37 PM, "Leonard Daly" <Leonard.Daly at realism.com> 
> wrote:
>
>> Only have time right now to respond to the first thing that caught 
>> my
>> attention...
>>
>>
>> It's not clear that much much recent dialog is penetrating several
>> portions of your list.  For example, SVG also has a script node 
>> that seems
>> to operate just fine in combination with HTML.  It seems prudent to 
>> pose
>> interoperability as the baseline goal requirement, with the 
>> corresponding
>> due diligence to compare pros/cons and implement alternatives. 
>> Listing
>> things like "nodes shall not have name conflicts" and "shall behave 
>> as the
>> HTML element" as end states seems to close off such necessary 
>> consideration
>> of alternative approaches that already exist and can work.
>>
>>
>> It has been repeated pointed out that SVG has a script node. It is 
>> called
>> script. SVG is also part of HTML5 and fully integrated into the 
>> DOM. Also
>> SVG's script is a real JavaScript node that is accessible from 
>> outside of
>> the SVG tag set. In order to get X3D there, X3D would need to be 
>> recognized
>> as part of HTML and this would need to be regular JavaScript 
>> element. Based
>> on everything I did in a quick read (several pages from a Google 
>> search of
>> 'SVG Script') this morning, you can script SVG from inside or 
>> outside of
>> the SVG tag.
>>
>> So until X3D becomes fully integrated in HTML and can be solely 
>> scripted
>> through DOM and does not need a JavaScript library to parse and 
>> execute it,
>> there is no point in talking about an X3D Script node.
>>
>> --
>> *Leonard Daly*
>> 3D Systems & Cloud Consultant
>> LA ACM SIGGRAPH Chair
>> President, Daly Realism - *Creating the Future*
>>
>> _______________________________________________
>> x3d-public mailing list
>> x3d-public at web3d.org
>> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>>
>>
>


--------------------------------------------------------------------------------


> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>