fieldOfView | SPi-V devEmbed in Style
Upcoming changes in Internet Explorer on Windows system affect the way plugins are embedded in a webpage. SPi-V is a Shockwave movie, and as such it is affected by this change.
When a patched/new version of Internet Explorer for Windows encounters a piece of Shockwave content (or Quicktime, or many other types of plugin content as well), it will present the end user with an unsightly dialog. For more information about the exact changes, please consult this article on Microsoft's MSDN website.
A workaround is suggested by both Microsoft and Macromedia, which involves embedding the Shockwave (or other plugin) content using an external javascript file. This article proposes a more elegant solution, that adds benefits to the otherwise unwelcome changes.
to be completed
The embed in style mechanism is currently employed in both the SPi-V gallery (except the legacy demos) and the fullscreen gallery.
Re: Embed in Style
At the bottom of the article there are 2 links:
1. to the SPI-V gallery and
2. to the fullscreen gallery.
From what I can see both have the same destination and I can only find ONE gallery.
Where is the other?
Re: Embed in Style
Oops. fixed
Re: Embed in Style
If I understand properly the headline "Embed in Style" does not refer to the "article on Microsoft's MSDN website" but to the "workaround .. suggested by both Microsoft and Macromedia".
Once you will complete this article please do not only let us know the link to the workaround article but also let us see the entire script which you already have employed in the galleries.
Unfortunately my knowledge does not allow me to identify and eliminate the "embed in style mechanism" in the gallery page.
Re: Embed in Style
This project is about an alternative to the workaround suggested by Microsoft/Adobe. My version is more 'AJAX-like' than theirs, and will allow for some very nice additional features.
I never got round to finishing this article, and plan to change/add to my own method in the SPi-V 1.4 timeframe.
Re: Embed in Style
I would very much like to see the style sheet! You can see my xsl/xml aspx and vr's at my site www.dlgreene.com follow links code -> code-info all the pages have w3c and css check buttons at the bottom of the page. All buttons are functional checks and will allow you to see the css.
I am very interested in SPi-V. I'm a bit of a block head when it comes to the Adobe jargon. Will SPi-V work in Flash? This Adobe stuff is a bit like "who's on first and what's on second" I can't tell if Shockwave is using the same object as what I am currently using to view *.swf files that I make in Pano2QTVR? Is Shockwave Flash?
Shockwave vs Flash
Shockwave and Flash are two different technologies. Shockwave files (.dcr) are created using Adobe Director while Flash files (.swf) are created with Adobe Flash and other tools (such as Pano2VR). Director predates Flash, but has some interesting features that Flash does not have. Most significantly, it can tap into 3d hardware acceleration.
Interestingly, Shockwave can play Flash files (currently up to Flash version 8), but the reverse is not possible; the Flash player can not display Shockwave content, so it can not display SPi-V at this time.
Re: Embed in Style
Never mind...
I see the javascript on the class. The problem is that this style of function without allowing the end user to activate the object explicitly puts the browser in a "hinky" state of affairs. I notice that you have the vr's showing full screen using up the entire window. You MUST do this because if you didn't and the vr is in the browser's cashe the vr(object) won't allow the other parts of the page to refresh. This is precisely the problem I have now. Something about the way Adobe works or how Adobe programmers work I can't tell which. DevalVR nor PureTools need to take over the entire window to "stay in the object"(programmatically) Both of these viewers allow for full screen but they don't mess up the browser. Note that with the other viewers they have a "border" of sorts whereas SPi-V nor Flash(swf) do... Except when I use object but then they can't go full screen. Why not? I fully understand they are in an object in javascript but clearly there IS a differance. If there was no differance I could use the "Flash Satay Method" for flash and it would still have the capability to go full screen.
I still think I like SPi-V better that the Pano2QTVR swf's that I currently create. I think SPi-V is better viewing. If I can set up a toolbar like Pano2QTVR, DevalVR, or PureTools I will get a licence.
Re: Embed in Style
Using my 'embed in style' method, there is no 'hinky' state of affairs. You can style the div that gets replaced by the Shockwave object any which way you like, at any size within the browser window. That is the beauty of my method. It is just that by default - if you don't specify a width/height - the object fills the entire browser window. But if you add a style to the div, it should be respected.
I'm afraid I don't quite understand you.
A toolbar scriptlet is available here:
http://www.fieldofview.com/spv-dev/downloads#scriptlets
Re: Embed in Style
This is difficult to explain... Mostly because it happens to some and not to others. The only thing that may give you a very clear visual clue is to look at the differance in the focus of the differant veiwers at my site...
http://www.dlgreene.com/vr_flash.aspx?panid=2006-10-08_15-00-02
Note this takes you to the flash vr that has a similar visual clue that your method has. As you move your mouse cursor across the vr notice that there is NO visual clue that the object want's focus. Now view in any of the other viewers and notice the border around the object. This is NOT the border that I have set... It is a visual clue that the object has for all objects that "Please whatever to activate this control".
If I didn't use javascript on the flash swf flash would have the same border. Look at many of the site examples that you have here (not yours but other) and you can see the differance in the "focus" on start up.
This differance, if you see it, is only a clue for you that there is most likely a problem for others.
When flash is in this state on opening the window (no border or asking for selection) Flash or Shockwave "thinks" it owns the page and if the vr is in the browsers cashe won't even refresh(repaint) the window. Adobe "sucks up" the focus and it's even difficult to use the browsers menu.
Adobe programmers will assume that "this end user is an idiot" and dismiss this problem out of hand. Unfortunatly I am not alone and I have seen message after message talking and pleading for an answer but Adobe programmers don't believe it exists.
Let me add that I have shut the autorotate off on start up for the flash vrs that I use this seems to "fix" the problem. At least it doesn't have the "browser freezing effect". You need to be very careful that when you start your vrs that there is no autorotate or similar "focus sucking" continueous events happening on start of the object when you use this method.