The Eolas vs Internet Explorer case has been getting a lot of attention lately, since it is almost time the patch is released in the wild. To make a long story short: Internet Explorer 6 and the upcoming version 7 will display plugin content differently from the 'seamless' experience we're used to. Whereas most plugins (Flash, Windows Media) will 'only' require an additional click to enabled interactivity, some plugins such as Quicktime and Shockwave result in an ugly dialog box when they are found on a page. The official workaround has authors rewrite each HTML page containing the 'offending' tags substantially.
Director has a bit of a bad habbit of ignoring the mime-type, or even the filename in the header of a file when you import it through importFileInto or setting the fileName property of a member in Shockwave. This means that it is not possible to load eg an image through a php script; Shockwave/Director only sees the .php extension it requested, and does not recognise that as an image format. As a result the image will not import. Since php is often used to 'glue' Shockwave movies to a database, this inability can be quite a problem. Personally, I am using PHP scripts to digest complex files into chunks that Shockwave can handle (ie: load embedded jpg frames from quicktime vr files).
While waiting from a fix from either 'formerly Macromedia' or the Firefox team, here's what I use to work around the float() deficiency on European systems with Firefox 1.5:
Instead of using float() to convert a string to a float, I am now using myFloat(). myFloat() first checks if the current system is affected (seeing if a float is actually a float), and if so changes periods to commas.
With all my complaining about Safari and Shockwave, you'ld almost forget there are other browsers with issues regarding Shockwave. Firefox 1.5 has been released recently, and many people are complaining about the new browser having issues with plugins in general; they just won't 'play'.
The deal was finalised last week, but starting today the macromedia.com website has been slightly restyled(*) and heads 'Adobe, formerly macromedia'
What this means for Director, Shockwave, and ultimately SPi-V is unclear, but I have no reason to believe things will change dramatically in the near future. Director is still Macromedia Director, so SPi-V 1.3 will probably still launch 'powered by Macromedia Shockwave'...
(*) As a tribute to macromedia, I am going to stick with the original Macromedia gradient I ripped for the Director subtheme on hoeben.net ;-)
Today's the first conference day of Spark, Europe's Premier Flash Event. I am looking forward to being inspired, and learning about where Flash is heading. Panorama-wise, I am ofcourse more of a Shockwave person, but for my new job at Avinity I am doing more and more flash work...
Thomas Higgins picks up on my note on dir3d-l (after Iwan Baan told me) that OS X 10.4.3 has just been released and it finally fixes the 3d offset bug that has been paguing Shockwave 3d (and SPi-V) on Safari since version 1 (and the betas before).
The webkit nightly builds are pretty sweet in combination with SPi-V. The fieldOfView fullscreen panorama gallery now contains an experimental build that detects the nightly build and disables the fixes that were necessary before. SPi-V goodness in Safari at last!
To celebrate, I updated the panoramas to include the screensaver behavior scriptlet from SPi-V dev, through a nice new feature of the upcoming SPi-V 1.3. Leave the panorama alone for a good couple of seconds, and it will start to automatically show you around...
So, the good news is that SPi-V will run better in Safari in the foreseeable future, when this version of Webkit makes it to an official release of Safari. If you use the current version of SPi-V (eg the fullscreen panoramas gallery) with the new nightly build, you will see a black bar at the top of the window, whereas there used to be a black bar at the bottom.