x_ite 8.11.6 → 8.11.8

package/docs/_posts/tutorials/introducing-animation.md

@@ -1,216 +0,0 @@
----
-title: Introducing Animations
-date: 2022-11-28
-nav: tutorials-animation-sensors-and-geometry
-categories: [Tutorials]
-tags: [Introducing, Animations]
----
-## Motivation
-
-- Nodes like [Billboard](../components/navigation/billboard) and [Anchor](../components/networking/anchor) have built-in behavior
-- You can create your own behaviors to make shapes move, rotate, scale, blink, and more
-- We need a means to trigger, time, and respond to a sequence of events in order to provide better user/world interactions
-
-## Building animation circuits
-
-Almost every node can be a component in an animation circuit
-
-- Nodes act like virtual electronic parts
-- Nodes can send and receive events
-- Wired routes connect nodes together
-
-An event is a message sent between nodes
-
-- A data value (such as a translation)
-- A time stamp (when did the event get sent)
-
-## Examples
-
-To spin a shape:
-
-- Connect a node that sends rotation events to a [Transform](../components/grouping/transform) node's *rotation* field
-
-To blink a shape:
-
-- Connect a node that sends color events to a [Material](../components/shape/material) node's *diffuseColor* field
-
-## Routing events
-
-To set up an animation circuit, you need three things:
-
-1. A node which sends events
-  - The node must be named with **DEF**
-2. A node which receives events
-  - The node must be named with **DEF**
-3. A route connecting them
-
-## Using node inputs and outputs
-
-Every node has fields, inputs, and outputs:
-
-- initializeOnly: A stored value
-- inputOnly: An input
-- outputOnly: An output
-
-An inputOutput field is a short-hand for a initializeOnly, inputOnly, and outputOnly
-
-## Sample inputs
-
-A [Transform](../components/grouping/transform) node has these input fields:
-
-- *set\_translation*
-- *set\_rotation*
-- *set\_scale*
-
-A [Material](../components/shape/material) node has these input fields:
-
-- *set\_diffuseColor*
-- *set\_emissiveColor*
-- *set\_transparency*
-
-## Sample outputs
-
-An [OrientationInterpolator](../components/interpolation/orientationinterpolator) node has this output field:
-
-- *value\_changed* to send rotation values
-
-A [PositionInterpolator](../components/interpolation/positioninterpolator) node has this output field:
-
-- *value\_changed* to send position (translation) values
-
-A [TimeSensor](../components/time/timesensor) node has this output field:
-
-- *time* to send time values
-
-## Syntax: ROUTE
-
-A **ROUTE** statement connects two nodes together using
-
-- The sender's node name and output field name
-- The receiver's node name and input field name
-
-### XML Encoding
-
-```xml
-<ROUTE fromNode='MySender' fromField='rotation_changed' toNode='MyReceiver' toField='set_rotation'/>
-```
-
-### Classic Encoding
-
-```js
-ROUTE MySender.rotation_changed TO MyReceiver.set_rotation
-```
-
-**ROUTE** and **TO** must be in upper-case
-
-## Field data types
-
-Sender and receiver field data types must match!
-
-Data types have names with a standard format, such as:
-
-- **SFString,****SFRotation,** or **MFColor**
-
-| Character | Values                                                                |
-|-----------|-----------------------------------------------------------------------|
-| 1         | \*\*S:\*\* Single value \*\*M:\*\* Multiple values                    |
-| 2         | Always an \*\*F\*\* (for field)                                       |
-| remainder | Name of data type, such as \*\*String, Rotation,\*\* or \*\*Color\*\* |
-
-| Data type                | Meaning                                     |
-|--------------------------|---------------------------------------------|
-| SFBool, MFBool           | Boolean, true or false value                |
-| SFColor, MFColor         | RGB color value                             |
-| SFColorRGBA, MFColorRGBA | RGBA color value                            |
-| SFDouble, MFDouble       | Double precision floating point value       |
-| SFFloat, MFFloat         | Floating point value                        |
-| SFImage, MFImage         | Image value                                 |
-| SFInt32, MFInt32         | Integer value                               |
-| SFMatrix3d, MFMatrix3d   | 3×3 matrix value, double precision          |
-| SFMatrix3f, MFMatrix3f   | 3×3 matrix value                            |
-| SFMatrix4d, MFMatrix4d   | 4×4 matrix value, double precision          |
-| SFMatrix4f, MFMatrix4f   | 4×4 matrix value                            |
-| SFNode, MFNode           | Node value                                  |
-| SFRotation, MFRotation   | Rotation value                              |
-| SFString, MFString       | Text string value                           |
-| SFTime, MFTime           | Time value                                  |
-| SFVec2d, MFVec2d         | XY floating point value, double precision   |
-| SFVec2f, MFVec2f         | XY floating point value                     |
-| SFVec3d, MFVec3d         | XYZ floating point value, double precision  |
-| SFVec3f, MFVec3f         | XYZ floating point value                    |
-| SFVec4d, MFVec4d         | XYZW floating point value, double precision |
-| SFVec4f, MFVec4f         | XYZW floating point value                   |
-
-## Following naming conventions
-
-Most nodes have inputOutput fields.
-
-If the inputOutput field name is *xxx*, then:
-
-- *set\_xxx* is an input to set the field
-- *xxx\_changed* is an output that sends when the field changes
-- The *set\_* and *\_changed* sufixes are optional but recommended for clarity
-
-The [Transform](../components/grouping/transform) node has:
-
-- *rotation* field
-- *set\_rotation* input
-- *rotation\_changed* output
-
-## A sample animation
-
-### XML Encoding
-
-```xml
-<TouchSensor DEF='Touch'/>
-
-<TimeSensor DEF='Timer1' ... />
-
-<OrientationInterpolator DEF='Rot1' ... />
-
-<Transform DEF='Frame1'>
-  <Shape><!-- ... --></Shape>
-</Transform>
-
-<ROUTE fromNode='Touch' fromField='touchTime' toNode='Timer1' toField='set_startTime'/>
-<ROUTE fromNode='Timer1' fromField='fraction_changed' toNode='Rot1' toField='set_fraction'/>
-<ROUTE fromNode='Rot1' fromField='value_changed' toNode='Frame1' toField='set_rotation'/>
-```
-
-### Classic Encoding
-
-```js
-DEF Touch TouchSensor { }
-
-DEF Timer1 TimeSensor { ... }
-
-DEF Rot1 OrientationInterpolator { ... }
-
-DEF Frame1 Transform {
-  children [
-    Shape { ... }
-  ]
-}
-
-ROUTE Touch.touchTime         TO Timer1.set_startTime
-ROUTE Timer1.fraction_changed TO Rot1.set_fraction
-ROUTE Rot1.value_changed      TO Frame1.set_rotation
-```
-
-## Using multiple routes
-
-You can have **fan-out**
-
-- Multiple routes out of the same sender
-
-You can have **fan-in**
-
-- Multiple routes into the same receiver
-
-## Summary
-
-- Connect senders to receivers using routes
-- input fields are inputs, and output fields are outputs
-- A route names the sender.output, and the receiver.input
-  - Data types must match
-- You can have multiple routes into or out of a node

