[cw-discuss] Wineconf return

[Phil Stopford]

Jeremy White wrote:
> Hi Folks,
> 
> I thought I'd just drop a note to let you know that we've
> all just returned from our annual Wine technical conference,
> in lovely Reading, England, where we've been this past 4-5 days.
> If you're interested, there is a nice write up of it here:
>   http://www.winehq.org/?issue=320
> 
> Now we just need to shake the dust of, clear our inboxes,
> and we should be back to work on readying a new set of
> CrossOver betas (one for Linux and one for Mac).
> 
> Cheers,
> 
> Jeremy
> 

That 3x slower benchmark on OSX is a little worrying to read about.

More disconcerting for me is that 1.0 of Wine seems to be rushing 
towards us without a fix for the OpenGL-in-a-window bug (2398 on 
bugs.winehq.org). I assumed that bug was one of the blockers, but the 
conference report makes no mention of it being discussed which is 
disappointing. I have nudged Codeweavers about this before so Jeremy is 
probably shouting at his monitor, but I feel the point is worth raising 
again in a more public arena.

It would really be a big draw for application vendors to have this 
fixed. Weren't Softimage looking at Wine as a potential mechanism to 
bring XSI to OSX (scanning the wine-devel group on gmane)? That shopuld 
show what potential Wine has for big investment and how much there is to 
lose.

The impact of this bug has been huge to me. The last CXO release that 
wasn't affected was 3.0.1 - everything afterwards has been entirely 
broken due to this issue, or something very much like it. I wrote my 
doctoral thesis entirely using CXO 4.x, partly because I wanted to see 
how long it would take to break Wine (it never choked) and partly 
because Windows couldn't print the document to PDF without failing due 
to lack of memory, but CXO could. I couldn't get by without a dual boot, 
though, due to this issue - some of the apps needed OpenGL-in-a-window.

I'm currently back in Windows due to this bug, but am still paying CW in 
the hope that the cash will help get this issue squashed without threat 
of it resurfacing. Please tell me it's still on the 1.0 blocker list for 
Wine and that all concerned are at least aware of the problem, if not 
actively working on it for a (various) reason(s)

Phil.