This leads to related questions.
> In the 'Jena3D Viewer' you can request specifically Jmol or JSmol.
> And this decision is also inherited by subsequent viewer openings from
> the current viewer or from a QuickSearch result from within the viewer.
>
> Q: How should this be handled regarding the fallback setting?
> (It would be quite tricky to discriminate between the different cases.)
>
Generally I cache that setting and then, when I construct a new page, I add
*?_USE=xxxx* to the URL. This overrides *Info.use* and forces Java or
HTML5. There are four settings:
*_USE=HTML5_USE=SIGNED*_USE=JAVA
_USE=WEBGL
I recommend the first two. "SIGNED" is really "Trusted-signed" whereas
"JAVA" is sandboxed -- what we used to call "unsigned". (All applets must
be signed now, even the sandboxed ones.)
Even if you are just working from your own site, the signed applet allows
easy download of files and images to the user's computer, including PDF.
WEBGL is not being developed actively; it's a compromise that doesn't work
on iOS and doesn't have several important features (like labels).
> Q: Is there a situation where "HTML5 JAVA" would lead to using Java
> instead of HTML5 automatically?
>
>
Not really. Old computers that probably won't run the Java either, anyway.
> Regards,
> Rolf
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
