These tags are not recognised by your 2D browser and so will not affect the rendering of your page in 2D. What they will do is tell ExitReality to go and find 3D resources to include in your transmogrified webspace.
The X3D tags are defined by their respective PROTO definitions. You can view the definitions within the respective files in your cache. For example, to see the definition for the X3D-INLINE tag, open the file X3DINLINE.wrl that appears in your cache (once you have accessed them).
In order to make sure that you can view these files from your cache, you might like to visit the files using your browser. You won't see anything, but after you do this the files will be in your cache for you to open in VrmlPad (or NotePad etc.).
http://tpl.exitreality.com/3ss/X3DINLINE.wrl
http://tpl.exitreality.com/3ss/X3DSTYLESHEET.wrl
http://tpl.exitreality.com/3ss/X3DSTRING.wrl
http://tpl.exitreality.com/3ss/X3DTRANSFORM.wrl
<X3D-INLINE>
The X3D-INLINE tag tells the browser to inline a .wrl file. It works similar to the Inline node. If you open the X3DINLINE.wrl file from your cache you will see that one of the exposedFields is url. This will accept a URL parameter from the X3D-INLINE tag.
E.g., within the html of a webpage:
<X3D-INLINE url="http://lib.exitreality.com/objects/telias.free.fr/boat/boat.wrl">
</X3D-INLINE>
This will place the object defined by boat.wrl at the position within the Body node relative to the position of the tag in the html. That is to say, if you put the tag at the end of your html then the boat will appear at the end of your transmogrified 3D webspace.
<X3D-STYLESHEET>
The X3D-STYLESHEET tag is very similar to the X3D-INLINE tag, only it doesn't account for the position of the tag, and it will over-ride any x3d-stylesheet parameter in your button tag (if you have one, having saved decorations to the page in the normal way). If you don't want to mess with your saved decorations, use the X3D-INLINE tag.
<X3D-STRING>
The X3D-STRING tag performs a similar function again, only the 3D objects are defined directly within the tag, rather than in an external file. It takes a single parameter string which needs to be valid VRML. A VRML header is not required.
<X3D-STRING string="Box { }">
</X3D-STRING>
<X3D-STRING string="Transform { translation 10 0 0 children [ Cone { } ] }">
</X3D-STRING>
These are very simple examples, but you can make the VRML as complex as you like. There must not be any line breaks in the string though. It must all be on the same line.
