[X3D-Public] Web3D.org Front Page

[GLG]

Yes Joe, I realized the 'type' element in <object> was not
likely the same thimg as in <embed>. But it was worth a try
to see what happens. As it turns out, nested <object> tags
do not work in Firefox. 

With the correct 'type=application/x-oleobject' all I get is
a blank page/frame. 

When attempting to use the <embed>
'type="application/x-cc3d"' Firefox complains that a plugin
needs to be installed. 

Looks like I'll continue to rely on <embed> for a while
until <object> is fully sorted out in Firefox.

Lauren


>-----Original Message-----
>From: Joe D Williams [mailto:joedwil at earthlink.net]
>Sent: Monday, June 22, 2009 12:49 AM
>To: info at 3dnetproductions.com; 'Braden McDaniel'; x3d-
>public at web3d.org
>Subject: Re: [X3D-Public] Web3D.org Front Page
>
>HI Lauren,
>Both <object> and <embed> can include a type.
>One thing is: Is the type the same in both the use in
>object and in
>embed.
>The classid in object may not work if the type is not
>registered by
>the classid you are trying to invoke. LIkewise for the
>embed the type
>is different and that may allow the plugin to be picked.
>Or, there may
>be only the one .wrl browser installed. So you are seeing
>it work but
>there are definately some potential problems and incolplete
>statements
>in there so without further detailed looking and trying, I
>can't tell
>you exactly how or why it is working.
>Good Luck and Best Regards,
>Joe
>
>----- Original Message -----
>From: "GLG" <info at 3dnetproductions.com>
>To: "'Joe D Williams'" <joedwil at earthlink.net>; "'Braden
>McDaniel'"
><braden at endoframe.com>; <x3d-public at web3d.org>
>Sent: Sunday, June 21, 2009 12:28 PM
>Subject: RE: [X3D-Public] Web3D.org Front Page
>
>
>>
>>> As Joe notes, you should be able to use a nested object
>> element (without classid) in place of the embed element.
>>
>> That seems like a sensitive solution, but so far <embed>
>has
>> allowed us to specify 'TYPE="application/x-cc3d"' which
>> appears to successfully help select the correct plugin
>> (Contact in this case - testing with Firefox 3.0.8).
>Perhaps
>> I should try the above type in nested <object> instead of
>> the 'type=application/x-oleobject' we now use. Will
>report
>> on that in a few days.
>>
>> If you'd like more specifics please see
>> www.officetowers.com, click "Connect to Server, Start,
>> Enter, that will take you to the loading page in
>question.
>> Thanks for all of the input Joe and Braden.
>>
>> Lauren
>>
>>
>>>-----Original Message-----
>>>From: Joe D Williams [mailto:joedwil at earthlink.net]
>>>Sent: Sunday, June 21, 2009 1:21 PM
>>>To: info at 3dnetproductions.com; 'Braden McDaniel'; x3d-
>>>public at web3d.org
>>>Subject: Re: [X3D-Public] Web3D.org Front Page
>>>
>>>
>>>
>>>
>>>
>>>----- Original Message -----
>>>From: "GLG" <info at 3dnetproductions.com>
>>>To: "'Braden McDaniel'" <braden at endoframe.com>; <x3d-
>>>public at web3d.org>
>>>Sent: Sunday, June 21, 2009 2:29 AM
>>>Subject: Re: [X3D-Public] Web3D.org Front Page
>>>
>>>
>>>>I am saying if you need to use classid in <object> to
>load
>>>a
>>>> particular plugin in IE, then you must use <embed> as
>>>well
>>>> for firefox to be able to load that plugin (or another
>>>one
>>>> to handle the mime type). In other words, using classid
>>>in
>>>> <object> will cause it to malfunction in firefox.
>>><object>
>>>> will work in firefox without classid, but using it
>breaks
>>>> it. So if the <object> tag is broken then you'll need
>>>> <embed> to fall back on. At least that is my
>experience.
>>>
>>>Well that is correct, but there was a time when Ff didn't
>>>understand
>>><object>, so <embed> was required for fallback. Now all
>>>browsers will
>>>accept <object> so the fallback here could be another
>>><object> without
>>>@classid and that would work.
>>>However, later browsers are now just overlooking classid
>>>rather than
>>>failing, so in the latest you might fine you need no
>>>fallback except
>>>maybe some text if the X3D browser can't be found.
>>>
>>>At this time it might be good to test the W3C browsers
>you
>>>are
>>>interested in and see which uses the fallback, maybe by
>>>having a
>>>different X3D file name in the fallback content.
>>>Best Regards,
>>>Joe
>>
>>