Inside SWT

Sunday, July 23, 2006

Closing 37683

We closed 37683. At times, this bug resembled a blog rather than a bug report. It was used by some to spread FUDge about the toolkit and that's bad. Fortunately, I don't have a sweet tooth.

Let's be clear. Some people were seeing problems and we worked hard to isolate them (the problems - not the people). When there was a bug we could recreate, we opened a new bug report and fixed it. We wrote example code that created the same window using GTK calls in C, then GTK calls in Java and finally in pure SWT code to see whether there were fundamental problems in the event loop or elsewhere in the toolkit. There weren't.

Some of the focus was on the speed of popup menus. Menus come up fast in SWT, but application programs like Eclipse do lots of domain specific work to enable or disable items and in some cases, build a new menu each time a menu is requested. If this work involves file i/o and threads, then performance numbers are variable.

Was this bug worth it? I'd have to say "yes". We found and fixed real problems and that makes me happy.

Steve

2 Comments:

  • Thanks Steve... And thanks to the whole SWT team. SWT on Linux has come a long way since 2002 when I first started using it.

    I still think there are lots of directions SWT can go in, and I will continue to post comments (bugs, etc...). I hope no-one sees these as put downs or complaints. I truly believe that SWT can be the universal widget set!

    By Blogger Bull, at 12:31 PM  

  • Keep that great feedback coming! We're having a lot of fun building and maintaining the toolkit.

    Steve

    By Blogger Steve, at 9:40 AM  

Post a Comment

<< Home