X3D V4 Open Meeting - Revision history

Walroy: /* X3D Player in the Browser */

2016-06-15T14:28:32Z

‎X3D Player in the Browser

2016-06-15T14:27:27Z

‎XML3D Design

2016-06-15T14:24:19Z

‎XML3D Design

2016-06-15T14:20:56Z

‎HTML integration and backwards compatibility

2016-06-15T14:20:20Z

‎HTML Integration and backwards compatibility

2016-06-15T14:20:08Z

‎HTML and backwards compatibility

2016-06-15T14:19:39Z

‎HTML and backwards compatibility

2016-06-13T09:29:01Z

‎Topics

2016-06-09T15:21:43Z

‎Contribution 14

2016-06-09T15:20:45Z

‎Contribution 13

@@ Line 46: / Line 46: @@
 === X3D Player in the Browser ===
-Can we get to a situation where X3D presentation is built into the browser or will we always need Cobweb/X3DOM
+Can we get to a situation where X3D presentation is built into the browser or will we always need Cobweb/X3DOM or something similar?
-Browser writers are not interested in adding 3D.
+Currently browser writers are not interested in adding 3D. Therefore, always need a JavaScript engine to be used.
-−
-Always need a JavaScript engine to be used.
 === Node Set ===

@@ Line 42: / Line 42: @@
 Recent XML3D design work is investigating the use of [https://www.w3.org/standards/techs/components#w3c_all Web Components]
-Node.js, DOM module on Node.js.
+XML3D a layered structure, built on Node.js and a DOM module.
-−
-Could use node.js in applications
-−
-Modularity and Web3D components.
 === X3D Player in the Browser ===

@@ Line 40: / Line 40: @@
 ===XML3D Design===
-XML3D, using WebComponents
+Recent XML3D design work is investigating the use of [https://www.w3.org/standards/techs/components#w3c_all Web Components]
 Node.js, DOM module on Node.js.

← Older revision		Revision as of 14:20, 15 June 2016
Line 37:		Line 37:

	General strategy is to integrate into HTML and keep backwards compatibility, without throwing away existing capabilities.		General strategy is to integrate into HTML and keep backwards compatibility, without throwing away existing capabilities.
		+
		+	===XML3D Design===

	XML3D, using WebComponents		XML3D, using WebComponents

@@ Line 34: / Line 34: @@
 Note: This section is intended for the capture of discussion points.
-===HTML Integration and backwards compatibility===
+===HTML integration and backwards compatibility===
 General strategy is to integrate into HTML and keep backwards compatibility, without throwing away existing capabilities.

@@ Line 36: / Line 36: @@
 ===HTML and backwards compatibility===
-) Integrate into HTML and keep backwards compatibility
+General strategy is to integrate into HTML and keep backwards compatibility, without throwing away existing capabilities.
-−
-Don't throw away existing.
 XML3D, using WebComponents

@@ Line 6: / Line 6: @@
 Note: The red question marks at the end of each question are place-holders for any short answers to emerge from the discussions.
-*What level of X3D integration into HTML5 do we want? <span style="color: red;">???</span>
+*What level of X3D integration into HTML5 do we want?
-**Do we want to be fully integrated like SVG? <span style="color: red;">???</span>
+**Do we want to be fully integrated like SVG? <span style="color: red;">Yes</span>
-*Do we want/need a DOM spec? If so: <span style="color: red;">???</span>
+*Do we want/need a DOM spec? If so: <span style="color: red;">Yes</span>
 **Which DOM version should it be based on? <span style="color: red;">???</span>
 **Do we want to fully support all DOM/HTML features? <span style="color: red;">???</span>
-*Do we want to maximize the backwards compatibility of V4.0 with V3.3? Or break away completely? <span style="color: red;">???</span>
+*Do we want to maximize the backwards compatibility of V4.0 with V3.3? Or break away completely? <span style="color: red;">Maximize compatibility</span>
-**Do we want to retain SAI? <span style="color: red;">???</span>
+**Do we want to retain SAI? <span style="color: red;">Yes</span>
 *What features do we want? For example, <span style="color: red;">???</span>
 **How is animation to be handled? The X3D way of TimeSensor and ROUTEs, or an HTML way, such as CSS3 animations, or else JavaScript? <span style="color: red;">???</span>

@@ Line 647: / Line 647: @@
 ===Contribution 14===
 <pre style="white-space: pre-wrap;">
 Thanks to all those who've expressed their view.

@@ Line 635: / Line 635: @@
 ===Contribution 13===
 <pre style="white-space: pre-wrap;">
 Thank you for that concise, clear and pragmatic summary of a possible bright future for an X3D V4.