[X3D-Public] Web3D.org Front Page

Joe D Williams joedwil at earthlink.net
Sat Jun 6 21:27:14 PDT 2009

Hi Paul,
Rather than all that going on in previous response, I should just say 
show the code:)

>    <object id='showx3dlogo' class='X3D3Dlogo'
>      type='model/x3d-vrml' data='x3d_logo7c.x3dv'
>      style='width:176px;height:112px;' title'Welcome to X3D'>
>      <param name="src" value="x3d_logo7c.x3dv">
>      <param name="DASHBOARD" value="FALSE">
>        <img src="x3dTag_176x86.png"
>          alt="View X3D Content in real-time">
>    </object>

is the basic code for the guts part of the web3d.org front page inside 
<div id='exampleHomeBlock'> and other block, but that is the 
suggestion. It moves the existing png to fallback content.

I think if the file was .x3d and type model/x3d_xml this would work 
fine in latest updated W3C and X3D browsers.
I am taking a cut at the transcoding now.

I know there is an advantage in generating the element with script but 
that is diminished in the current html <object> implementations and I 
think the idea of allowing for old browsers is off the list of stuff 
to do. Fine in its day but gratefully I think/hope its day is done and 
we can count on the W3C browser to deal with mimes and file extensions 
in a reasonable and predictable way.

At least that is what I am seeing. Simple is better and is getting 
betterer as I see it.

It would even be more simple if on the X3D side, all X3D browsers 
accepted src='url' and so drop the data attr. I haven't checked that 
in a while.

The 'sandbox' feature seems to be taking shape as an authoring feature 
of your web page so you can tell what you want your web page to allow 
for an embedded object. That is, if you as an author put no 
restrictions on the <object> then the thing is produced as a 
full-featured nested browsing context in the host DOM. With its own 
context name, even.
It is still may be up to the user/administrator to allow permission 
for some steps, but at least the interface produced by the W3C browser 
for install/run permissions etc, and for manually registering 
mimes/extenstions, is converging to be mostly consistent and 
understandable and finally more controllable by the user. And fallback 
is more consistent for the X3D in HTML/XHTML author.

Thanks Again and Best Regards,

More information about the X3D-Public mailing list