ResEdit

~ the obit ~

resedit lived on macs. i was on windows. the closest i got to resource forks was a confused readme in a shareware download where a mac file refused to behave on a turkish ibm clone in 2001. the larger story belongs to the mac power-user world i read about from outside.

the tool was an apple-published gui editor for the classic mac resource fork. every mac application from 1984 onward stored its menus and icons as numbered resources inside a fork attached to the same file as the executable code. dialog boxes, version strings, sounds, and cursors all lived there too. resedit opened that fork in a window full of icons. you could double-click a menu resource and edit the labels by hand, or drag a new picture into an icon slot to replace it. all of it persisted, often through restarts, sometimes through a crash that took the application with it.

the last official release was version 2.1.3 in august 1994. an unofficial 2.1.4 with a decompiler add-on circulated later, never blessed by apple. the powerpc transition skipped resedit, so the tool ran in emulation on every post-1994 mac through the classic compatibility shim. mac os x abandoned the resource fork model for nextstep-style bundles in 2001. the classic environment kept resedit barely usable until intel macs and 10.5 leopard cut it off entirely.

~ the rap sheet ~

~ what it was ~

the official audience was mac developers who wanted to inspect their own resources without compiling a separate tool. the actual audience that gave resedit its cultural life was a much wider set of curious users. anyone could rename the file menu of their copy of microsoft word for mac. anyone could replace the trash icon with something else. forums of the early 1990s were full of tutorials that started with "open resedit, navigate to type DLOG..." and ended with a screenshot of a custom interface. the barrier to teaching yourself how a mac app worked under its skin was a free download from apple.

~ how it got obsoleted ~

the resource fork itself died before resedit did. nextstep, then mac os x, treated an application as a directory containing its own resources as separate files in a bundle. resource forks remained as a compatibility carry-over on hfs+ disks for a long while, but new code stopped using them. by the time intel macs arrived and the classic environment was dropped, opening resedit meant booting an emulated old machine. the tool did not disappear. it became archaeological.

~ the long tail ~

people still keep copies of resedit 2.1.3 in their old mac emulator setups. the macintosh garden has it. mini vmac and sheepshaver users can launch it on a modern machine to poke at a 1991 game's dialog. the open-source resknife tried to do the same job for newer mac systems and saw limited adoption. the practice of editing your application's interface by opening a separate tool on the same desk has not really returned. modern apps are signed and sandboxed, so the resedit move would now break the signature and refuse to run.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »