Comments on: JRuby can save Swing - Follow up http://www.rawblock.com/2007/03/09/jruby-can-save-swing-follow-up/ Random braindumps vaguely related to coding Tue, 06 Jan 2009 08:39:20 +0000 http://wordpress.org/?v=2.6.3 By: Zero Schezard http://www.rawblock.com/2007/03/09/jruby-can-save-swing-follow-up/#comment-109 Zero Schezard Tue, 27 Nov 2007 19:42:00 +0000 http://www.rawblock.com/2007/03/09/jruby-can-save-swing-follow-up/#comment-109 I propose you a test-case: Make a Hello World in Java, with swing. Now, make a Hello World in Ruby, with QT, or in Ruby, with GTK+ or any other framework. Now, answer me please: WHY your "Hello World" in Swing is SLOWER to open AND SLOWER to resize? If this is a proof, well, I don't really now what is... I propose you a test-case: Make a Hello World in Java, with swing. Now, make a Hello World in Ruby, with QT, or in Ruby, with GTK+ or any other framework. Now, answer me please: WHY your “Hello World” in Swing is SLOWER to open AND SLOWER to resize? If this is a proof, well, I don’t really now what is…

]]> By: something fast http://www.rawblock.com/2007/03/09/jruby-can-save-swing-follow-up/#comment-22 something fast Sat, 17 Mar 2007 12:11:00 +0000 http://www.rawblock.com/2007/03/09/jruby-can-save-swing-follow-up/#comment-22 There are some basic design flaws in Swing.<br/><br/>If you stack 100 windows with only the top 5 or 6 of them visible and then drag another window over the stack, you will see an immense slow down in drag speed. I said 100 windows because it makes the effect obvious. Fewer stacked windows and it just shows up to the user as strange and quirky "Java behavior".<br/><br/>It looks like Swing does not keep track (or test) what is visible and what is not.<br/><br/>I recently re-tested this issue and found it to be still there in the latest Java 6.<br/><br/>What is also interesting for Swing is something like JAXX, especially if JAXX were incorporated into NetBeans.<br/><br/>Anyhow, I'm hoping Sun's recent refocus on Swing and usability will pay off in Java 7. There are some basic design flaws in Swing.

If you stack 100 windows with only the top 5 or 6 of them visible and then drag another window over the stack, you will see an immense slow down in drag speed. I said 100 windows because it makes the effect obvious. Fewer stacked windows and it just shows up to the user as strange and quirky “Java behavior”.

It looks like Swing does not keep track (or test) what is visible and what is not.

I recently re-tested this issue and found it to be still there in the latest Java 6.

What is also interesting for Swing is something like JAXX, especially if JAXX were incorporated into NetBeans.

Anyhow, I’m hoping Sun’s recent refocus on Swing and usability will pay off in Java 7.

]]>