|
From: Casper H. <ch...@us...> - 2002-04-23 18:21:18
|
tir, 2002-04-23 kl. 19:28 skrev Mike Shepherd: > Yeah, I'd much rather duplicate what NT does but it just looked like > a much bigger job. Having looked at the code more extensively I can > see that there's more there than I had thought. Hopefully you > appreciate that as a newbie poster it's useful to hear why design > decisions made before my involvement were made! Yes, we should be writing more docs about such issues ;o) > > > > > > > Implementation ideas :- > > > > > > - Remove the current user32.dll code and associated code in > > > win32k.sys etc. and replace with the relevant code from > > > Wine. > > > > This is not just a copy/paste job, so why bother? Using WINE for > > something as low-level as the window manager puts restrictions on the > > design of the ReactOS window manager. If I had to choose, I would much > > rather spend the time needed for adapting the WINE code for > > ReactOS, on > > designing the window manager code properly - even if it takes longer. > > Sure we can learn from the WINE implementation, but using its > > design is > > IMO not worth it. > > Fair enough. I think the Wine USER code could be ported fairly quickly > but I do agree that an NT like implementation would be more efficient > and probably the longer term solution. I guess that some of the WINE code that use GDI APIs (but not WINE specific APIs) could be easily modified for ReactOS. > > > We can use WINE modules that only use the Win32 API without > > any need to > > make changes specific to ReactOS. If we can agree with the > > WINE project > > to use the same headers, ReactOS developers can develop on the shared > > modules with less of a risk of breaking something for the WINE > > developers (and vice-versa). > > Definitely. It does look like things like comctl32.dll could be > taken almost directly from Wine (assuming, as you say, uniform use > of header files). Yes, comctl32.dll is one of the many DLLs that can be written to exclusively use the Win32 API. |