Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!psuvm!blekul11!ghgaqz4
From: GHGAQZ4@cc1.kuleuven.ac.be
Newsgroups: comp.windows.misc
Subject: Re: Macintosh vs. X windows
Message-ID: <91052.104847GHGAQZ4@cc1.kuleuven.ac.be>
Date: 21 Feb 91 10:47:47 GMT
References: <930@borg.cs.unc.edu> <1991Jan28.173654.10133@cs.utk.edu>
Organization: K.U.Leuven - Academic Computing Center
Lines: 29

>>I hesitate to ask this.  Given a choice between developing for a
>>Macintosh and developing for X windows, why would anybody choose X?
>
>Because they don't want to be tied to single vendor.  Or perhaps they
>realize that X-based systems are the present/future of desktop
>computing.
>
>>I know nothing about the Mac toolbox, but I've been reading the
>>O'Reilly manuals on Xlib, Xt and Xview.  Seems like the Mac toolbox
>>couldn't possibly be as complicated as X.
>
>You might reserve judgement until you've looked at the Mac.

I find both the Mac toolbox and X toolbox rather complicated. I've
programmed in the X toolbox and I know people who program for the
Macintosh. I find it really strange that you need so much code
simply to open a window. The X toolbox is better, but still I prefer
the Amiga way of doing things (I mean in AmigaDOS 2.0 the new version
of the operating system). There is now a toolbox that is very easy to
use. A C program to open a window with a button could be written in
only about 12 lines, with on each line only one statement or declaration.
And you don't need external files like in X.
And this program would automatically account for window sizing, closing
of the window, refreshing of the window and it would include a small
event loop for the button.

This is of course my personal opinion.

            Jorrit Tyberghein