Well, to be perfectly honest its also not the game-performance advantage that drives me so enthusiastic about this feature.Basically I want to see big swing apps like JBuilder or Netbeans even more fly on Linux but with the nice effect that my Java2D games also perform better...

I was a bit sad when I saw how the OGL pipeline performed in 1.5, STR made it much better but there are areas where X11 is still the clear winner withought any technical reason (since x11 has context-switch+protocoll overhead).

However one bug ist still open and is even worse with STR: Every java-application causes 1500 context-switches/s, and since the java2d-team sis not know how to fix it they marked it as "not a bug" and closed it.If it can't be solved why does my system with a lot of native GUI apps can have only 500CS/s, whereas 5 running java apps cause 6-7000 (!!) context switches. This also really affects scheduler/system performance!However, nothing is perfect :-(

Sun already put support for framebuffer-objects as a RFE in their bug-database and since nvidia will provide support for EXT_Framebuffer even in their next drivers it would be great to see Framebuffer-backed VIs already in mustang, not in dolphin...

maybe you are right but maybe not, because if canvas should be marked as deprecated why there are thousands of experienced programmers which think that it is the best solution?

Because it takes a long time till experienced programmers come to the conclusion that the way they did it till they started isn't the best anymore.Have a look at yourself ;-)

Quote

and if swing everything can do what awt does, why is it not thread-safe?

Well, AWT isn't thread-safe either. It was designed to be thread-safe but it soon turned out that this was a BAD desision and some hacks to allow AWT stuff to be used from many threads was even removed in 1.2+!So in most situations it will work but it is really not recommended. In Swing the removed thread-safty from the beginning to avaoid the mistakes made with AWT.Multi-Threaded Graphics is never a good idea, at least on all underlaying graphic subsystems AWT is supported on.Rendering is always done only with a single thread down to the hardware!

Quote

if you already implemented a canvas-like JPanel with a BufferStrategy and a Painting-Thread, i would be happy if you can give me some tips.

No I haven't. But if you really need to draw from multiple threads maybe your design is broken anyway?

just make me wonder too, same for pixelgrabber which is unuseable when using the OGL-Pipeline. why isn't it simply emulated by using bufferedimages in background...Its so slow that some 1.1 software becoms even unuseable in todays modern hardware....

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