Re: Strange applet behaviour on Windows XP
Qu0ll wrote:
[quoted text clipped - 31 lines]
'yes' to all three of the above. But I am not sure
what you are refering to.)
Actually, I have found Web Start to be quite problematic as well.
"Actually, I have found applets to be quite problematic as well"
..My pet
peeve is when you try to launch an application and after a few minutes a
small window pops up (usually behind the browser where it is not visible)
saying that the application failed to launch.
"My pet peeve is when ... small message appears in the browser
status bar saying 'not inited'. That is *assuming* the browser
status bar is configured to show at that moment.."
..It gives no details as to why
and no remedial action can be taken.
'ditto' (change JWS for applet)
..This has happened a number of times
for me as I have tried to launch apps on various sites (but don't ask me to
list them just now).
'ditto' (change JWS for applet)
Now your excuses are becoming pathetic.
Your statements apply to both, probably even more so
to applets than JWS.
There are remedies for both, mostly involved around, and
in control of, the deployer. That is *you*. If you deploy a
broken-ass applet, JWS project, or 'plain jain' application,
stuff will break, and in ways not immediately obvious
to the user.
*We* as developers can pop consoles for applets or JWS
applications and send the trace level up to 5 to find out
what is happening, if need be. During development is the
time that should be done, to reduce the possibility of a
'no information crash and burn' once the app. goes public.
If you want to pursue applets, fair enough. Just do
not think that such pathetically silly comments will
go unchallenged.
--
Andrew Thompson
http://www.athompson.info/andrew/
Message posted via JavaKB.com
http://www.javakb.com/Uwe/Forums.aspx/java-general/200711/1