x_ite 8.0.0 → 8.3.0

package/docs/_layouts/wide.html

@@ -0,0 +1,52 @@
+---
+layout: page
+---
+<style>
+#sidebar,
+#panel-wrapper {
+   display: none !important;
+}
+
+@media all and (max-width: 849px) {
+   #sidebar,
+   #panel-wrapper {
+      display: block !important;
+   }
+}
+
+#topbar-wrapper {
+   left: 0;
+}
+
+#topbar {
+   margin: 0;
+   max-width: unset;
+}
+
+#search-wrapper {
+   margin: 0;
+}
+
+#main-wrapper,
+footer {
+   margin: 0;
+}
+
+#main {
+   margin: 0;
+   max-width: unset;
+}
+
+#core-wrapper {
+   flex: 0 0 100%;
+   max-width: unset;
+}
+
+footer > .container {
+   padding: 0 !important;
+   max-width: unset;
+}
+</style>
+
+{% include scripts.html %}
+{{ content }}

package/docs/_layouts/wrap.html

@@ -0,0 +1,4 @@
+---
+# Wrapper HTML
+---
+{{ content | replace: 'data-src=', 'src=' }}

package/docs/_layouts/x_ite.html

@@ -0,0 +1,8 @@
+---
+layout: post
+panel_includes:
+  - nav
+  - toc
+---
+{% include scripts.html %}
+{{ content }}

package/docs/_plugins/no_date.rb

@@ -0,0 +1,11 @@
+class Jekyll::PostReader
+   # Don't use DATE_FILENAME_MATCHER so we don't need to put those stupid dates
+   # in the filename. Also limit to just *.markdown, so it won't process binary
+   # files from e.g. drags.
+   def read_posts(dir)
+     read_publishable(dir, "_posts", /.*\.md$/)
+   end
+   def read_drafts(dir)
+     read_publishable(dir, "_drafts", /.*\.md$/)
+   end
+ end

package/docs/_plugins/posts-lastmod-hook.rb

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+#
+# Check for changed posts
+
+Jekyll::Hooks.register :posts, :post_init do |post|
+
+  commit_num = `git rev-list --count HEAD "#{ post.path }"`
+
+  if commit_num.to_i > 1
+    lastmod_date = `git log -1 --pretty="%ad" --date=iso "#{ post.path }"`
+    post.data['last_modified_at'] = lastmod_date
+  end
+
+end

package/docs/{Accessing-the-External-Browser.md → _posts/accessing-the-external-browser.md}

@@ -1,20 +1,20 @@
 ---
-# Feel free to add content and custom Front Matter to this file.
-# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
-
-layout: single
+title: Accessing the External Browser
+date: 2022-11-28
+nav: main
+categories: []
+tags: [accessing, external, browser]
 ---
-# Accessing the External Browser
 
 ## Overview
 
-X\_ITE is designed to provide access to the internal X3D browser and its contained scene graph via JavaScript, either within an internal X3D Script node or an external HTML script.
+X_ITE is designed to provide access to the internal X3D browser and its contained scene graph via JavaScript, either within an internal X3D Script node or an external HTML script.
 
 If you want combine DOM access with X3D access in your JavaScript functions then you probably want to access the external browser object if you want include an external JavaScript file in your HTML page and you don't wanna do it directly a in Script node.
 
 ## Introduction
 
-There is the X3D object which is always available, it expects one function handler that is called when the browsers (<x3d-canvas> elements) are ready, and a second function handler, that is called if an error occurred. These two arguments are optional. The return value of the X3D function is a Promise, which can be used instead of the arguments.
+There is the X3D object which is always available, it expects one function handler that is called when the browsers (\<x3d-canvas\> elements) are ready, and a second function handler, that is called if an error occurred. These two arguments are optional. The return value of the X3D function is a Promise, which can be used instead of the arguments.
 
 ```js
 Promise X3D ([callback[, errorCallback]]);
@@ -27,7 +27,7 @@ function callback ()
 function errorCallback (error)
 ```
 
