It was released on a Thursday 
As for Exceptions and missing Splash images causing issues with WebStart - I would consider that very low priority - I mean, come onā¦ fix YOUR bugs first.
The āWorks the second timeā thing sounds like a much bigger dealā¦ does anyone have a bug # for that one?
Hehe, not my bugs, I noticed it on somebodyelses JWS app.
I havenāt deployed anything in JWS for ages - Iām the innocent end user
Seems the priority is low, so I donāt see that being fixed anytime soon.
Itās not really that, itās just that I literally donāt know how to improve this. As you can see from the bug report Iād tried a bunch of different approaches, without much success. If you have any ideas or know any d3d gurus, be my guest, the code was ported to jdk7 which is open sourced.
Dmitri
Just disable the pipeline for applets and let the user decide if he/she wants to use it in combination with the new plugin. If not that, disable it for the old plugin at least. The way it is now, i can disable it for the new plugin, but thereās no way to do the same for the old pluginā¦which is the plugin running on the majority of systems ATM and especially on those that suffer from this problem: The some years old AGP based machines with something like a GeForce 5x00, 6x00 or 7x00 in it.
btw, has anyone seen the new Nimbus look and feelās class names? The look and feel itself is very nice, a real step up from the horrible LAFs that have been the default for years. But the class names, come on:
com.sun.java.swing.plaf.nimbus.InternalFrameInternalFrameTitlePaneInternalFrameTitlePaneCloseButtonWindowNotFocusedState
Why do you care? These were automatically generated by the nimbus design tool, of course.
Dmitri
How about you disable it for your applets? Itās possible with the new plugin (since it can launch a new vm if you speficy a flag or property which is different from already running vms). You will only get the new plugin with 6u10 where the new pipeline is, and the new plugin is enabled by default on all browsers that you probably careā¦
Dmitri
Well, iāve already written that i can disable it myself with the new plugin and most likely, i have to. But i canāt do that for the old plugin and that just plain sucks.
No. Iāve some talkback function (can be disabled by the user of course) in my stuff and people have current VMs but they have old browsers and often enough hardware from the stone age. The new pipeline disabled by default for the old pluginā¦thatās all i want for nowā¦you are not promoting applets by killing performance for a lot of people with this new pipeline. Anyway, we already had this discussion IIRCā¦