Path: utzoo!attcan!uunet!wugate!wuarchive!swbatl!texbell!sw1e!uucibg From: uucibg@sw1e.UUCP (3929]) Newsgroups: comp.sys.mac.programmer Subject: Re: Config File Resource Blues Message-ID: <1813@sw1e.UUCP> Date: 28 Jul 89 18:54:48 GMT References: <2013@dogie.macc.wisc.edu> <1165@intercon.UUCP> <7930@hoptoad.uucp> <1034@unix.SRI.COM> <26241@agate.BERKELEY.EDU> <14355@dartvax.Dartmouth.EDU> Reply-To: uucibg@sw1e.UUCP (Brian Gilstrap [5-3929]) Organization: Southwestern Bell Telephone Co Lines: 55 In article <14355@dartvax.Dartmouth.EDU> earleh@eleazar.dartmouth.edu (Earle R. Horton) writes: +In article <26241@agate.BERKELEY.EDU> lippin@math.berkeley.edu writes: ++Recently stores@unix.UUCP (Matt Mora) wrote: +++About the "remebering the state of things" I would like to see some sort of +++standard about text file resources. It would be wonderful for my appliction +++to be able to read a text file and get the font, font size, window +++size/position and cursor location no matter what application created it. ++A fine idea. How about if we all use whatever MPW uses? It's got to ++be the most commonly used editor that does this, and I'll bet (or at ++least hope) that it isn't too badly hacked. + The 'MPSR' resource which is used to store this information is +undocumented (read: subject to change). You can access this +information from tools that you write, but only by going through the +MPW library routine faccess(). The information is not available to +standalone applications using this method. I agree that a standard +for this sort of thing would be real nice to have, and that it would +be even better if supported by Apple. Okay, I'll bite :-), why don't we just come up with a resource format and use it? Of course, I imagine everyone will argue about it for several months before coming to a conclusion (if that ever does happen :-) but, hey, I'm learning lots about the Mac from these discussions, so I won't complain. On the off chance that this'll actually become a discussion, I'll start it off with: Stated above, you'd want: + font + font size + window size + window position + cursor location (within the text). The cursor location seems to present some definite problems. My non-display- able character may be someone else's display-able character. I suppose the cursor location could be kept in the case of text only files. What does one do when one gets a file that was last used on a mac with a larger monitor than the current one? Move off-screen windows barely on screen? Leave windows the same even if they are partly off-screen? Also, is RFT really that bulky? (I've never had a chance to look at it... speaking of which, where can I get a description?) -------------------------------------------------------------------------------- Brian R. Gilstrap ...!{ bellcore!texbell, uunet }!swbatl!sw1e!uucibg One Bell Center +---------------------------------------------------------- Rm 17-G-4 | "Winnie-the-Pooh read the two notices very carefully, St. Louis, MO 63101 | first from left to right, and afterwards, in case he had (314) 235-3929 | missed some of it, from right to left." -- A. A. Milne -------------------------------------------------------------------------------- Disclaimer: Me, speak for my company? You must be joking. I'm just speaking my mind.