package/docs/_posts/tutorials/introducing-script-use.md

@@ -1,132 +0,0 @@
----
-title: Introducing Script Use
-date: 2022-11-28
-nav: tutorials-scripts-and-prototypes
-categories: [Tutorials]
-tags: [Introducing, Script]
----
-## Motivation
-
-Many actions are too complex for animation nodes:
-
-- Computed animation paths (eg. gravity)
-- Algorithmic shapes (eg. fractals)
-- Collaborative environments (eg. games)
-
-You can create new sensors, interpolators, etc., using program scripts written in:
-
-- JavaScript - easy-to-learn language
-- ECMAScript - same as JavaScript
-
-## Syntax: Script
-
-A [Script](../components/scripting/script) node selects a program script to run:
-
-- *url* - choice of program script
-
-### XML Encoding
-
-```xml
-<Script DEF='Bouncer'>
-<![CDATA[ecmascript:
-...
-]]>
-</Script>
-
-<!-- or -->
-
-<Script DEF='Bouncer'
-    url='"bouncer.js"'/>
-```
-
-### Classic Encoding
-
-```js
-DEF Bouncer Script {
-  url "ecmascript: ..."
-  #or...
-  url "bouncer.js"
-}
-```
-
-## Defining the program script interface
-
-A Script node also declares the program script interface:
-
-- **initializeOnly, inputOnly, outputOnly, inputOutput** - inputs and outputs
-  - Each has a name and data type
-  - Fields have an initial value
-
-### XML Encoding
-
-```xml
-<Script DEF='Bouncer'>
-  <field accessType='initializeOnly' type='SFFloat' name='bounceHeight' value='3'/>
-  <field accessType='inputOnly' type='SFFloat' name='set_fraction'/>
-  <field accessType='outputOnly' type='SFVec3f' name='value_changed'/>
-  <field accessType='inputOutput' type='SFBool' name='enabled' value='true'/>
-</Script>
-```
-
-### Classic Encoding
-
-```js
-DEF Bouncer Script {
-  initializeOnly  SFFloat bounceHeight 3.0
-  inputOnly       SFFloat set_fraction
-  outputOnly      SFVec3f value_changed
-  inputOutput     SFBool  enabled TRUE
-}
-```
-
-## A sample using a program script
-
-### XML Encoding
-
-```xml
-<TimeSensor DEF='Clock' ... />
-
-<Transform DEF='Ball' ... />
-
-<Script DEF='Bouncer'>
-  <field accessType='initializeOnly' type='SFFloat' name='bounceHeight' value='3'/>
-  <field accessType='inputOnly' type='SFFloat' name='set_fraction'/>
-  <field accessType='outputOnly' type='SFVec3f' name='value_changed'/>
-  <field accessType='inputOutput' type='SFBool' name='enabled' value='true'/>
-<![CDATA[ecmascript:
-...
-]]>
-</Script>
-
-<ROUTE fromNode='Clock' fromField='fraction_changed' toNode='Bouncer' toField='set_fraction'/>
-<ROUTE fromNode='Bouncer' fromField='value_changed' toNode='Ball' toField='set_translation'/>
-```
-
-### Classic Encoding
-
-```js
-DEF Clock TimeSensor { ... }
-
-DEF Ball Transform { ... }
-
-DEF Bouncer Script {
-  initializeOnly  SFFloat bounceHeight 3.0
-  inputOnly       SFFloat set_fraction
-  outputOnly      SFVec3f value_changed
-  inputOutput     SFBool  enabled TRUE
-  url "ecmascript: ..."
-}
-
-ROUTE Clock.fraction_changed TO Bouncer.set_fraction
-ROUTE Bouncer.value_changed  TO Ball.set_translation
-```
-
-## Summary
-
-The [Script](../components/scripting/script) node selects a program script, specified by a URL.
-
-Program scripts have field and event interface declarations, each with:
-
-- A data type
-- A name
-- An initial value (fields only)

