ews00461@uxa.cso.uiuc.edu (07/23/90)
The answer (as I understand it): console I/O can only be done within an MPW tool. This annoys me to no end. MPW C *should* be a fine environment for porting of stdio based software, and this limitation eliminates the possibility. I know, I should not complain and write my own stdio library for apps... Still, it annoys me. Eric W Sink
sbd@dsto.oz.au (Scott Davis) (07/24/90)
This is for a fellow worker (johnh@itd.dsto.oz.au): Can someone please answer the following (simple?) question? How does one perform plain, unvarnished keyboard input and console output using MPW C 3.0? Thanks, Scott Davis -- Scott Davis Phone (08) 259 6360 Information Technology Division, Defence Science and Technology Organisation Salisbury, South Australia sbd@itd.dsto.oz.au
sabbagh@acf5.NYU.EDU (sabbagh) (07/24/90)
In article <1234600048@uxa.cso.uiuc.edu> ews00461@uxa.cso.uiuc.edu writes: > > > >The answer (as I understand it): console I/O can only be done >within an MPW tool. > I would like to know how this is done as an MPW tool. I cannot seem to write a truly interactive tool. The best I can do is have all the input set up before any output, i.e., I can't do prompting. Any ideas? Hadil G. Sabbagh E-mail: sabbagh@csd27.nyu.edu Voice: (212) 998-3125 Snail: Courant Institute of Math. Sci. 251 Mercer St. New York,NY 10012 Disclaimer: This is not a disclaimer.
mneerach@c.inf.ethz.ch (Matthias Ulrich Neeracher) (07/26/90)
In article <1234600048@uxa.cso.uiuc.edu> ews00461@uxa.cso.uiuc.edu writes: >The answer (as I understand it): console I/O can only be done >within an MPW tool. I think I have seen a file called WriteInWindow somewhere on a CD. This was said to allow Applications to use console I/O. I haven't tested it yet, though. Matthias ----- Matthias Neeracher mneerach@c.inf.ethz.ch "I wouldn't recommend sex, drugs or insanity for everyone, but they've always worked for me" -- Hunter S. Thompson
lsr@Apple.COM (Larry Rosenstein) (07/27/90)
In article <111@neptune.inf.ethz.ch> mneerach@c.inf.ethz.ch (Matthias Ulrich Neeracher) writes: > >I think I have seen a file called WriteInWindow somewhere on a CD. This >was said to allow Applications to use console I/O. I haven't tested it >yet, though. This is a unit I did for MacApp originally. It certainly comes with MacApp (which is probably the lastest version), but I don't know if some version is also available on a CD. The allows for both input and output, and various options for the number of lines to save, redirecting output to a file, etc. -- Larry Rosenstein, Object Specialist Apple Computer, Inc. 20525 Mariani Ave, MS 46-B Cupertino, CA 95014 AppleLink:Rosenstein1 domain:lsr@Apple.COM UUCP:{sun,voder,nsc,decwrl}!apple!lsr
keith@Apple.COM (Keith Rollin) (07/27/90)
In article <9446@goofy.Apple.COM> lsr@Apple.COM (Larry Rosenstein) writes: >In article <111@neptune.inf.ethz.ch> mneerach@c.inf.ethz.ch (Matthias Ulrich Neeracher) writes: >> >>I think I have seen a file called WriteInWindow somewhere on a CD. This >>was said to allow Applications to use console I/O. I haven't tested it >>yet, though. > >This is a unit I did for MacApp originally. It certainly comes with MacApp >(which is probably the lastest version), but I don't know if some version is >also available on a CD. The allows for both input and output, and various >options for the number of lines to save, redirecting output to a file, etc. So _you_ wrote that! I always wondered. A long time ago, someone in DTS extracted that from MacApp 1.x and made it a standalone unit. I think it might have been Jim Friedlander, as a lot of his sample code used it. That unit is now on the quarterly Developer CD (Phil & Daves, A Disk Called Wanda, Disky Business), along with the warning that we won't support it, we don't know how it works, and you better not ship an application with it because we don't guarantee its working. Basically, it's for testing and playing only. However, all those nasty warnings aren't to say that it's not a rubust unit. After all, Larry wrote it, so it must be solid. It's just that it's never been formally tested outside of MacApp. -- ------------------------------------------------------------------------------ Keith Rollin --- Apple Computer, Inc. --- Developer Technical Support INTERNET: keith@apple.com UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith "Argue for your Apple, and sure enough, it's yours" - Keith Rollin, Contusions
earleh@microsoft.UUCP (Earle HORTON) (07/28/90)
In article <111@neptune.inf.ethz.ch> mneerach@c.inf.ethz.ch (Matthias Ulrich Neeracher) writes: >In article <1234600048@uxa.cso.uiuc.edu> ews00461@uxa.cso.uiuc.edu writes: >>The answer (as I understand it): console I/O can only be done >>within an MPW tool. > >I think I have seen a file called WriteInWindow somewhere on a CD. This >was said to allow Applications to use console I/O. I haven't tested it >yet, though. > WriteLnWindow does work for this purpose, but: a) Apple doesn't want it used for anything but debugging. b) Output text is handled by TextEdit and is therefore limited to 32k in size. You could probably get away with using WriteLnWindow for in-house, non-commercial applications. It is on Phil and Dave's Excellent CD. Earle Horton Disclaimer: My employer does not necessarily share any opinion expressed here.