-The external browser can be accessed by calling the `X3D .getBrowser (selector)` function, *selector* can be any CSS selector, if you have only one &lt;x3d-canvas&gt; element on your page, you can omit the selector argument:
+The external browser can be accessed by calling the `X3D .getBrowser (selector)` function, *selector* can be any CSS selector, if you have only one \<x3d-canvas\> element on your page, you can omit the selector argument:
 
 ```html
 <script>
@@ -92,9 +92,9 @@ async function foo (url)
 
 #### X3D **noConflict** ()
 
-In X\_ITE's case, the `X3D` function object is the main entry function. If you need to use another JavaScript library alongside X\_ITE, return control of the `X3D` function object back to the other library with a call to `X3D .noConflict ()`. Old references of `X3D` function object are saved during X\_ITE initialization; `X3D .noConflict ()` simply restores them. The return value is the `X3D` function object itself.
+In X_ITE's case, the `X3D` function object is the main entry function. If you need to use another JavaScript library alongside X_ITE, return control of the `X3D` function object back to the other library with a call to `X3D .noConflict ()`. Old references of `X3D` function object are saved during X_ITE initialization; `X3D .noConflict ()` simply restores them. The return value is the `X3D` function object itself.
 
-If for some reason two versions of X\_ITE are loaded (which is not recommended), calling `X3D .noConflict ()` from the second version will return the globally scoped `X3D` object to those of the first version.
+If for some reason two versions of X_ITE are loaded (which is not recommended), calling `X3D .noConflict ()` from the second version will return the globally scoped `X3D` object to those of the first version.
 
 ```html
 <script src="other_lib.js"></script>
@@ -107,7 +107,7 @@ const X_ITE_X3D = X3D .noConflict ();
 
 The following services can be used to establish a session and obtain the X3DBrowser object.
 
-#### X3DBrowser **getBrowser** (*\[selector : String\]*)
+#### X3DBrowser **getBrowser** (*[selector : String]*)
 
 The *selector* argument must be a string containing a valid CSS selector expression to match elements against. If no selector was given, »x3d-canvas« is used as selector string. The return value is the appropriate X3DBrowser object.
 
@@ -122,12 +122,12 @@ Given a DOM element that represents a x3d-canvas element, the getBrowser functio
 
 ```js
 // Query all x3d-canvas elements within the HTML page.
-const x3d_canvases = document .querySelectorAll ("x3d-canvas");
+const canvases = document .querySelectorAll ("x3d-canvas");
 
-for (const x3d_canvas of x3d_canvases)
+for (const canvas of canvases)
 {
   // Obtain X3DBrowser object of element i.
-  const Browser = X3D .getBrowser (x3d_canvas);
+  const Browser = X3D .getBrowser (canvas);
   ...
 }
 ```
@@ -140,11 +140,11 @@ Creates a new x3d-canvas DOM element, initializes it and returns it. Throws an e
 function addBrowser (parent)
 {
    // Create a new x3d-canvas element.
-   const x3d_canvas = X3D .createBrowser ();
+   const canvas = X3D .createBrowser ();
 
-   x3d_canvas .setAttribute ("src", "/my/world.x3d");
+   canvas .setAttribute ("src", "/my/world.x3d");
 
-   parent .appendChild (x3d_canvas);
+   parent .appendChild (canvas);
 }
 ```
 
@@ -154,7 +154,7 @@ The X3D object has several properties, you can use any of the properties below.
 
 #### **X3DConstants**
 
-The X3DConstants object defines values that can be useful for scripting.
+The X3DConstants object defines values that can be useful for scripting. See also [Constants Services](reference/constants-services).
 
 ```js
 function foo (node)
@@ -186,7 +186,10 @@ function foo (node)
 
 #### **X3DFields**
 
