Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!uunet!zephyr.ens.tek.com!uw-beaver!Teknowledge.COM!unix!mxmora From: mxmora@unix.SRI.COM (Matt Mora) Newsgroups: comp.sys.mac.hypercard Subject: Re: FONTs in stack: what's bad? Message-ID: <18838@unix.SRI.COM> Date: 3 Dec 90 18:36:34 GMT References: <46927@apple.Apple.COM> <1990Nov29.010919.24666@hayes.ims.alaska.edu> <47015@apple.Apple.COM> Reply-To: mxmora@unix.UUCP (Matt Mora) Organization: SRI International, Menlo Park, CA Lines: 29 In article <47015@apple.Apple.COM> bc@Apple.COM (bill coderre) writes: >This is from Technical Note 245, August 89 version: [Stuff deleted] >Well, that's their opinion. As best I can tell, MacPaint, MacDraw, >PixelPaint, and Hypercard all have font information in their resource >forks. And, apparently, Hypercard tries to facilitate this practice by >forcing the Font Manager to rebuild its internal info. The Tech note says its OK for an application to have Font's in its resource fork, its the documents (stacks) that they have problems with. Its just another example of hypercard breaking the rules just to suit itself. :-) (notice the smiley. Boy would I get flamed if I left that out) Maybe now that Claris has the ball, they will play by the rules. (when hypercard first came out, who was going to tell Bill "Gee, what a great program but I think we can't release it because it breaks too many Human interface Guidelines".) I think 2.0 is much better now at keeping the faith. Good work Guy/Gals! -- ___________________________________________________________ Matthew Mora | my Mac Matt_Mora@sri.com SRI International | my unix mxmora@unix.sri.com ___________________________________________________________