In early MacOS, fonts and desk accessories (small applications which could run concurrently with a main application in the pre-multifinder era) were resources which lived in the "System" file. An uninstalled font or desk accessory would be stored in the resource fork of a "suitcase", and a utility called the Font/DA Mover offered a simple UI for copying these resources between suitcases and the system file.
Decker doesn't use a forked filesystem, but still has "resources" in the form of various disembodied modular pieces that can be copied between decks: fonts, sounds, pattern/color palettes, lil modules, and contraption prototypes. When I designed the UI for managing and importing resources, I modeled it after the Font/DA Mover, and naturally called it the "Font/Deck Accessory Mover". :)
This is one of my favorite gags, so I'm glad at least a few people caught the reference.
Would you be able to explain it to those of us who did not grow up with Macs at the time?
In early MacOS, fonts and desk accessories (small applications which could run concurrently with a main application in the pre-multifinder era) were resources which lived in the "System" file. An uninstalled font or desk accessory would be stored in the resource fork of a "suitcase", and a utility called the Font/DA Mover offered a simple UI for copying these resources between suitcases and the system file.
Decker doesn't use a forked filesystem, but still has "resources" in the form of various disembodied modular pieces that can be copied between decks: fonts, sounds, pattern/color palettes, lil modules, and contraption prototypes. When I designed the UI for managing and importing resources, I modeled it after the Font/DA Mover, and naturally called it the "Font/Deck Accessory Mover". :)
1 reply →