Re: [Jmol-users] Tiger and jmol

[Philip Bays]

On May 7, 2005, at 2:47 AM, Bob Hanson wrote: This is SUCH disappointing news. Obviously not a problem unique to Jmol. How could they POSSIBLY not have noticed this in the development of this product? I think there are a couple of issues here.� With the Mozilla browsers, as I understand it, there is the main tree and the branches.� The tree still relies on java 1.3.� �Until that changes, the branches (FireFox et. a.l) will not change.� Now that fact that a single programmer can write a small open source plugin that corrects the issue says to me that we need to be harassing Mozilla development.� However, clearly Apple broke something with Tiger that makes the plug-in need to be revised. On the Safari issue, they have clearly broken something along the way -- I think about 10.3.8.� I am not enough of a programmer to know what they did; I can only see the results.� My observation is that a page will work fine using either 10.3.9 or 10.4, as long as it is the first instance of the applet loaded. And the issue does not seem to be there in our campus version of 10.3.5.� This seems to me to be a different problem, though I will rely on Tim to be more specific. Perhaps if ALL of us send a bug report to Apple we can get some action. We have the testable, reproducible pages, I think. What would be the simplest test sequence to offer them that they could see the problem in seconds? I agree here.� I think it would be best if we had a simple page -- perhaps some iteration of Tim's jmolaccess test.� �I also think it would be useful if we could trace OS's to identify when this issue arose in Safari -- though that should be Apple's job. On the issue of uniqueness:� I have not seen similar complaints elsewhere, but I will do some searching of the apple discussions.� But, a question for us,� is there something unique about Jmol that is not common to other applets? What is the method of filing these reports? You need to be a developer -- which you can self declare -- and subscribe to the developer list.� I have done that some time ago.� �But I think we need to agree on what we are going to say before we file the bug.� �I think Tim has already done. Seriously, maybe if we ALL did this, someone might take notice. Bob Hanson J. Philip Bays Professor of Chemistry Science Hall 158 Saint Mary's College Notre Dame� IN� 46556 (574) 284-4663