nanogui: tcl/tk
Subject:
RE: tcl/tk
From:
"Scott Redman" ####@####.####
Date:
8 May 2000 16:55:50 -0000
Message-Id: <NDBBKOKBCMMALHMJIHNLIEKCCGAA.redman@scriptics.com>
It's not really the GDI layer that I'm worried about, but rather
the rest of the (non-GUI) Win32 API. The entire event notifier
on Windows is different than on Unix (which uses select()), and
I'm worried that the Win32 Tk code will depend on the Windows
version of the notifier, and a few other things.
Tk is really rather complicated, and probably does a lot of things
you don't expect a scripting widget set to be doing. I'm going to
talk to Jeff when he gets in, since he is a lot familiar with all
of it than I am.
-- Scott
> -----Original Message-----
> From: Greg Haerr ####@####.####
> Sent: Monday, May 08, 2000 9:10 AM
> To: Scott Redman; ####@####.####
> Subject: Re: tcl/tk
>
>
> : Actually, given the Win32 port's reliance on the Win32 architecture
> : this isn't as easy as you might think. It might be easier to work
> : with the NanoGUI code, but we're considering both options now.
> :
>
> Microwindows' win32 semantics are pretty accurate. All of the
> erasebkgnd, paint and DC handling are almost exactly like win32.
> In addition, private DC's are supported, as well as user clip regions.
>
> What aspects are you thinking differ?
>
>
>
> : It might be possible to rework the Win32 X Emulation Layer in Tk
> : to work with Microwindows. But, this will take a lot of work,
> : IMHO.
>
> Usually the win32 port can be performed with just a few changes
> that would be #ifdef MWIN
>
> Regards,
>
> Greg
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
