Prev: Communication with embedded shockwave
Next: Drag and Drop Problem
From: _eyesonly on 22 Apr 2008 14:14
ALL Director developers should read this:
http://www.adobedirectoronline.com/tutorials/tutorial_backwardCompatability.php

If you do not (at the minimum) make changes to the page containing your
shockwave file, the content will break. You must include the
TYPE="application/x-director" playerVersion="10" parameter in your embed/object
tags or the shockwave loader screen appears and nothing ever loads

This is a major departure from how Macromedia handled Director updates. Under
Macromedia backwards compatibility was an important feature for both platforms.
Under Adobe not only are we forced to make edits so that pre Director 11
content is supported, the backwards compatibility is supported on WINDOWS only!

For this reason I am no longer recommending that customers update to shockwave
11 until Adobe corrects this problem for all platforms and resumes backwards
compatibility for older Director content. The temporary fix instituted by the
team in Bangalore is serving to undermine the Director community's breadth of
existing content that by and large is still ahead of its time. Also there
appear to be other bugs introduced into the content so this developer is
converting shockwave content to downloadable executables for the Mac platform.




From: tr on 23 Apr 2008 13:23
from the article:

"Whenever the content earlier to Director 11 is played, Adobe Shockwave
Player needs to understand the version of the content to enable smooth
playback of that content. For this purpose a new and efficient approach is
adopted."

They either mean it's efficient for them or there is a different definition
for the word efficient than I'm used to.

How sad.


From: _eyesonly on 24 Apr 2008 01:14
not only that but I have some DirMX sw3d content content that when run under
shockwave 11 (playerVersion=11) it uses a different coordinate system than the
one specified by the w3d used in the scene thereby throwing off all the camera
position calculations.


From: _eyesonly on 24 Apr 2008 15:00
SO far I have not even found a system (MAC or PC) where the compatibility
operation actually succeeds. The plugin simply goes to a screen where it says
the compatibility components are downloading and then just hangs. THis is
historically the first release of shockwave where an update actually breaks all
prior content. Setting the playerVersion=10 guarantees a hanging request for
compatibility components that dont appear to exist and playing the content as
sw11 introduces so many bugs that 3d content is unplayable
I am actually writing a Javascript detection scheme to check for sw11 and deny
viewing saying they have an incompatible plugin.
Comeon Adobe, this is pathetic, you have to actually make the compatibility
solution work 100% of the time. Macromedia left quite a high standard on
compatibilty issues that Adobe seems to fall severely short of the mark on

 | 
Pages: 1
Prev: Communication with embedded shockwave
Next: Drag and Drop Problem