Re: [ros-kernel] native vs. Win32 - again

[Yuri P. <pro...@fr...>]

On 31 May 2002 23:27:55 +0200, Casper Hornstrup wrote:

>l r, 2002-06-01 kl. 00:16 skrev David Welch:
>> On Fri, May 31, 2002 at 02:49:05PM +0200, Casper Hornstrup wrote:
>> > Maybe you don't like it because you still see user32.dll and gdi32.dll
>> > as Win32 components. Well that all changed when we decided to make them
>> > native. Even such a small change can make a big difference to how you
>> > percieve things. Now, these components have been adopted as _the_
>> > standard user mode interface to the window manager and GDI and they are
>> > no more part of the Win32 subsystem than any other subsystem. They are
>> > subsystem support code. Using these DLLs in subsystems does not mean
>> > that the subsystems cannot have their own look and feel. It gives you
>> > the _option_ of not having to duplicate the user32.dll for each and
>> > every subsystem and you can then focus on getting your subsystem to do
>> > what it is supposed to do; run applications that expect certain APIs.
>> > You also have the option of reimplementing user32.dll if you feel
>> > strongly about your applications look and feel differently from others
>> > on the desktop.
>> > 
>> I did not realise we had decided this! In my view, user32, gdi32 and 
>> win32k.sys should implement the user and gdi parts of the Win32 API and 
>> nothing else. Of course other subsystems can use these to emulate whatever 
>> APIs they want just as they can on Windows NT itself.
>
>Yes, the graphics APIs of other subsystems can be written as thin
>wrappers to gdi32.dll and user32.dll. Since these modules perform most
>of the win32k.sys interfacing, the wrappers should be small compared to
>the subsystems using win32k.sys directly.
Well. Now I again don't understand goal of subsystems. Why then don't use ODIN approach? Just make wrappers from pm* to *32 dlls? And how win32 apps will interact 
with gdi32? Or all win32 will be moved to native part?