I have a stack of plug-ins for my application in a "plug-ins"
folder in the same folder as my application. I can set set this
as the default folder for the shared library search algorithm
described in the Code Fragment Manager documentation
by creating an alias resource that points to the file
and setting the right alias ID in the cfrg resource. OK so far.
The problem is, what happens when the user moves my application
to a different computer? Now the alias points to the folder location
on the previous computer's disk. I need to either: a) force Code Fragment
manager to resolve the alias relative to my application file, or
b) make a new alias and stuff it into my application resource fork
if my app finds that said alias doesn't point to the right folder.
As I don't know how to do a), I'm currently using b), which is not
only breaking the rule about an application not modifying itself,
but it also forces the user to relaunch the application, bacause CFM has
already set the shared library search path.
Any ideas? Am I doing something very silly? Is there a way to build an alias
such that it can only be resolved relative to another file?