26April2006 CODE fixes for PTVIEWER,  QTVR and FLASH -Tested

Because I have colored text here it is not wise to copy this code.

Suggest downloading the scripts zip file from here

http://360texas.com/sitedirectory/download.htm

You will need to

1. Change Paths and file names for your PTviewer JAR, .JPG,  .MOV and Flash .SWF's. 

2. The .JS files are located in your root directory on the Server and are hard code pathed e.g  http://www.360Texas.com/embedxxx.js

*********** ===========JAVA PTVIEWER CODE======= ****************

----------create embedjava.js--------
document.write("<NOSCRIPT>")

window.onload = function() {
 document.body.innerHTML = document.body.innerHTML.replace(/\<noscript\>/gi,"")
}
---------- save as embedjava.js -----------

---Body Java Applet Code ---

<!--[if gte IE 6]><SCRIPT language="javascript" src="http://www.360texas.com/embedjava.js"><![endif]--></SCRIPT>
<APPLET archive = "ptviewer27.jar" code = "ptviewer.class" width = 900 height = 540 codebase="../../../../" >

 <PARAM name = wait value = "../../../../loading.jpg">

 <param name="cursor" value="MOVE">
 
 <PARAM name = panmin value = -180>
 <PARAM name = panmax value = 180>
 <PARAM name = pan value = 0>

 <PARAM name = view_x value = 0>
 <PARAM name = view_y value = 0>
 <PARAM name = view_width value = 900>
 <PARAM name = view_height value = 540>

 <PARAM name = tiltmin value = -90>
 <PARAM name = tiltmax value = 90>
 <PARAM name = tilt value = 0>

 <PARAM name = fovmin value = 75>
 <PARAM name = fov value = 90>
 <PARAM name = fovmax value = 100>
 
 <PARAM name = "autoTime" value = 120>
 <PARAM name = "auto" value = 0.1>

 <PARAM name = bar_x value = 320>
 <PARAM name = bar_y value = 300>
 <PARAM name = bar_width value = 250>
 <PARAM name = bar_height value = 5>
 <PARAM name = barcolor value = 3c8dbd>

 <PARAM name = quality value = 4>

 <PARAM name = frame value = "../../../../bar360.gif">
 <PARAM name = bgcolor value = ffffff>
 <PARAM name = shotspot0 value = " x822 y504 a836 b518 u'ptviewer:startAutoPan(-.1,0,1.0,120)' "> 
 <PARAM name = shotspot1 value = " x835 y504 a849 b518 u'ptviewer:startAutoPan(.1,0,1.0,120)' ">
 <PARAM name = shotspot2 value = " x864 y504 a878 b518 u'ptviewer:startAutoPan(0,0,0.99)' ">
 <PARAM name = shotspot3 value = " x877 y504 a891 b518 u'ptviewer:startAutoPan(0,0,1.01)' ">

 <PARAM name="file" value="16giftshop.jpg">

</Applet>
<!--[if gte IE 6]></NOSCRIPT><![e

-------------
/s/
Dave
Forum Moderator for
EasyPano - Panoweaver
Pano2VR


Visit 360texas.com

Hi Spinem,

If you are using a PC  XP and IE6 did you update your computer with the MS April 11 Patch ?

Dave

Dave,

Whilst testing your suggested version of the QTVR fix it has come to my attention that it causes Firefox not to display the Quicktime movie.

Have you tested this and the other scripts you are suggesting across each browser platform?

Example here

Regards, Smooth

Hmmm I am using IE6 modified Apr 11 version.  Maybe Firefox will need an update fix. I am confident that the Mozilla folks are aware.  I just checked with FF 1.07  and current 1.5.02  and both returned your page with a BIG Q.   Apparantly FF does not YET know how to deal with external .js or Active X issues.

Dave

The "ActiveX" issue this fix is for, is NOT an issue with Firefox or Opera and thus doesn't need the .js file. Both Firefox and Opera do understand how to interpret normal external .js files.

The patent issue over browser plug-ins was against Microsoft only and thus only effects Microsoft products.

I doubt Firefox or Opera need to update anything related to this. The script just needs improving to handle all browsers.

I think these bugs will be ironed out as the big boys write the answers needed once the dust settles. We'll see.....

Regards, Smooth

I too tried the FlashFix.  It works very well with IE6.  So nothing is wrong with the FlashFix or IE6 with the April 11 patch.

What does that say about Firefox?

By the way.  The Dust has Settled.

Adobe Macromedia Active Content Update Article 31March 2006

http://www.macromedia.com/devnet/activecontent/articles/devletter.html

Microsoft MS06-013 Cumulative (912812) April 11, 2006

http://www.microsoft.com/technet/security/Bulletin/MS06-013.mspx

Activating ActiveX Controls (applet, embed or Object elements) Shows scripting code.

http://msdn.microsoft.com/library/default.asp?url=/workshop/author/dhtml/overview/activating_activex.asp

It might be interesting to see similar reference pages for Mozilla effort.

Dave

Sorry Dave, I don't agree. The dust has not settled. Fact is, pre the "forced" changes made by Microsoft. The "old" method worked correctly on all browsers. Now, the "old" method works on all browsers "except" Internet Explorer. This is to say if you change nothing, Firefox and Opera work with active content as expected.

Now "if" we implement the scripts you have suggested it fixes the issue with Internet Explorer and stuffs up Firefox and Opera.

Now I'm all for only one browser and one standard but! You cannot blame Mozilla or Opera for Microsoft's change because they didn't pay up for using a technology that wasn't theirs to use.

What is required is a <javascript> that phases the browser and implements the correct command to the viewer using whatever browser they choose.

This I believe will be available once the dust has settled and people are confident on the new standard (without worry of another change). Clicking the "Activate Button" is better then blank white boxes in the browsers that still work properly, just because we use a script to make Internet Explorer work only.

Regards, Smooth 

While maybe not the most definitive source on browser statistics, IE6 and a few other browsers do appear to on a minor downward slide.  IE7 jumped from .2 to .6 ths of a percent since the beginning of 2006.

http://www.w3schools.com/browsers/browsers_stats.asp

2006	IE7	IE6	IE5	Ffox	Moz	N	O
March	0.6%	58.8%	5.3%	24.5%	2.4%	0.5%	1.5%
February	0.5%	59.5%	5.7%	25.1%	2.9%	0.4%	1.5%
January	0.2%	60.3%	5.5%	25.0%	3.1%	0.5%	1.6%

The folks over at Bugzilla are watching Active X.  18 as of 30April2006.  18 notices are not so many and most date back to 2002 through only 1 or 2 in January 2006.  I don't think any are the affect of the recent April 11 event.

https://bugzilla.mozilla.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=%22Active+X%22

++ MS 11 April release +other Mozilla issues are contributing to the non operability of Flash.

http://forums.mozillazine.org/viewtopic.php?p=2215867&highlight=912812#2215867