🚀 go-pugleaf

In article <4879@ihlpf.ATT.COM> straka@ihlpf.UUCP (55223-Straka,R.J.) writes:
>Yes, but even that's a workaround!  (I assume) you have to still open the
>font file manually every time you want to work on that file(s), or else
>you are forced to place the fonts in the appropriate folder so that
>Suitcase loads the fonts into the system heap at boot time anyway.  That is,
>unless Suitcase was smart enough to figure out that a used font was not
>system resident and go out and look for it.  Of course, that really belongs
>in the domain of the system software anyway.

  Suitcase solves two problems.  Allows you to use Font's with out installing
them in the system file using the Font/DA mover, & allows you to use more than
15 DA's at once.

  Suitcase still does not pre-load the information into the system heap.

  If you would take the time to read the resource manager in Inside Macintosh
you would discover that the Macintosh uses an on-demand memory Managerment
scheme for System Resources like Font's & DA's.  That means the memory is not
allocated until the user requests their presence.

  I'm not triing to be-little Suitcase {I mean I haven't tried to write it and
I'm sure there are some traps}  but all Suitcase does is "hook" some of the
more important resource calls so that they not only check the normal files
but any additional files suitcase wants them to see as well.  Notice that
all this does it allow the application to find additional resources, it doesn't
require them to be in memory.  When the user wants them in memory the resource
manager allocates the necessary memory and reads them in at that time, or if
they are already there it simply returns the handle to that memory.

>My point is that the operating system should take care of shielding these
>sort of interactions from the user (and it does now, although in a
>memory-hungry manner).  Tools like suitcase, f/da juggler+, et al. are very
>useful tools, but are really patches (workarounds) since they don't solve this
>original (memory-usage) problem.  (They do address OTHER, problems, of course!)

  There was no memory-usage problem since the Macintosh doesn't allocate 
memory in the way that you think it does.  When you get a chance pick up the
"Technical Introducation to Macintosh" from Apple, it goes over Memory
Management & Resources.  I think you'll find the information enlightning.




-- 
David M. O'Rourke

Disclaimer: I don't represent the school.  All opinions are mine!