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

[Casper H. <ch...@us...>]

fre, 2002-05-31 kl. 18:50 skrev Yuri Prokushev:
> On Fri, 31 May 2002 07:28:16 +0200, Patrick Mauritz wrote:
> 
> >On Thu, May 30, 2002 at 11:44:20PM +0200, Aliberti Emanuele wrote:
> >> OS/2 has its own graphics and windowing API: why should it use Win32?
> >it should at least use win32 windows and messages - that way you can
> >run win32 and os/2 stuff on one desktop.
> >getting them on one desktop with two distinct "window lists" (or however they
> >are stored internally) you'll have a big time trying to keep them all
> >up-to-date...
> Well. Question is _why_ should it use win32? _Why_ not win32k? Of couse, os2ss (and any other ss) can (and must) use common window manager and messages. But 
> why make it depended on win32? I don't like this aproach. I consider usage of win32k graphics is ok, but usage of win32 graphics and highlevel objects is bad. I don't like 
> to see win32-looks windows on my desktop. I prefer to see os2-style windows on my desktop.

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.

- Casper