-All X3DFields (SFColor, ..., MFBool, MFColor, and so on). The fields can be created using the object as constructor. **Note:** Scalar objects like SFBool, SFDouble, SFFloat, SFInt32, SFString, and SFTime have no constructor, just use the built-in JavaScript types Boolean, Number, and String.
+All X3DFields (SFColor, ..., MFBool, MFColor, and so on). The fields can be created using the object as constructor. See also [Field Services and Objects](reference/field-services-and-objects).
+
+>**Note:** Scalar objects like SFBool, SFDouble, SFFloat, SFInt32, SFString, and SFTime have no constructor, just use the built-in JavaScript types Boolean, Number, and String.
+{: .prompt-info }
 
 ```js
 // Create a new translation vector and
@@ -199,19 +202,17 @@ const
 
 ## Function Reference
 
-A complete function reference for the X3DBrowser object and all other X3D JavaScript objects can be found [here](reference/ECMAScript-Object-and-Function-Definitions.html).
+A complete function reference for the X3DBrowser object and all other X3D JavaScript objects can be found in [ECMAScript Object and Function Definitions](reference/ecmascript-object-and-function-definitions).
 
 ## Example
 
-[![Adrenaline Molecule in 3D](https://create3000.github.io/media/x_ite/external-browser/adrenaline.png)](https://create3000.github.io/media/x_ite/external-browser/adrenaline.html)
-
-[View scene in this window.](https://create3000.github.io/media/x_ite/external-browser/adrenaline.html)
+<iframe src="https://create3000.github.io/media/x_ite/external-browser/adrenaline.html"></iframe>
 
 Adding HTML controls to your scene is no rocket science. We have added some HTML buttons below the x3d-canvas, which on click call a callback function.
 
 ### The JavaScript
 
-```js
+```html
 <script>
 function init ()
 {
@@ -221,7 +222,7 @@ function init ()
     timer   = scene .getNamedNode ("SpinAnimationTimer"); // Get box TouchSensor node.
 
   // Add field callback to get informed when cycleTime is fired. "time" is an arbitrary
-  // string to identify the callback, for intance if you later want to remove the callback.
+  // string to identify the callback, for instance if you later want to remove the callback.
   timer .addFieldCallback ("cycleTime", "time", function (value)
   {
     console .log ("cycleTime: " + value);

package/docs/_posts/browser-support.md

@@ -0,0 +1,53 @@
+---
+title: Browser Support
+date: 2022-11-28
+nav: main
+categories: []
+tags: [browser, support]
+---
+
+## Overview
+
+To enjoy the best and most secure experience, we recommend you keep your browser and operating system updated. X_ITE will support the current and previous major releases of:
+
+## Desktop
+
+Since April 2016 **Chrome** supports all WebGL and JavaScript ES 6 features required by X_ITE. We support the current version and the previous version of Chrome, although X_ITE also runs fine in older versions.
+<https://www.google.com/chrome>{:target="_blank"}
+
+**Firefox** as the first browser that supports everything X_ITE needs and is extensively tested since years. We have full support for Firefox.
+<https://www.mozilla.org/firefox/products/>{:target="_blank"}
+
+**Safari** has excellent support for WebGL and JavaScript ES 6 and is as much popular as other browsers especially on MacOS X. Keep your Mac up to date to have the best experience we can give.
+<https://www.apple.com/safari/>{:target="_blank"}
+
+**Opera** uses the same rendering engine used by Safari and Chrome and is therefore fully supported since April 2016. Always use the latest version of Opera to make your Internet experience more secure and enjoyable.
+<https://www.opera.com/>{:target="_blank"}
+
+Starting with Windows 10 X_ITE runs fine in **Microsoft Edge** and is fully supported. Microsoft Edge provides everything X_ITE needs to give you the best performance.
+<https://www.microsoft.com/windows/microsoft-edge>{:target="_blank"}
+
+## Mobile
+
+All stock browser on **Android** 4.0+ support WebGL and JavaScript ES 6 natively. Always keep in mind to keep your files small in size and always consider to optimize for performance.
+<https://www.android.com/>{:target="_blank"}
+
+iOS has good support since **Safari** on iOS 7+. Simplify your scenes and test them extensively to achieve the best results how you would like it to be.
+<https://www.apple.com/ios/>{:target="_blank"}
+
+>**Note:** Any problem with X_ITE in the above browsers should be reported as a bug in X_ITE. See [Report a Bug](report-a-bug).
+{: .prompt-info }
+
+We do not support older browsers like Internet Explorer 6-9, Opera 12.1x or Safari 5.1+.
+
+## Unsupported Browsers
+
+While X_ITE *might* run without major issues in older browser versions, we do not actively test X_ITE in them and generally do not fix bugs that may appear in them.
+
+Similarly, X_ITE does not fix bugs in pre-release versions of browsers, such as beta or dev releases. If you find a bug with X_ITE in a pre-release of a browser, you should report the bug to the browser vendor.
+
+## About Browser Support
+
+X_ITE is constantly tested with all of its supported browsers via unit tests. However, a web page using X_ITE may not work in the same set of browsers if its own code takes advantage of (or falls prey to) browser-specific behaviors. Testing is essential to fully support a browser. The Microsoft Edge Developer site makes available [virtual machines](https://dev.windows.com/en-us/microsoft-edge/tools/vms/){:target="_blank"} for testing many different versions of Internet Explorer. Older versions of other browsers can be found at [oldversion.com](http://oldversion.com/){:target="_blank"}.
+
+Only the most current version of X_ITE is tested and updated to fix bugs or add features. Users of older versions that find a bug should upgrade to the latest released version to determine if the bug has already been fixed.

package/docs/{Custom-Shaders.md → _posts/custom-shaders.md}

@@ -1,11 +1,10 @@
 ---
-# Feel free to add content and custom Front Matter to this file.
-# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
-
-layout: single
+title: Custom Shaders
+date: 2022-11-28
+nav: main
+categories: []
+tags: [custom, shaders]
 ---
-# Custom Shaders
-
 ## Overview
 
 When you display your 3D models with X\_ITE, by default it will use the Gouraud shader. This is a versatile shader that can cover a lot of your rendering needs. If this is not enough there is also a Phong shader available, adjustable with the browser shading option per scripting.
@@ -14,18 +13,20 @@ However, you will often want to perform special effects or special cases for you
 
 ## Example
 
-[![Shader Example](https://create3000.github.io/media/images/water-quality.png)](https://create3000.github.io/media/examples/X3D/WaterQuality/example.html)
+<x3d-canvas src="https://create3000.github.io/media/examples/X3D/WaterQuality/WaterQuality.x3d">
+  <img src="https://create3000.github.io/media/images/water-quality.png" alt="Shader Example"/>
+</x3d-canvas>
 
-[View scene in this window.](https://create3000.github.io/media/examples/X3D/WaterQuality/example.html)
+[Download ZIP Archive](https://create3000.github.io/media/examples/X3D/WaterQuality/WaterQuality.zip)
 
 ## Shaders and Shader Definition
 
-WebGL uses the GLSL language to write shaders that can be run across all browsers. With X\_ITE you create your own shader using ComposedShader and ShaderPart nodes and than attach the ComposedShader to the *shader* field of an Appearance node and that is a child''s play with Titania.
+WebGL uses the GLSL language to write shaders that can be run across all browsers. With X\_ITE you create your own shader using ComposedShader and ShaderPart nodes and than attach the ComposedShader to the *shader* field of an Appearance node and that is a child's play with Titania.
 
 ### X3D
 
 ```js
