>> WOLips 3.5 is not considered a stable release. I use it all the time, but it has serious performance issues, especially in the Cocoa build -- these are Eclipse problems, not WOLips problems. We are mostly at the mercy of the Eclipse team to fix these problems before we declare a WOLips 3.5 release build. Maybe 3.5.2 will have the performance fixes necessary to move.
>>
>> ms
> This is no surprise, but when I have submitted bugs against eclipse, they seem to opine that WOLips may be at fault. They are not especially grumpy about it, but I suspect they point the finger at us as often as we point it at them.
This is generally more of an issue for JDT-related items than SWT-related items, but such is the nature of the beast. We're both huge and complicated and it's sometimes hard to actually create an isolated test case of the problem. For SWT, I generally have much more success because it's rare that it's tied up in something we do. While I do have an open JDT performance issue (which may or may not be us/them -- i really don't know other than that it worked fine in 3.4), most of the problems holding up 3.4 are SWT, provably.
> Is there a tag or a search you use to find relevant WOLips-related bugs in bugs.eclispe.org? I can do a search for "WOLips" and I see 9 bugs (below), and then there are the 260 open bugs aginst 'Mac OS X - Cocoa'. But I suspect there are some bugs that do not have "WOLips" in the strings but which are (in our opinion) blocking us. Do we have a way to track those bugs?
>
> There are several ways to mark bugs in bugzilla as being part of some "group" or "category" and I have looked for a "WOLips" thing in those markers but do not see any. Perhaps a "[WOLips]" in the bug title would be a way to start? Or something in the whiteboard? The list of keywords is not huge, so I suspect that using a keyword would be discouraged.
Not sure eclipse people would appreciate us tagging bugs with our own flags ... I don't have a search that I do specifically for WOLips, I just have a saved search of "mine":
The biggest problem right now is probably:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=282229
I think there are fixes for most of the other terrible performance problems, though I don't know if they'll make it in 3.5.2 or 3.6.
ms
This archive was generated by hypermail 2.0.0 : Tue Jan 05 2010 - 11:49:52 EST
