downloaded&installed today and its build 33. Build 28 would be pretty strange since it had some issues with draggable applets which is more or less together with the new plugin the main feature regarding desktop java.

> 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.

> 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:

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:

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.

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..

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, ...

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.

Quote

...and the new plugin is enabled by default on all browsers that you probably care..

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...

java-gaming.org is not responsible for the content posted by its members, including references to external websites,
and other references that may or may not have a relation with our primarily
gaming and game production oriented community.
inquiries and complaints can be sent via email to the info‑account of the
company managing the website of java‑gaming.org