package/docs/_posts/tutorials/introducing-x3d.md

@@ -1,100 +0,0 @@
----
-title: Introducing X3D
-date: 2022-11-28
-nav: tutorials-shapes-geometry-and-appearance
-categories: [Tutorials]
-tags: [Introducing]
----
-## What is X3D?
-
-X3D is:
-
-- A simple text language for describing 3-D shapes and interactive environments
-- X3D text files use a .x3d, x3dj, x3dv, or .x3db extension
-  - .x3d (XML) - save to parse
-  - .x3dj (JSON) - good for scripting
-  - .x3dv (VRML) - easy to learn
-  - x3db (Binary) - good for large models
-
->**Note:** All examples are in X3D XML and X3D Classic Encoded file format (.x3d and .x3dv).
-{: .prompt-info }
-
-## What do I need to use X3D?
-
-You can view X3D files using an X3D browser:
-
-- A X3D standalone application
-- A X3D JavaScript plug-in like to an HTML browser
-
-You can view X3D files from your local hard disk, or from the Internet.
-
-## How can X3D be used on a Web page?
-
-- Fill Web page
-- Embed into Web page
-- Fill Web page frame
-- Embed into Web page frame
-- Embed multiple times
-
-## What do I need to develop in X3D?
-
-You can construct X3D files using:
-
-- A text editor
-- A authoring tool
-- A 3D modeler and format translator
-- A shape generator (like a Python, or Perl script)
-
-## Should I use a text editor?
-
-Pros:
-
-- No new software to buy
-- Access to all X3D features
-- Detailed control of world efficiency
-
-Cons:
-
-- Hard to author complex 3D shapes
-- Requires knowledge of X3D syntax
-
-## Should I use a authoring tool?
-
-Pros:
-
-- Easy 3-D drawing and animating user interface
-- Little need to learn X3D syntax
-
-Cons:
-
-- May not support all X3D features
-- May not produce most efficient X3D
-
-## Should I use a 3D modeler and format translator?
-
-Pros:
-
-- Very powerful drawing and animating features
-- Can make photo-realistic images too
-
-Cons:
-
-- May not support all X3D features
-- May not produce most efficient X3D
-- Not designed for X3D
-- Often a one-way path from 3D modeler into X3D
-- Easy to make shapes that are too complex
-
-## Should I use a shape generator?
-
-Pros:
-
-- Easy way to generate complex shapes
-- Fractal mountains, logos, etc.
-- Generate X3D from PHP scripts
-- Common to extend science applications to generate X3D
-
-Cons:
-
-- Only suitable for narrow set of shapes
-- Best used with other software

