| 1 |
<?xml version="1.0" encoding="UTF-8"?>
|
| 2 |
<!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 3.0//EN" "https://www.web3d.org/specifications/x3d-3.0.dtd">
|
| 3 | <X3D profile='Immersive' version='3.0' xmlns:xsd='http://www.w3.org/2001/XMLSchema-instance' xsd:noNamespaceSchemaLocation='https://www.web3d.org/specifications/x3d-3.0.xsd'> |
| 4 | <head> |
| 5 | <meta name='title' content=' X3DRetreatProtoExercise.x3d '/> |
| 6 | <meta name='creator' content='Don Brutzman'/> |
| 7 | <meta name='created' content='25 May 2000'/> |
| 8 | <meta name='modified' content='20 October 2019'/> |
| 9 | <meta name=' error ' content=' Contains multiple intentional warnings and errors, for validation testing purposes. '/> |
| 10 | <meta name='description' content='Solutions to the Proto Exercise posed by Chris Marrin of SONY at the May 2000 X3D Retreat. This exercise includes intentionally illegal VRML and does not render.'/> |
| 11 | <meta name='reference' content=' https://www.web3d.org/x3d/sony/X3DRetreatProtoEx.html '/> |
| 12 | <meta name='identifier' content=' https://www.web3d.org/x3d/content/examples/development/X3DRetreatProtoExercise.x3d '/> |
| 13 | <meta name='generator' content=' X3D-Edit 3.1, https://www.web3d.org/x3d/content/README.X3D-Edit.html '/> |
| 14 | <meta name='license' content='../license.html'/> |
| 15 | </head> |
| 16 | <Scene> |
| 17 | <!-- ============= Example 1 ============= --> |
| 18 | <!-- GeometryNode and ChildNode are not valid node types, so used type Node/Nodes instead. --> |
| 19 | <!-- Note exercise example is incomplete and has no node(s) defined for body content. --> |
| 20 | <!-- X3D DTD can correctly detect these content errors if they occur, scene will be well-formed but not valid. --> |
| 21 | <ProtoDeclare name='MyProto'> |
| 22 | <ProtoInterface> |
| 23 | <field name='geometry' type='SFNode' value='NULL' accessType='initializeOnly'/> |
| 24 | <field name='children' type='MFNode' value='NULL' accessType='initializeOnly'/> |
| 25 | </ProtoInterface> |
| 26 | <ProtoBody> |
| 27 | <WorldInfo info='"Added this node as PROTO body, so that the example can be valid VRML"'/> |
| 28 | </ProtoBody> |
| 29 | </ProtoDeclare> |
| 30 | <!-- ============= Example 2 ============= --> |
| 31 | <!-- Adding new fields to an existing node. --> |
| 32 | <!-- Corrected example by moving Material from PROTO interface to PROTO body. --> |
| 33 | <ProtoDeclare name='PhysicalMaterial'> |
| 34 | <ProtoInterface> |
| 35 | <field name='mass' type='SFFloat' value='1' accessType='inputOutput'/> |
| 36 | <field name='hardness' type='SFFloat' value='1' accessType='initializeOnly'/> |
| 37 | <field name='friction' type='SFFloat' value='1' accessType='initializeOnly'/> |
| 38 | </ProtoInterface> |
| 39 | <ProtoBody> |
| 40 | <Material DEF='M'/> |
| 41 | <!-- EXPORT M (this is Blendo nomenclature, not VRML 97) --> |
| 42 | </ProtoBody> |
| 43 | </ProtoDeclare> |
| 44 | <!-- ============= Example 3a ============= --> |
| 45 | <!-- Consider new possibility of declaring a field PROTO. --> |
| 46 | <!-- Again no body provided in this example (since goal is a new FieldPROTO construct). --> |
| 47 | <ProtoDeclare name='Plane'> |
| 48 | <ProtoInterface> |
| 49 | <!-- FIELDPROTO --> |
| 50 | <field name='normal' type='SFVec3f' value='0 0 1' accessType='initializeOnly'/> |
| 51 | <field name='distance' type='SFFloat' value='0' accessType='initializeOnly'/> |
| 52 | </ProtoInterface> |
| 53 | <ProtoBody> |
| 54 | <WorldInfo info='"Added this node as PROTO body, so that the example can be valid VRML"'/> |
| 55 | </ProtoBody> |
| 56 | </ProtoDeclare> |
| 57 | <!-- ============= Example 3b ============= --> |
| 58 | <!-- Example 3b employs the supposed field PROTO. --> |
| 59 | <!-- X3D DTD currently restricts field types to VRML 97 types, and so flags these untyped fields as an error. --> |
| 60 | <!-- We could allow unspecified field types, but would lose checking (and authoring suggestions) on existing types. --> |
| 61 | <ProtoDeclare name='BSPLeaf'> |
| 62 | <ProtoInterface> |
| 63 | <!-- Intentionally invalid type values used. --> |
| 64 | <field name='plane' type='Plane' value='0 0 1 0' accessType='initializeOnly'/> |
| 65 | <field name='front' type='BSPLeaf' value='NULL' accessType='initializeOnly'/> |
| 66 | <field name='back' type='BSPLeaf' value='NULL' accessType='initializeOnly'/> |
| 67 | <field name='children' type='MFNode' value='NULL' accessType='initializeOnly'/> |
| 68 | </ProtoInterface> |
| 69 | <ProtoBody> |
| 70 | <WorldInfo info='"Added this node as PROTO body, so that the example can be valid VRML"'/> |
| 71 | </ProtoBody> |
| 72 | </ProtoDeclare> |
| 73 | <!-- ============= Example 4 ============= --> |
| 74 | <!-- PROTO with routes. Example nodes moved from interface definition to body. --> |
| 75 | <ProtoDeclare name='SpinGroup'> |
| 76 | <ProtoInterface> |
| 77 | <!-- Example 4 calls three of the field references ROUTEs, but they actually match VRML 97 'IS' statements. IS="TS.cycleInterval" IS="TS.startTime" IS="TS.stopTime" --> |
| 78 | <field name='speed' type='SFTime' value='1' accessType='initializeOnly'/> |
| 79 | <field name='startTime' type='SFTime' value='0' accessType='initializeOnly'/> |
| 80 | <field name='stopTime' type='SFTime' value='0' accessType='initializeOnly'/> |
| 81 | </ProtoInterface> |
| 82 | <ProtoBody> |
| 83 | <!-- Corrected example by moving nodes T, G, TS and OI from PROTO interface to PROTO body. --> |
| 84 |
<!-- ROUTE information for T node:
[from OI.value_changed to set_rotation
]
-->
<Transform DEF='T'> |
| 85 | <!-- EXPORT G (this is Blendo nomenclature, not VRML 97) --> |
| 86 | <Group DEF='G'/> |
| 87 | </Transform> |
| 88 |
<!-- ROUTE information for TS node:
[from fraction_changed to OI.set_fraction
]
-->
<TimeSensor DEF='TS' loop='true'/> |
| 89 |
<!-- ROUTE information for OI node:
[from TS.fraction_changed to set_fraction
]
[from value_changed to T.set_rotation
]
-->
<OrientationInterpolator DEF='OI' key='0 0.25 0.5 0.75 1' keyValue='0 1 0 0 0 1 0 1.57 0 1 0 3.14 0 1 0 4.71 0 1 0 0'/> |
| 90 | < ROUTE fromNode='TS' fromField='fraction_changed' toNode='OI' toField='set_fraction'/> |
| 91 | < ROUTE fromNode='OI' fromField='value_changed' toNode='T' toField='set_rotation'/> |
| 92 | </ProtoBody> |
| 93 | </ProtoDeclare> |
| 94 | <!-- ============= Example 5 ============= --> |
| 95 | <!-- Show "overriding of a method of the inherited interface." --> |
| 96 | <!-- X3D DTD currently restricts field types to VRML 97 types, other values can be entered but are flagged as invalid. IS="RENDERscript.plane" IS="RENDERscript.front" IS="RENDERscript.back" --> |
| 97 | <ProtoDeclare name='BSPLeaf'> |
| 98 | <ProtoInterface> |
| 99 | <field name='plane' type='Plane' value='0 0 1 0' accessType='initializeOnly'/> |
| 100 | <field name='front' type='BSPLeaf' value='NULL' accessType='initializeOnly'/> |
| 101 | <field name='back' type='BSPLeaf' value='NULL' accessType='initializeOnly'/> |
| 102 | </ProtoInterface> |
| 103 | <ProtoBody> |
| 104 | <!-- Here is a curious example problem: an unattached function overriding an unspecified (but commonly occuring) implementation-specific browser function. --> |
| 105 | <!-- This solution wraps a Script node around the render () function to maintain VRML 97 semantics. --> |
| 106 | <!-- Preprocessing can automate this process of wrapping a Script node around inline functions. --> |
| 107 | <!-- Corrected example by moving Group G (renamed GG) from PROTO interface to PROTO body. --> |
| 108 | <Group DEF='GG'/> |
| 109 | <Script DEF='RENDERscript'> |
<![CDATA[
ecmascript:
function render()
{
var result = plane.onPlane(System.sceneManager.getCameraPos());
if (result < 0) {
front.render();
G.render();
back.render();
}
else if (result > 0) {
back.render();
G.render();
front.render();
}
else {
front.render();
back.render();
}
}
]]>
|
|
| 111 | </Script> |
| 112 | </ProtoBody> |
| 113 | </ProtoDeclare> |
| 114 | <!-- ============= Example 6 ============= --> |
| 115 | <!-- Show "inclusion of field scripts which execute whenever the field receives an event." --> |
| 116 | <ProtoDeclare name='AnimatedMaterial'> |
| 117 | <ProtoInterface> |
| 118 | <!-- FROM is Blendo nomenclature, expressed using IS references. IS="timeBase.startTime" IS="timeBase.stopTime" --> |
| 119 | <field name='startTime' type='SFTime' value='0' accessType='initializeOnly'/> |
| 120 | <field name='stopTime' type='SFTime' value='0' accessType='initializeOnly'/> |
| 121 | <field name='startColor' type='SFColor' value='0 0 0' accessType='initializeOnly'/> |
| 122 | <field name='endColor' type='SFColor' value='0 0 0' accessType='initializeOnly'/> |
| 123 | <!-- During the December 3 1999 x3d-contributors meeting, Chris showed how --> |
| 124 | <!-- the VRML 97 specification allows an SF/MFNode field node to be initialized with node content. --> |
| 125 | <!-- This construct is now permitted by DTD, here is an example: --> |
| 126 | <field name='initializedChildren' type='MFNode' accessType='initializeOnly'> |
| 127 | <Group bboxCenter='1 2 3'/> |
| 128 | <Transform translation='1 2 3'/> |
| 129 | </field> |
| 130 | </ProtoInterface> |
| 131 | <ProtoBody> |
| 132 | <!-- Moved the following content nodes from PROTO interface to PROTO body in order to match valid VRML 97 content. --> |
| 133 |
<!-- ROUTE information for MM node:
[from CI.value_changed to set_diffuseColor
]
-->
<Material DEF='MM'/> |
| 134 | <ProtoInstance name='IntervalSensor'> |
| 135 | <fieldValue name='timeBase'> |
| 136 | <ProtoInstance name='TimeBase' DEF='timeBase'/> |
| 137 | </fieldValue> |
| 138 | </ProtoInstance> |
| 139 |
<!-- ROUTE information for CI node:
[from value_changed to MM.set_diffuseColor
]
-->
<ColorInterpolator DEF='CI' key='0 0.5 1'/> |
| 140 | <Script DEF='AnimatedMaterialInitialize'> |
<![CDATA[
ecmascript:
{ // simple exercise for reader to initialize/update PROTO field values
// to the MM Material node. Be sure to add some IS statements to match.
}
]]>
|
|
| 142 | </Script> |
| 143 | < ROUTE fromNode='CI' fromField='value_changed' toNode='MM' toField='set_diffuseColor'/> |
| 144 | </ProtoBody> |
| 145 | </ProtoDeclare> |
| 146 | </Scene> |
| 147 | </X3D> |
Event Graph ROUTE Table entries with 3 ROUTE connections total, showing X3D event-model relationships for this scene.
Each row shows an event cascade that may occur during a single timestamp interval between frame renderings, as part of the X3D execution model.
|
TS
TimeSensor fraction_changed SFFloat |
OI
OrientationInterpolator set_fraction SFFloat |
then
|
OI
OrientationInterpolator value_changed SFRotation |
T
Transform set_rotation SFRotation |
| line 134
ProtoInstance IntervalSensor |
No direct ROUTE connection found for events to/from this node. This ProtoInstance contains SFNode/MFNode fieldValue declaration with direct access to other nodes, and thus has potential to produce run-time animation. |
|
timeBase
ProtoInstance TimeBase |
No direct ROUTE connection found for events to/from this node. This ProtoInstance contains SFNode/MFNode fieldValue declarations with direct access to other nodes, and thus has potential to produce run-time animation. |
<!--
Color-coding legend: X3D terminology
<X3dNode
DEF='idName' field='value'/>
matches XML terminology
<XmlElement
DEF='idName' attribute='value'/>
(Light-blue background: event-based behavior node or statement)
(Grey background inside box: inserted documentation)
(Magenta background: X3D Extensibility)
<ProtoInstance name='ProtoName'>
<field
name='fieldName'/> </ProtoInstance>
-->
<!--
For additional help information about X3D scenes, please see X3D Tooltips, X3D Resources, and X3D Scene Authoring Hints.
-->