[ros-kernel] Re: Header Files and GUI apps

[Eric K. <ek...@rz...>]

Steven Edwards <Ste...@kn...> wrote:


> Thanks Eric, it does help to answer some of the questions I have. I also
was
> able to get the programs to compile without a console. It ended up being a
> typo in my makefile.
>
> Ok I'm still really new at this so feel free to tell me to shut up and
guide
> me to what book i need to read. I've been attempting to build the comctrl
> lib that you wrote for wine under mingw but have a few questions before I
> waste alot of time on it.
>
> 1. Wineserver emulates WinNT by default right? I understand the whole
> Wraping X11->GDI and POSIX->Win32. But how generic is this? Should porting
> these higher level libs be very hard?
>
Not exactly. Wine can emulate various windows versions (see '--winver'
parameter). Wineserver is a single server instance that manages kernel
objects and ipc, much like ntoskrnl.
AFAICS, it should be pretty easy to port a high level dll. But stay away
from the low level dll's, like ntdll, kernel32, advapi32, gdi32 and user32.
They include the ugly X11<->GDI/USER and POSIX<->Win32  stuff which is *NOT*
portable!!!! Some parts of ole/com are not portable too because they (will)
use the wineserver.

 > 2. There is some redundant declarations in comctrl.h most of the redunacy
> occurs in include/messages.h and defines.h. Also some declarations lacking
> in windows.h that are wines winuser.h. How should this be aranged?
>
The common controls should only use 'windows.h', 'commctrl.h' and perhaps
dll internal header files. Declarations that are missing in the reactos
header files should be added to the reactos sdk header files. Unfortunately
we are still using the old mingw header files. Extensive rework is needed to
update the header file structure.

> 3. From what I have already seen the UNICODE stuff looks like it will be
> hard to fix. So the finaly queston is once again, am I going to be wasint
my
> time trying to port this?
No, it is not that hard! Last week I had a long discussion with Guy
Albertelli about missing and undocumented features in the common controls.
We agreed on a method to implement the Unicode messages in ListView and
TreeView. But this will take a few weeks since we are both busy with other
tasks. Another problem is that someone (me!?) will have to check which
controls are up-to-date and what is missing (e.g. balloon tooltips).

At present it is a waste of time to port comctl32 or shell32 to reactos. :-(

- Eric

====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================