On Tue, Jun 09, 1998 at 08:26:21PM +0900, P. E. Jareth Hein wrote:
Well, we talked about this before... The big problem is that
neither
gtk or Qt use Xt, and therfore all the resource-related code and event
loops would need to be rewritten.
Yup, I was there at the time. The difference, now, is that XEmacs/w32
works. I.e., most or all the needed abstractions needed to have a
sensible integration of different GUIs are there.
Hmmm...
132 console-msw.c
239 console-msw.h
313 device-msw.c
421 dialog-msw.c
665 dired-msw.c
2805 event-msw.c
719 frame-msw.c
1903 glyphs-msw.c
79 glyphs-msw.h
789 menubar-msw.c
43 menubar-msw.h
1233 objects-msw.c
51 objects-msw.h
1493 redisplay-msw.c
306 scrollbar-msw.c
62 scrollbar-msw.h
180 select-msw.c
624 toolbar-msw.c
12057 total
163 balloon-x.c
282 console-x.c
492 console-x.h
1762 device-x.c
276 dialog-x.c
2803 frame-x.c
4294 glyphs-x.c
106 glyphs-x.h
628 gui-x.c
82 gui-x.h
815 menubar-x.c
1035 objects-x.c
67 objects-x.h
2337 redisplay-x.c
760 scrollbar-x.c
75 scrollbar-x.h
799 toolbar-x.c
16776 total
374 console-tty.c
301 console-tty.h
228 device-tty.c
268 event-tty.c
256 frame-tty.c
391 objects-tty.c
52 objects-tty.h
1553 redisplay-tty.c
3423 total
<sky kind=blue version="21.1 or more">
We should probably regroup everything non-portable in bigger
function-oriented files. Like GUI, filesystem, etc... If we tend to
make clear and documented interfaces portability will be easier
between unix and NT (and MacOS X, BeOS, etc... :-).
Actually, if you have a clean interface on which to write the support
for another OS/GUI/etc, the probability for someone to go and do it is
much higher.
</sky>
OG.