<p dir="ltr">One advantage of integrating x3d nodes as DOM nodes is that they can be manipulated in the same way and by the same tools as other DOM nodes, including D3. So it should not be necessary to explicitly add .enter and such to the spec. or API . It only should be necessary to spell out that X3D nodes can be manipulated using the standard DOM API, just like other nodes such as svg or table. Then tools like D3 or jquery will work with x3d nodes, like they work today with x3dom nodes.</p>
<p dir="ltr">While to me it is self evident that the web platform is the most relevant platform for X3D - after all vrml has URLs - I want to point out that from what I have seen most VR development takes currently place as standalone apps using Unity, distributed from tightly controlled app stores. Such a distribution model fits standalone X3D browsers better, once they have a VR mode.<br>
But once 3d gets more common on the web, there will be an expectation that VR is also available and perhaps somehow integrated with other web content.</p>
<p dir="ltr">Andreas</p>
<div class="gmail_quote">On Feb 24, 2016 10:26 PM, <<a href="mailto:x3d-public-request@web3d.org">x3d-public-request@web3d.org</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send x3d-public mailing list submissions to<br>
<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:x3d-public-request@web3d.org">x3d-public-request@web3d.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:x3d-public-owner@web3d.org">x3d-public-owner@web3d.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of x3d-public digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Non-Hand Coding of X3D (Leonard Daly)<br>
2. Re: Non-Hand Coding of X3D (John Carlson)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 24 Feb 2016 18:01:47 -0800<br>
From: Leonard Daly <<a href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>><br>
To: John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>><br>
Cc: X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br>
Subject: Re: [x3d-public] Non-Hand Coding of X3D<br>
Message-ID: <<a href="mailto:56CE608B.6000501@realism.com">56CE608B.6000501@realism.com</a>><br>
Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>
<br>
John,<br>
<br>
Just to address a few of your points.<br>
<br>
I don't see the functionality currently available with PROTOs and<br>
Scripts going away. I see it increasing because HTML Scripts can easily<br>
add nodes to the DOM. There have been several discussions on the topic<br>
of PROTOs. I see a proto-expander or MACRO as being a great addition to<br>
V4. It is also possible to easily provide that sort of service via an<br>
HTML Script or new custom-implemented node. If the new node is a<br>
collection of existing nodes (say Yves pyramid node), then the<br>
supporting code to create and parse that node is very easy to write in<br>
X3DOM.<br>
<br>
I can see a shared library of useful nodes that sites on top of X3D and<br>
is available to the user as either nodes or HTML scripts.<br>
<br>
I would like to see X3D accept a wide variety of data formats, even if<br>
some translation/conversion needs to occur. Using InstantReality it is<br>
possible to go from X3D, OBJ, FBX and perhaps others to SRC. SRC is a<br>
good format for injestion because it moves quickly to WebGL. X3D is to<br>
remain ISO standardized. No other 3D format and run-time can state that.<br>
<br>
Animation is a current problem. The SRC does not hold animations. The<br>
only widely used format that does combined with model data is FBX. That<br>
is something that needs to be developed, but there are several things<br>
that need to come first.<br>
<br>
<br>
Leonard Daly<br>
<br>
<br>
<br>
<br>
<br>
> You make good points Leonard. How would you differentiate V4 from<br>
> Collada in that case? My understanding is that X3D provides for<br>
> declarative app development. This is one reason we are moving towards<br>
> the web, to open X3D up to more app developers. What is important for<br>
> declarative app development? Protos, Templates, Web Components and<br>
> associated scripts, essentially *shared behavior*. If you have a<br>
> virtual world, you might certainly have exactly one of everything.<br>
> However, it?s easier to instantiate Protos or Templates, I think.<br>
> The trick is to only mention the creation a few times (once) with<br>
> templates or web components, and let the environment expand it into<br>
> multiple instances through templated transforms and parameterization.<br>
> I don?t want to see 400 ProtoInstances of cylinders in code, unless<br>
> it?s generated (HTML). X3D *should* be associated with a data format<br>
> for pure data, like D3.js has several, and transforming pure data into<br>
> 3D. I know I have different requirements, but I think X3D V4 should<br>
> be designed for scaling things up?not only shapes and transforms, but<br>
> coordinates and polygons as well (SRC). Is any other format in<br>
> position to provide for such scaling without killing memory or<br>
> diskspace? Models are certainly moving towards SRC. If you are<br>
> concerned about animation, what?s the best way to provide for<br>
> animation coming from these tools? We have your proposed nodes. Are<br>
> these sufficient? Should we start looking more at creating exporters<br>
> for animation beyond just models? What animation exporters to X3D are<br>
> already out there?<br>
><br>
> John<br>
><br>
>> On Feb 24, 2016, at 7:55 PM, Leonard Daly <<a href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a><br>
>> <mailto:<a href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>>> wrote:<br>
>><br>
>> There seems to be some confusion about my statements about not<br>
>> hand-coding certain things.<br>
>><br>
>> I have stated that models and animations are not hand-coded anymore.<br>
>> That statement does not mean it can't be done, but there are many<br>
>> tools that do it, including open-source ones. There is no way someone<br>
>> is going to hand-code models such as you can see at<br>
>> <a href="http://www.blendswap.com/blends/index" rel="noreferrer" target="_blank">http://www.blendswap.com/blends/index</a>. Hand coding models to be<br>
>> printed is also not a good idea because things will probably not line<br>
>> up correctly.<br>
>><br>
>> Animation is the same thing. Yes you can animate by hand-coding all<br>
>> of the motions and deformations, but that is not how it is done. If<br>
>> X3D is to get any acceptance into the professional marketplace it<br>
>> MUST work with application generated models and animations. There<br>
>> will still be some important animations that are hand coded (e.g.,<br>
>> camera motions, automated systems, etc.).<br>
>><br>
>> Nothing I have done in working out the V4 proposal precludes<br>
>> hand-coding of animation or modeling. It does not provide a lot of<br>
>> convenience features/nodes to make complex work simple. In the<br>
>> marketplace, it is much simpler to get someone to do the model or<br>
>> animation in a tool.<br>
>><br>
>><br>
>> --<br>
>> *Leonard Daly*<br>
>> 3D Systems & Cloud Consultant<br>
>> X3D Co-Chair on Sabbatical<br>
>> LA ACM SIGGRAPH Chair<br>
>> President, Daly Realism - /Creating the Future/<br>
>> _______________________________________________<br>
>> x3d-public mailing list<br>
>> <a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a> <mailto:<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br>
>> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
><br>
<br>
<br>
--<br>
*Leonard Daly*<br>
3D Systems & Cloud Consultant<br>
X3D Co-Chair on Sabbatical<br>
LA ACM SIGGRAPH Chair<br>
President, Daly Realism - /Creating the Future/<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160224/37e79dac/attachment-0001.html" rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160224/37e79dac/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 24 Feb 2016 22:26:10 -0500<br>
From: John Carlson <<a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a>><br>
To: Leonard Daly <<a href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>><br>
Cc: X3D Graphics public mailing list <<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br>
Subject: Re: [x3d-public] Non-Hand Coding of X3D<br>
Message-ID: <<a href="mailto:7D6472CF-CF81-4AB3-8911-7A465CFF570E@gmail.com">7D6472CF-CF81-4AB3-8911-7A465CFF570E@gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
It would be cool if X3D had an .enter() function like D3.js to add and update nodes from data. I think there?s .exit().remove() to for removing nodes. This makes your data work extremely well with creating and removing visualization objects. <a href="https://bl.ocks.org/mbostock/3808218" rel="noreferrer" target="_blank">https://bl.ocks.org/mbostock/3808218</a> <<a href="https://bl.ocks.org/mbostock/3808218" rel="noreferrer" target="_blank">https://bl.ocks.org/mbostock/3808218</a>> This might be done by attaching data to a MACRO (the MACRO being enter()).<br>
<br>
On Feb 24, 2016, at 9:01 PM, Leonard Daly <<a href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>> wrote:<br>
><br>
> John,<br>
><br>
> Just to address a few of your points.<br>
><br>
> I don't see the functionality currently available with PROTOs and Scripts going away. I see it increasing because HTML Scripts can easily add nodes to the DOM. There have been several discussions on the topic of PROTOs. I see a proto-expander or MACRO as being a great addition to V4. It is also possible to easily provide that sort of service via an HTML Script or new custom-implemented node. If the new node is a collection of existing nodes (say Yves pyramid node), then the supporting code to create and parse that node is very easy to write in X3DOM.<br>
><br>
> I can see a shared library of useful nodes that sites on top of X3D and is available to the user as either nodes or HTML scripts.<br>
><br>
> I would like to see X3D accept a wide variety of data formats, even if some translation/conversion needs to occur. Using InstantReality it is possible to go from X3D, OBJ, FBX and perhaps others to SRC. SRC is a good format for injestion because it moves quickly to WebGL. X3D is to remain ISO standardized. No other 3D format and run-time can state that.<br>
><br>
> Animation is a current problem. The SRC does not hold animations. The only widely used format that does combined with model data is FBX. That is something that needs to be developed, but there are several things that need to come first.<br>
><br>
><br>
> Leonard Daly<br>
><br>
><br>
><br>
><br>
><br>
>> You make good points Leonard. How would you differentiate V4 from Collada in that case? My understanding is that X3D provides for declarative app development. This is one reason we are moving towards the web, to open X3D up to more app developers. What is important for declarative app development? Protos, Templates, Web Components and associated scripts, essentially *shared behavior*. If you have a virtual world, you might certainly have exactly one of everything. However, it?s easier to instantiate Protos or Templates, I think. The trick is to only mention the creation a few times (once) with templates or web components, and let the environment expand it into multiple instances through templated transforms and parameterization. I don?t want to see 400 ProtoInstances of cylinders in code, unless it?s generated (HTML). X3D *should* be associated with a data format for pure data, like D3.js has several, and transforming pure data into 3D. I know I have different requirements, but I think X3D V4 should be designed for scaling things up?not only shapes and transforms, but coordinates and polygons as well (SRC). Is any other format in position to provide for such scaling without killing memory or diskspace? Models are certainly moving towards SRC. If you are concerned about animation, what?s the best way to provide for animation coming from these tools? We have your proposed nodes. Are these sufficient? Should we start looking more at creating exporters for animation beyond just models? What animation exporters to X3D are already out there?<br>
>><br>
>> John<br>
>><br>
>>> On Feb 24, 2016, at 7:55 PM, Leonard Daly <<a href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a> <mailto:<a href="mailto:Leonard.Daly@realism.com">Leonard.Daly@realism.com</a>>> wrote:<br>
>>><br>
>>> There seems to be some confusion about my statements about not hand-coding certain things.<br>
>>><br>
>>> I have stated that models and animations are not hand-coded anymore. That statement does not mean it can't be done, but there are many tools that do it, including open-source ones. There is no way someone is going to hand-code models such as you can see at <a href="http://www.blendswap.com/blends/index" rel="noreferrer" target="_blank">http://www.blendswap.com/blends/index</a> <<a href="http://www.blendswap.com/blends/index" rel="noreferrer" target="_blank">http://www.blendswap.com/blends/index</a>>. Hand coding models to be printed is also not a good idea because things will probably not line up correctly.<br>
>>><br>
>>> Animation is the same thing. Yes you can animate by hand-coding all of the motions and deformations, but that is not how it is done. If X3D is to get any acceptance into the professional marketplace it MUST work with application generated models and animations. There will still be some important animations that are hand coded (e.g., camera motions, automated systems, etc.).<br>
>>><br>
>>> Nothing I have done in working out the V4 proposal precludes hand-coding of animation or modeling. It does not provide a lot of convenience features/nodes to make complex work simple. In the marketplace, it is much simpler to get someone to do the model or animation in a tool.<br>
>>><br>
>>><br>
>>> --<br>
>>> Leonard Daly<br>
>>> 3D Systems & Cloud Consultant<br>
>>> X3D Co-Chair on Sabbatical<br>
>>> LA ACM SIGGRAPH Chair<br>
>>> President, Daly Realism - Creating the Future<br>
>>> _______________________________________________<br>
>>> x3d-public mailing list<br>
>>> <a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a> <mailto:<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a>><br>
>>> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a> <<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a>><br>
>><br>
><br>
><br>
> --<br>
> Leonard Daly<br>
> 3D Systems & Cloud Consultant<br>
> X3D Co-Chair on Sabbatical<br>
> LA ACM SIGGRAPH Chair<br>
> President, Daly Realism - Creating the Future<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160224/3f2cfb59/attachment.html" rel="noreferrer" target="_blank">http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20160224/3f2cfb59/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
x3d-public mailing list<br>
<a href="mailto:x3d-public@web3d.org">x3d-public@web3d.org</a><br>
<a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
<br>
<br>
------------------------------<br>
<br>
End of x3d-public Digest, Vol 83, Issue 69<br>
******************************************<br>
</blockquote></div>