Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!nrl-cmf!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!mcvax!enea!tut!santra!jmunkki From: jmunkki@santra.UUCP (Juri Munkki) Newsgroups: comp.sys.mac Subject: Re: FullWrite on shelves Keywords: fullwrite nonvapor Message-ID: <12788@santra.UUCP> Date: 11 May 88 13:57:12 GMT References: <158@amcad.UUCP> <52428@sun.uucp> Reply-To: jmunkki@santra.UUCP (Juri Munkki) Organization: Helsinki University of Technology, Finland Lines: 59 In article <52428@sun.uucp> chuq@sun.UUCP (Chuq Von Rospach) writes: >I think so, so far. I picked up my copy at ComputerWare for about $260. I I hope we get ours (we ordered 3 of them in February)... >- The manual is incomplete in some areas. It mentions, but never explains, > stationery (read-only documents that are used as templates). It > barely mentions something called background files, which are (I > think!) used to import stuff like EPS files into stationery. I > really don't understand what they do, how, or why. I'm hoping that > the examples shipped with the program explain it, since the manual > ignores them. This looks to be, also, the only way to get postscript > code into your documents. Hope I'm wrong on that one. You can always use Postscipt Escape to incorporate postscipt in your documents. This works even with programs like MacWrite and MacDraw. >+ They've implemented something called a variable. A more generalized flavor > of the various page/date/time icons in Word headers. you can define > your own, too (I'm not sure why yet, though). One that I find > missing is the # of words (variables exist for pages and > characters). I think people will find a lot of uses for them. I guess the version number or name of the document could be one. My address would make a good variable. :-) >- Startup is rather slow, and it brings up a copyright message every time. > Not really bad, but it stays up long enough to be irritating, and I > almost get the feeling AT has a wait loop in the initialization code > for the startup screen. If that's true, I hope someone finds a patch > for it. If not, there's a lot of initialization going down. I did some digging with TMON (and removed the demo text from my demo version) and found out that FullWrite uses packed code resources. It checks if the code is packed and unpacks every time it loads from disk. Unfortunately it has a lot of code resources to unpack when it starts up, so it is very slow. Fortunately it does check first if the code is packed (I bet they use an unpacked version of FullWrite at Ann Arbor and Aston Tate). I wrote a small FKEY that saves a code resource once that it has been unpacked. It worked fine, but I haven't had time to do any serious experimenting. Of course an unpacked version of FullWrite no longer fits on a disk, but then again...who cares. I would REALLY like to get in touch with the developers of FullWrite. (E-Mail would be great and TeleFAX is ok...) I'd like to help them internationalize FullWrite because we need a version with Finnish hyphenation and probably a Finnish spelling checker too. So, if you know how to contact them, please tell me how. Juri Munkki Helsinki University of Technology, Computing Centre Microcomputing Support Division Otakaari 1, Room Y250A SF02150 Espoo, Finland Internet: jmunkki@santra.hut.fi Bitnet: jmunkki@fingate.bitnet Telex: 125161 htkk sf TeleFAX: +358 0 465 077