package/docs/_posts/tutorials/lighting-your-world.md

@@ -1,144 +0,0 @@
----
-title: Lighting Your World
-date: 2022-11-28
-nav: tutorials-textures-lights-and-environment
-categories: [Tutorials]
-tags: [Lighting, World]
----
-## Motivation
-
-- By default, you have one light in the scene, attached to your head
-- For more realism, you can add multiple lights
-  - Suns, light bulbs, candles
-  - Flashlights, spotlights, firelight
-- Lights can be positioned, oriented, and colored
-- Lights do not cast shadows
-
-## Using types of lights
-
-There are three types of X3D lights:
-
-- Point lights - radiate in all directions from a point
-- Directional lights - aim in one direction from infinitely far away
-- Spot lights - aim in one direction from a point, radiating in a cone
-
-## Using common lighting features
-
-All lights have several common fields:
-
-- *on* - turn it on or off
-- *intensity* - control brightness
-- *ambientIntensity* - control ambient effect
-- *color* - select color
-
-Point lights and spot lights also have:
-
-- *location* - position
-- *radius* - maximum lighting distance
-- *attenuation* - drop off with distance
-
-Directional lights and spot lights also have:
-
-- *direction* - aim direction
-
-## Syntax: PointLight
-
-A [PointLight](../components/lighting/pointlight) node illuminates radially from a point:
-
-### XML Encoding
-
-```xml
-<PointLight
-    location='0.0 0.0 0.0'
-    intensity='1.0'
-    color='1.0 1.0 1.0'/>
-```
-
-### Classic Encoding
-
-```js
-PointLight {
-  location  0.0 0.0 0.0
-  intensity 1.0
-  color     1.0 1.0 1.0
-}
-```
-
-## Syntax: DirectionalLight
-
-A [DirectionalLight](../components/lighting/directionallight) node illuminates in one direction from infinitely far away:
-
-### XML Encoding
-
-```xml
-<DirectionalLight
-    direction='1.0 0.0 0.0'
-    intensity='1.0'
-    color='1.0 1.0 1.0'/>
-```
-
-### Classic Encoding
-
-```js
-DirectionalLight {
-  direction 1.0 0.0 0.0
-  intensity 1.0
-  color     1.0 1.0 1.0
-}
-```
-
-## Syntax: SpotLight
-
-A [SpotLight](../components/lighting/spotlight) node illuminates from a point, in one direction, within a cone:
-
-### XML Encoding
-
-```xml
-<SpotLight
-    location='0.0 0.0 0.0'
-    direction='1.0 0.0 0.0'
-    intensity='1.0'
-    color='1.0 1.0 1.0'
-    cutOffAngle='0.785'/>
-```
-
-### Classic Encoding
-
-```js
-SpotLight {
-  location    0.0 0.0 0.0
-  direction   1.0 0.0 0.0
-  intensity   1.0
-  color       1.0 1.0 1.0
-  cutOffAngle 0.785
-}
-```
-
-- The maximum width of a spot light's cone is controlled by the cutOffAngle field
-- An inner cone region with constant brightness is controlled by the beamWidth field
-
-### XML Encoding
-
-```xml
-<SpotLight
-    ...
-    cutOffAngle='0.785'
-    beamWidth='0.52'/>
-```
-
-### Classic Encoding
-
-```js
-SpotLight {
-  ...
-  cutOffAngle 0.785
-  beamWidth   0.52
-}
-```
-
-## Summary
-
-- There are three types of lights: point, directional, and spot
-- All lights have an on/off, intensity, ambient effect, and color
-- Point and spot lights have a location, radius, and attenuation
-- Directional and spot lights have a direction