Fwd: Re: [ros-kernel] Re: WINE porting templates

2003-10-18 Thread Steven Edwards
So are you interested in helping to implement this? The WINE project has started a uxtheme.dll It would be nice if we could agree on a common theme system for both projects. Thanks Steven Note: forwarded message attached. __ Do you Yahoo!? The New Yahoo!

Re: [ros-kernel] Re: WINE porting templates

2003-10-16 Thread Steven Edwards
--- Dimitrie O. Paun [EMAIL PROTECTED] wrote: For my info, what's the problem with the headers? What headers are you using? If not Wine's, why not? It seems we have better headers than then w32api guys... I dont know if better is the right word. WINE has more compleate headers but they are not

Re: [ros-kernel] Re: WINE porting templates

2003-10-16 Thread Steven Edwards
--- Dmitry Timoshkov [EMAIL PROTECTED] wrote: But for simple things which use pure Win32 APIs like USER controls, message boxes you have to be able to share code with Wine without any significant effort. By porting that code to reactos you gain nothing except bugs. Have a look at

Re: [ros-kernel] Re: WINE porting templates

2003-10-16 Thread Dimitrie O. Paun
On Thu, 16 Oct 2003, Steven Edwards wrote: I dont know if better is the right word. WINE has more compleate headers but they are not the most correct. The w32api people are very anal (No Offence Danny) about getting changes in to the package. I have almost never found where something is wrong

Re: [ros-kernel] Re: WINE porting templates

2003-10-16 Thread Dimitrie O. Paun
On Thu, 16 Oct 2003, Steven Edwards wrote: I have rebuilt a few engines in my day and this has been like trying to take parts from a BMW and use them on a Honda. It just doesnt work most of the time. Dont get me wrong it should just work. All of the interfaces should be the same but

Re: [ros-kernel] Re: WINE porting templates

2003-10-15 Thread Eric Kohl
Jason Filby [EMAIL PROTECTED] wrote: User32 and gdi32 are likely to be a problem as the bulk of our implementation is in kernel mode win32k.sys. More problems will be caused by advapi32 and rpcrt4 because ReactOS will use LPC instead of Unix-Sockets for local IPC. Regards Eric

Re: [ros-kernel] Re: WINE porting templates

2003-10-15 Thread Jason Filby
Hi Dimitrie User32 and gdi32 are likely to be a problem as the bulk of our implementation is in kernel mode win32k.sys. Regards Jason --- Dimitrie O. Paun [EMAIL PROTECTED] wrote: On October 14, 2003 03:11 pm, Jason Filby wrote: I agree that forking should be avoided at all costs. Of

Re: [ros-kernel] Re: WINE porting templates

2003-10-15 Thread Jason Filby
Hi Vizzini This sounds good to me. As you said, it seems like headers are the big blocker here. Regards Jason --- Vizzini [EMAIL PROTECTED] wrote: Steven and I spoke about this the other day, and I am in agreement with you, Dimitrie. I don't want to fork. We can use CVS to manage the wine

Re: [ros-kernel] Re: WINE porting templates

2003-10-15 Thread Steven Edwards
Hello All, Jason is right I think. I spoke with Alexandre the other night about implementing a Win32k.sys driver for WINE so we could use GDI32/User32 and it might be do-able it wont be somthing that is possible for at least another year at the rate we are sharing code. Wines user32 depends on a