|
Thanks, Biswajit.
The
client's browser is always under the client's control, that is the web model we
have to operate under. If you try and take the control away from the user
(popup windows, etc.) users are almost always end up dissatisfied with the
experience. The best you can do for this sort of thing is probably using some funky
page onUnload() actions... which are unreliable at best.
Another problem is that trying to get something this complex to
work on Exploder, Nutscrape, AmericaOffLine, etc. in all the myriad versions
will take you several weeks.
Why
not simply give the client the "cancel" option? They will know best
if they want to wait. Users are getting better and better about using the
web. Or, better yet, forget the long-loading applet altogether, just
send them straight to the _javascript_ menu, and THEN give them the link to
get the Applet. I can bet $100 no one will ever click that
link...
A
friend of mine just spent 2 days re-writing the Calendar class functions for his
100-line applet because they do not work the same on the M$FT JVM and Sun
JDK 1.3 JVM. You ended up with 42 day months in one case, and for the
other, the published API methods just did not exist. And no, I don't
need any comments right now from the rest of the list on how the applets are
just so -ing wonderful. Let's not open that can of worms again. If you like
them, then YOU use them. :-> As for my humble opinion, if you can do
without an applet, then you just saved yourself weeks of
grief.
Just
my additional 0.002 cents
Greg
____________________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm Be respectful! Clean up your posts before replying ____________________________________________________ |
