Path: utzoo!attcan!uunet!lll-winken!ames!ncar!boulder!fozzard
From: fozzard@boulder.Colorado.EDU (Richard Fozzard)
Newsgroups: comp.sys.mac
Subject: Re: MenuFonts 2.02
Keywords: menufonts
Message-ID: <7541@boulder.Colorado.EDU>
Date: 18 Mar 89 16:56:16 GMT
References: <1989Mar16.144238.21189@csuchico.uucp>
Sender: news@boulder.Colorado.EDU
Reply-To: fozzard@boulder.Colorado.EDU (Richard Fozzard)
Organization: University of Colorado, Boulder
Lines: 20

The overhead you mention for MenuFonts IS damned annoying, even with plenty
of RAM cache. But since you have to replace an application's menus, there
may not be a way around it. (Could MenuFonts set up its own "personal RAM
disk" at boot to hold the fonts from disk"? This would be much better than
using general purpose RAM cache which gets rewritten all the time, but would
of course have to be defeatable for limited Meg systems).  This whole thing
really should have been part of Apple system software to begin with.

Despite the overhead, I absolutely love this program - so much so that I am
lost without it, and just put up with the hassle (I have several friends with
1 meg systems who do the same.) I have had absolutely no software conflicts,
which is truly amazing, given how invasive this program must be,and how many
different applications and INITS I use. And it is a world better than the
slow-as-molasses menu-font capability of Suitcase II (though this will solve
your overhead problems if you only feel an occasional need for a "real" font
menu).
========================================================================
Richard Fozzard
University of Colorado				"Serendipity empowers"
fozzard@boulder.colorado.edu