Table of Contents Previous Chapter Details Viewpoint Slideshow Next Chapter Details X3D Resources

X3D Example Archives: Conformance Nist, Miscellaneous, EXTERNPROTO

X3D Scenes Descriptions
different name This tests browser ability to assign a different name to an EXTERNPROTO node from the name defined in the URL file. In this case the EXTERNPROTO name of "BallProto" is assigned to a PROTO named "Second_proto", which is in the URL file assigned to the EXTERNPROTO. As a result, a red Sphere should be rendered in this world.
different name proto This is a collateral file used in other tests for this node.
first proto This tests browser ability to select the first PROTO it finds in a wrl file if no PROTOname is supplied at the end of the URL in an EXTERNPROTO declaration. Three PROTOs are contained in the file first_proto_proto.x3d. The first PROTO generates a green Sphere geometry. PROTO #2 generates a white Sphere geometry. PROTO #3 generates a blue Sphere. Because no specific PROTO name is specified in the URL field of the EXTERNPROTO, the browser should select the first PROTO in the file, and render the green Sphere.
first proto file This is a collateral file used in other tests for this node.
first proto proto This is a collateral file used in other tests for this node.
ignore externproto This tests browser ability to ignore EXTERNPROTO statements in a file and select only PROTOs. The URL following an EXTERNPROTO references a file containing both a PROTO and an EXTERNPROTO statement. The PROTO generates a red Sphere geometry. The EXTERNPROTO references a file generating a green Sphere geometry. The browser should select the PROTO name, and generate a red Sphere geometry.
multi url specific This tests browser ability to select a specific PROTO if a #PROTOname is supplied at the end of the URL in a "list" of URLs. Two wrl file URLs are contained in the file URL list at the end of the EXTERNPROTO declaration. The first contains 3 PROTOs, however, none have # a name of "Red_sphere". The browser should continue its search for the PROTO name in the next URL. The next URL contains 3 PROTOs, one of which has a matching PROTO name. This PROTO should be used, and rendered as a red Sphere.
multi url specific nofile This tests browser ability to select a specific PROTO if a "#PROTOname" is supplied at the end of the URL in a "list" of URLs, but one of the URL files does not exist. Two wrl file URLs are contained in the file URL list at the end of the EXTERNPROTO declaration, however the first file does not exist. The second file contains 3 PROTOs, with one matching the PROTO name of "Red_sphere" specified after the EXTERNPROTO statement. Because the first file does not exist, the browser should continue its search for the PROTO name in the next URL, and find the matching PROTO name. This PROTO should be used, and rendered as a red Sphere.
second proto file This is a collateral file used in other tests for this node.
specific proto This tests browser ability to select a specific PROTO in a wrl file if a "#PROTOname" is supplied at the end of the URL in an EXTERNPROTO declaration. Three PROTOs are contained in the file "first_proto_proto.x3d". Proto #1 generates a green Sphere geometry. PROTO #2 generates a red Sphere geometry. PROTO #3 generates a blue Sphere geometry. Because the second PROTO name is specified in the URL field of the EXTERNPROTO statement, the browser should select the second PROTO and render the red Sphere.
specific proto proto This is a collateral file used in other tests for this node.

Online at http://www.web3d.org/x3d/content/examples/ConformanceNist/Miscellaneous/EXTERNPROTO

Master source code archive is under subversion control at
http://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/content/examples/ConformanceNist/Miscellaneous/EXTERNPROTO

Table of Contents Previous Chapter Details Viewpoint Slideshow Next Chapter Details X3D Resources

Also available: current and archived nightly builds and distributions of these examples, all published under an Open-Source License.

The X3D Resources: Examples page and Savage Developers Guide provide more information about the production of this archive.