Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!rpi!uupsi!njin!paul.rutgers.edu!aramis.rutgers.edu!athos.rutgers.edu!wiechman From: wiechman@athos.rutgers.edu (NightMeower) Newsgroups: comp.sys.mac.programmer Subject: Re: Local/AppleTalk Connectivity in MacApp Message-ID: Date: 4 Jan 91 18:24:18 GMT References: <1991Jan3.221839.21979@athena.cs.uga.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 36 In article <1991Jan3.221839.21979@athena.cs.uga.edu> fore@athena.cs.uga.edu (Howard Fore) writes: > Ok, you MacAppies: > > 1. How well is MacApp at dealing with Apple/LocalTalk communication? Are there > prewritten methods and classes to deal with this? I need to write a program > that will communicate across a LocalTalk LAN to retrieve a text file from > a hard drive. Will I have to write the routines myself for going across > LocalTalk? Any advice? The 2.0+ version of MacApp does not have anything on AppleTalk. 1.1b1 had an example of a Communications program that would send messages from one Mac to another. When MacApp was updated they left this sample out due its lack of popularity and improved the other samples. The code from the previous sample code be updated without too many problems because the deep down code has no user interface. One point to mention is that MacApp cannot be used to write DAs, INITs, etc. I imagine that it will be possible to do so in the future. > 2. The APDAlog lists MacApp 2.0 as being available on a CD as well as 10 disks. > It also mentions various "goodies" that are on the said CD with MacApp. What > are these "goodies"? The goodies include tear-off menus, custom menus, and floating palettes. These are currently unsupported but work very well. I am using them inside of a project that I am working on. There are others that I probably did not mention. Kevin -- =========================================================================== Kevin S. Wiechmann arpa: wiechman@cs.rutgers.edu This is only a test... for the next sixty seconds...