Inside SWT

Monday, December 18, 2006

I am Eclipse

The other day, I found out I was Eclipse. Apparently, Eclipse is a grizzled old platform hacker, whose every second word is f*ck ...

Seriously, I can see both sides of the "Eclipse is You" thing. Sometimes, people just complain and don't help (sometimes they are paid to do this but that's another story). Those must be the people Ward is talking about. Other people submit really good patches and we run out of time to process them. Often in SWT land, patches contain the essence of a fix or feature, but the real implementation is much more work. One thing that people don't seem to understand is that once an API is in, it can never come out. It must be supported forever. That's a long time (and a lot of work).

Anyhow, please hang in there and ping those bug reports that contain patches.



  • That is what I meant by contributed by a member of the community and maintained by a committer... People forget about the maintenance. And I imagine SWT is especially bad since most people probably don't think about the cross platform issues.


    :) just kidding, i know there's not a lot you can do about this one.

    By Blogger Bull, at 10:44 PM  

  • You still being burned by this?

    By Blogger Steve, at 10:05 AM  

  • Geesh, I can never get any credit/blame -- I wrote that post, not Ward...

    By Blogger Bjorn Freeman-Benson, at 12:51 PM  

  • Steve:

    This SWT bug is stopping our release. I realize I am useless in your eyes since I have no fix for this and no time to delve into it. But could you please apply your large brain to solving this for us :-) Having championed RCP and SWT for the past few years I would like to be able to release our application!

    By Blogger Sally, at 9:53 PM  

  • Sally, there is no bug number in your post and nothing for me to look at.


    By Blogger Steve, at 1:24 PM  

  • My apologies Steve, I thought the link would go there.
    Bug # is 204163
    I had posted a comment on it and since then it has now been gated for 3.4 M7, which is very promising. My only other concern is that the original writeup was talking about handle leaks in editors, whereas I 'appear' to be seeing them in both CTabFolder and 'update ToolItems' (colours and images). Although I don't pretend to be an expert with Sleak.
    Anyway, it does appear to be being looked at now. Thanks.

    By Blogger Sally, at 9:06 PM  

  • I looked quickly at the bug. ToolItem creates (and later disposes) a disabled automatically behind the scenes to feed Windows.

    It doesn't look like a real leak to me ... but I could be wrong. We'll let Paul look into it.

    By Blogger Steve, at 9:15 PM  

  • That is much appreciated Steve. If I find anything more I'll let you know. Thanks for taking the time.

    By Blogger Sally, at 9:31 PM  

Post a Comment

<< Home