> I don't get pissed off THAT easily. No, just concerned that you will > have a lot more email when people start getting the "big yellow screen" > on pages that used to work just fine. I haven't done enough with this to > care, personally. > > But you are putting up the yellow screen, then, right? > > Suggestion: > > 1. Only put up the yellow screen if the source is local-- file:/// not > http:// > > Developers will see it, but it won't break any web page.
I don't think that it is ever a good idea to work locally using file:/// It just causes problems because of applet security issues. If you are building for a web server then all development should be done against a web server. > 2. Make it friendlier: > > Developer alert! > > This applet does not include a progress bar. > If this page is intended for a web site, please include > the following between the <applet> and </applet> tags: > > <param name="ProgressBar" value="true"> > > Otherwise users will have no indication that the applet > is loading and may be confused or frustrated. > > (This message is appearing because the page is loading > from your local machine; it will not appear if the page > is loaded from a website using the http:// protocol.) > I thought that was about what it said. I will change the wording somewhat. > Can that be done? Yes, I will modify the wording. The better solution which will solve the majority of the problems is to provide the Jmol.js JavaScript library ... I'm working on it as a background task. Miguel ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Jmol-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-developers
