Xref: utzoo comp.windows.misc:1776 comp.windows.x:32130 comp.sys.mac.misc:8026 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!tandem.physics.upenn.edu!claytor From: claytor@tandem.physics.upenn.edu (Nelson Claytor) Newsgroups: comp.windows.misc,comp.windows.x,comp.sys.mac.misc Subject: Re: Mac vs. XView Message-ID: <36715@netnews.upenn.edu> Date: 31 Jan 91 20:19:14 GMT Sender: news@netnews.upenn.edu Organization: University of Pennsylvania Physics Dept. Lines: 28 References:<981@borg.cs.unc.edu> In article barnett@grymoire.crd.ge.com (Bruce Barnett) writes: > Well, I can try. Take an XView panel, with text and a scrollbar. (I'll > simplify it somewhat.) [stuff about simplicity of XView window creation deleted] [more stuff about complications of THINK C deleted] OK, now let's try it with MacApp. What routines do you have to know? Essentially none, if you want the "working application that does nothing" described. Use the 1 1/2 pages example program that initializes the MacApp routines and the toolbox. Now use the application called ViewEdit that is included with MacApp, and *draw* your window's interface. Then you have a working program that does nothing. My observation on the subject would be that I have yet to see an X program with an interface anywhere near as nice as the typical Mac application's, so how easy could it be? (Word is specifically excluded here >:-)) The object oriented approach described in the original message has been implemented in the forms of both MacApp and the THINK class library. No one *has to* know every last toolbox detail any more, or even how to do scrolling. Nelson Nelson Claytor claytor@tandem.physics.upenn.edu