Re: DIB clarification

2010-08-30 Thread Ken Thomases
On Aug 29, 2010, at 8:49 PM, Jeff Cook wrote: > To clarify, it's not about having secret DIB engine code, it's about > saying "I guess we just won't find time to provide useful feedback > until some company sponsors it...", as I saw several times during the > old threads. What Jeremy neglected to

Re: DIB clarification

2010-08-30 Thread Roderick Colenbrander
On Sun, Aug 29, 2010 at 2:18 PM, Jeff Cook wrote: > I hate to stir the pot, especially as an unknown in the community, but > I've spent the last few hours reading WINE's history regarding DIB > engines and it is pretty distressing. > > I have seen expressions of frustration from many regarding the

Re: DIB clarification

2010-08-30 Thread James Mckenzie
Michael Stefaniuc wrote: > >Now that "that waive with $$$" isn't very likely as the cost/benefit >ratio isn't very good. More likely is that Codeweavers will start >working on a Quartz driver and that work will make the DIB engine >"cheaper" to implement. Again, this is my *personal* opinion. > I

Re: DIB clarification

2010-08-30 Thread Michael Stefaniuc
Jeff Cook wrote: > On Sun, Aug 29, 2010 at 7:12 PM, Jeremy White wrote: >>> This could also help. If I recall correctly, Jeremy White mentioned >>> at Wineconf 2008 that this was a major reason they haven't invested >>> serious energy into one themselves: they had a hard time finding an >>> appl

Re: DIB clarification

2010-08-29 Thread Austin English
On Sun, Aug 29, 2010 at 7:00 PM, James McKenzie wrote: > One additional note:  We should, as a project, not accept 'broken' code.  I > work with a real-time project and get paid for this that soon will have this > policy in effect.  No broken code, it is way to hard to go back and fix it > later.

Re: DIB clarification

2010-08-29 Thread Tom Wickline
On Mon, Aug 30, 2010 at 8:00 AM, James McKenzie wrote: > > Also, Max's code has shown up in another 'for pay' project and where > implementation was done, works. Where implementation is not complete, it is > seriously broken. The problem is where it works and does not work is not > cleanly defin

Re: DIB clarification

2010-08-29 Thread Jeff Cook
On Sun, Aug 29, 2010 at 7:12 PM, Jeremy White wrote: >> This could also help.  If I recall correctly, Jeremy White mentioned >> at Wineconf 2008 that this was a major reason they haven't invested >> serious energy into one themselves:  they had a hard time finding an >> application that they cared

Re: DIB clarification

2010-08-29 Thread Jeremy White
> This could also help. If I recall correctly, Jeremy White mentioned > at Wineconf 2008 that this was a major reason they haven't invested > serious energy into one themselves: they had a hard time finding an > application that they cared about that benefited significantly from a > DIB engine.

Re: DIB clarification

2010-08-29 Thread James McKenzie
Juan Lang wrote: Hi Jeff, this has in fact come up before, and been addressed. The main problem with the current attempt, as far as I know, is that the risk of regressions is so high that only very high quality changes stand any chance of getting accepted. In the case of a DIB engine, the atte

Re: DIB clarification

2010-08-29 Thread Juan Lang
Hi Jeff, this has in fact come up before, and been addressed. The main problem with the current attempt, as far as I know, is that the risk of regressions is so high that only very high quality changes stand any chance of getting accepted. In the case of a DIB engine, the attempts have usually r

Re: DIB clarification

2010-08-29 Thread Jesse Allen
On Sun, Aug 29, 2010 at 6:18 AM, Jeff Cook wrote: > Alexandre is right that the > architecture is a lot of work, but I am not asking for him to write > out a complete spec, and I don't think the community is, either; the > main thing, as far as I can tell, is that the interaction and feedback > on

DIB clarification

2010-08-29 Thread Jeff Cook
I hate to stir the pot, especially as an unknown in the community, but I've spent the last few hours reading WINE's history regarding DIB engines and it is pretty distressing. I have seen expressions of frustration from many regarding the handling of the mostly-functional DIB engine that Massimo w

Re: Clarification

2006-09-01 Thread Juan Lang
Thanks Tom! I was indeed confused. I was wondering if it were some literary reference I was missing, like Tom Riddle in the Harry Potter books or something. /me stops scratching his head. --Juan __ Do You Yahoo!? Tired of spam? Yahoo! Mail has th

Clarification

2006-09-01 Thread Tom Booker
Hi everyone, I feel like I owe some of you some clarification with all of the names I have slung around here in the past as my own..I started contributing as Dustin Navea, then it switched to Dustin Booker, then to Tom Spear (aka Dustin Booker Dustin Navea), and finally to Tom Booker.  It's

Re: clarification regarding msxml

2005-06-22 Thread Mike McCormack
Vijay Kiran Kamuju wrote: Can you please clarify what msxml.idl is implementing It's aimed at implementing msxml3.dll, however the declarations should be independent of which version you're using. If you wish to extend the definitions, you should make sure to consult the Microsoft Windows

clarification regarding msxml

2005-06-22 Thread Vijay Kiran Kamuju
Hi, Can you please clarify what msxml.idl is implementing msxml.dll (Version 1.0) comes with IE4.0 or msxml.dll (Version 2.0) or msxml2.dll (Version 2.5/2.6) or msxml3.dll (Version 3.0) Thanks, Vijay