-#X3D V3.3 utf8
+#X3D V4.0 utf8
 
 DEF Timer TimeSensor {
   loop TRUE
@@ -596,7 +597,10 @@ If the shader node is part of a ParticleSystem node the following attributes and
 
 ## Built-in Constants
 
-Some built-in variables are enumerated and have special values and meanings. The following table list all of them and their corresponding values. Note: as of version 1.27 these constant are built-in.
+Some built-in variables are enumerated and have special values and meanings. The following table list all of them and their corresponding values.
+
+>**Note:** As of version 1.27 these constant are built-in.
+{: .prompt-tip }
 
 <table>
    <thead>
@@ -700,12 +704,12 @@ void
 main ()
 {
    ...
-   //http://outerra.blogspot.com/2013/07/logarithmic-depth-buffer-optimizations.html
+   //https://outerra.blogspot.com/2013/07/logarithmic-depth-buffer-optimizations.html
    gl_FragDepth = log2 (1.0 + 1.0 / gl_FragCoord .w) * x3d_LogarithmicFarFactor1_2;
 }
 ```
 
 ## See Also
 
-- [ComposedShader](https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#ComposedShader)
-- [ShaderPart](https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shaders.html#ShaderPart)
+- [ComposedShader](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/shaders.html#ComposedShader){:target="_blank"}
+- [ShaderPart](https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/shaders.html#ShaderPart){:target="_blank"}

package/docs/{DOM-Integration.md → _posts/dom-integration.md}

@@ -1,25 +1,22 @@
 ---
-# Feel free to add content and custom Front Matter to this file.
-# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
-
-layout: single
+title: DOM Integration
+date: 2022-11-28
+nav: main
+categories: []
+tags: [dom, integration, XHTML]
 ---
-# DOM Integration
-
 ## Overview
 
 DOM integration allows you to integrate 3D content seamlessly into your web page, with just a JavaScript file included the scene can be written directly into the XHTML or HTML markup.
 
 Andreas Plesch wrote a nice plug-in for X3D DOM integration. This enables JavaScript authors to use X3D content as if it would be HTML. It links the X3D DOM nodes to the X3D scene graph and thereby allows for control of the X3D scene using regular DOM manipulation methods.
 
-**HTML DOM integration is available by default now.**
+**HTML DOM integration is now an integral part of X_ITE.**
 
-## How use with X_ITE
+## How to Use With X_ITE
 
 Create an HTML or XHTML page and save it, include the »x_ite.min.js«. Now, X3D content can directly be written within the \<x3d-canvas\> element and regular DOM manipulation methods can be used to manipulate the scene graph. This gives X3D authors the ability to combine HTML with X3D. The example below will show a simple Box node in the \<x3d-canvas\> element.
 
-### Example
-
 ```html
 <!DOCTYPE html>
 <html>
@@ -28,8 +25,9 @@ Create an HTML or XHTML page and save it, include the »x_ite.min.js«. Now, X3D
     <script src="https://create3000.github.io/code/x_ite/latest/x_ite.min.js"></script>
     <style>
 x3d-canvas {
-  width: 768px;
-  height: 432px;
+  width: 100%;
+  height: auto;
+  aspect-ratio: 16 / 7.8;
 }
     </style>
     <script>
@@ -84,12 +82,19 @@ window .addEventListener ("load", function ()
 </html>
 ```
 
+>**Attention:** Make sure you use **closing tags** for all X3D elements. This is needed, because the web browser does not know the X3D elements, and therefor does not know if the tag is self-closing, unless you use XHTML.
+{: .prompt-danger }
+
+### Example
+
+<iframe src="https://create3000.github.io/media/x_ite/dom-integration/box.html"></iframe>
+
 ## Attributes
 
 If you change an attribute of an X3D element, then the internal state of the node will also change.
 
 ```js
-const material = document .querySelector ("Material")
+const material = document .querySelector ("Material");
 
 material .setAttribute ("diffuseColor", "1 0 0"); // Set diffuse color to red.
 ```
@@ -101,11 +106,12 @@ You can add an event listener to any X3D element with the name of the output fie
 Events sent from a node are of type CustomEvent and have the following properties:
 
 ```js
-{
-  type: string,   // name of field
+CustomEvent: {
+  type: string,        // name of field
+  target: HTMLElement, // X3D element of node
   detail: {
-    node: SFNode, // node to which the field belongs to
-    value: any,   // new value of field
+    node: SFNode,      // node to which the field belongs to
+    value: any,        // new value of field
   }
 }
 ```
@@ -181,12 +187,13 @@ function addRoute ()
     scene = document .querySelector ("Scene"),
     route = document .createElement ("ROUTE");
 
-  // Connect a TimeSensor node to a ScalarInterpolator node.
+  // Connect a TimeSensor node with DEF name »Timer« to a ScalarInterpolator node
+  // with DEF name »Interpolator«.
 
   route .setAttribute ("id",        "route1");
-  route .setAttribute ("fromNode",  "Timer1");
+  route .setAttribute ("fromNode",  "Timer");
   route .setAttribute ("fromField", "fraction_changed");
-  route .setAttribute ("toNode",    "Interpolator1");
+  route .setAttribute ("toNode",    "Interpolator");
   route .setAttribute ("toField",   "set_fraction");
 
   scene .appendChild (route);
@@ -202,5 +209,5 @@ function removeRoute ()
 
 ## See Also
 
-* [X3D Encoding : XML](https://www.web3d.org/documents/specifications/19776-1/V3.3/index.html)
-* [X3D Abstract : Node Definitions](https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html)
+* [X3D Encoding : XML](https://www.web3d.org/documents/specifications/19776-1/V3.3/index.html){:target="_blank"}
+* [X3D Abstract : Node Definitions](https://www.web3d.org/documents/specifications/19775-1/V4.0/index.html){:target="_blank"}

package/docs/{Features.md → _posts/features.md}

@@ -1,11 +1,10 @@
 ---
-# Feel free to add content and custom Front Matter to this file.
-# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
-
-layout: single
+title: Features
+date: 2022-11-28
+nav: main
+categories: []
+tags: [features]
 ---
-# Features
-
 ## Overview
 
 X_ITE is a fast, small, and feature-rich JavaScript library for displaying and executing X3D files. It makes things like WebGL programming, document access and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API that works across a multitude of browsers.
@@ -16,7 +15,7 @@ Runs completely standalone, ie. there are no other library dependencies. You jus
 
 Competitive performance for most frequently used functions and nodes. All function within X_ITE are optimized to give your the best performance that JavaScript can offer.
 
-The X_ITE package is optimized in size with Terser to achieve the smallest size we can reach. **X_ITE has only 305kB in size minified and gzipped.**
+The X_ITE package is optimized in size with Terser to achieve the smallest size we can reach. **X_ITE has only 250kB in size minified and compressed.**
 
 X_ITE is designed for optimal performance with event driven programming. The flow of the program is determined by events such as user actions (mouse clicks, key presses), sensor outputs, or messages from other scripts.
 
@@ -24,27 +23,27 @@ All code is held by CREATE3000 and all contributors are selected and all contrib
 
 ## Core Features
 
-Although WebGL acts behind the scenes you do not need any special knowledge about that. There are many of ready to use [X3D nodes](Supported-Nodes.html) that will make life easier. X_ITE provides comprehensive X3D support, which is complete and standard compliant.
+Although WebGL acts behind the scenes you do not need any special knowledge about that. There are many of ready to use [X3D nodes](supported-nodes) that will make life easier. X_ITE provides comprehensive X3D support, which is complete and standard compliant.
 
 X_ITE comes with a high performance JavaScript rendering engine, ie. developers may be completely free of worry about performance optimizations in their code.
 
-We offer full [X3D ECMAScript](reference/ECMAScript-Object-and-Function-Definitions.html) support to give you the best scripting tools you can get.
+We offer full [X3D ECMAScript](reference/ecmascript-object-and-function-definitions) support to give you the best scripting tools you can get.
 
 X3D comes with a fixed set of objects, called *nodes,* which will cover most of your needs. But it's creators have also planned ahead, knowing that you'll sometimes have to create your own objects. The prototyping feature lets you create complex objects that you can reuse, changing certain characteristics of the objects when desired.
 
 X_ITE works seamlessly together with Titania. There is a X_ITE Compatibility Mode in Titania that makes that everything looks equal both in Titania and X_ITE, additionally scripts, and shaders provide the same functionality.
 
-There is excellent build in support for Gouraud and Phong shading. Gouraud and Phong shading are the most popular shading algorithm in use today. This methods were developed by Henri Gouraud and Phong Bui-Toung. If the build in shading methods are not enough for you there is support for [Custom Shaders](Custom-Shaders.html). Don't bother about *uniform variables, shader compilation, and texture loading.* With the Composed Shader node it is easy to write to your own shader even if you are a beginner, but it is also all there for professionals. There is a standardized shader API similar to GLSL that makes it easy to convert your existing shaders. The build in shaders support eight simultaneous local lights for each Shape node, Color node attached to a geometry is supported. There is smooth texture mapping adjustable with TextureProperties node and normals can be auto generated depending on *creaseAngle* if you wish smooth shading.
+There is excellent build in support for Gouraud and Phong shading. Gouraud and Phong shading are the most popular shading algorithm in use today. This methods were developed by Henri Gouraud and Phong Bui-Toung. If the build in shading methods are not enough for you there is support for [Custom Shaders](custom-shaders). Don't bother about *uniform variables, shader compilation, and texture loading.* With the Composed Shader node it is easy to write to your own shader even if you are a beginner, but it is also all there for professionals. There is a standardized shader API similar to GLSL that makes it easy to convert your existing shaders. The build in shaders support eight simultaneous local lights for each Shape node, Color node attached to a geometry is supported. There is smooth texture mapping adjustable with TextureProperties node and normals can be auto generated depending on *creaseAngle* if you wish smooth shading.
 
 Complex routing graphs can be created. The event model of X3D allows the creation of connections between fields (routes) and event are propagated along those connections. The behavior graph collects all of these field connections. It can be changed dynamically by rerouting, adding or breaking connections. Events are injected into the system and propagated through the behavior graph in a well defined order.
 
 Collision detection is also considered, it is unbreakable. In virtual reality environments, collision detection is a algorithm that determines how close a user is to a real physical objects and will stop their movement before colliding with the object. If you wish there is terrain following support. Terrain following works by determining the floor under the avatar and let him go over plains and mountains. Use the NavigationInfo node to enable it.
 
-To add special effects and environment sound to your scenes there is support for MovieTexture and Sound node with a standardized set of functions. These are easy to use. They use HTML5 <video> and <audio> elements internally, you don't need to worry about it.
+To add special effects and environment sound to your scenes there is support for MovieTexture and Sound node with a standardized set of functions. These are easy to use. They use HTML5 \<video\> and \<audio\> elements internally, you don't need to worry about it.
 
 You can create text quick and easy. Use the Text node which can load remote font files in TrueType and OpenType format but there are also build in fonts.
 
-If this is not enough for you have a look at [Supported Nodes](Supported-Nodes.html) there's sure to be something there for you.
+If this is not enough for you have a look at [Supported Nodes](supported-nodes) there's sure to be something there for you.
 
 ## Code Features