> Miguel wrote:
>> The clipboard is not accessible to an untrusted applet ... access to t=
>> clipboard was deemed a security problem.
> Understood. Still, it works great with the applet in a test I just
> did, and I for one am definitely looking forward to using this. At
> least we need to make it *potentially* available at this point.
I fear that this is starting to move onto shaky ground.
> that I want to recommend hand-editing the java.policy file, still,
> since it CAN work, let's make it available.
The policy file does not work for the MSFT 1.1 JVM.
Recall that I have agreed to support the 1.1 JVM through 2006.
> Many users are instructors
> who would be happy to enable this on their own machines, though not
> for their general users.
Then those people should use the signed applet.
> If there are ways of implementing it so that
> it sends a message to the user when they attempt to use it but have
> not allowed the permissions necessary, that would be ideal.
Theoretically, one should be able to catch security exceptions and handle=
However, there is a pretty good chance that this would not work on 1.1 JV=
In addition, there is the problem of which mechanism to use to warn the
user. The viewer engine does not make any assumptions about a windowing
package, so it cannot put up a dialog box. So, we would have to add onto
the JmolStatusListener ... a mechanism that already needs work.