nanogui@linuxhacker.org

Subject: Re[2]: wine
From: Vladimir Cotfas
Date: Tue, 24 Oct 2000 22:17:40 -0700 (PDT)


On Wed, 25 Oct 2000, mark dufour wrote:

> > Hmm, one has to re-write the dev_x11 in WINE for nano-X [I guess it would
> > not be feasible for mwin/Win32 :]. This should not be a problem.
> 
> why would it not be feasible for mwin/win32 ? it might take some more
> work, but if the api is closer to the real win32 api it's probably more
> elegant and faster in the end.
*BECAUSE* WINE is a clean-room implementation of Winderz *AND* it works
pretty well *AND* mwin/Win32 does not aim at 100% compatibility with
Winderz (I think Greg wants people writing WinCE apps migrate immediatly
to mwin/Win32).

Moreover it would ve silly to use the mwin/Win32 API for re-writing
dev_x11. "dev_x11" is the means through which WINE communicates to the
graphics device [right now only X11R6]. (Veerry silly: Winderz native
application -> WINE -> dev_x11 -> mwin/Win32 -> hardware)

> 
> I'm still orienting myself but so far this looks like the best solution
> for improving wine graphics speed and portability. if it remains that way
> I'll probably start working on it in the following weeks. but I'm no wine
> or nanogui expert ;-)
Err, "nanogui" is only a name :)

Yiu know something? You gave me a hell of a nice idea: I can port dev_x11
to nano-X [well, I know how: tank hao did port FLTK to nano-X so this
would be feasible too].

Regards,

Vladimir