As of OMC 4.0 Abracode.framework is relocatable. It can be embedded in applet bundle in Applet.app/Contents/Frameworks or can be installed for all users in /Library/Frameworks
Each method has its advantages and disadvantages.
When embedded in an app:
makes the app standalone (can be redistributed when codesigned) (+)
makes the app bigger (-)
makes the framework harder to update (applet stays with the embedded version of the framework) (-)
When installed in /Library/Frameworks:
the applets are smaller (+)
one upgrade of the framework upgrades all applets (+)
installation is painful, especially when deploying to multiple machines in an organization (-)
The idea is to support a 3rd location, which would allow updating all apps at the same time, keep them small (only a single copy of Abracode.framework) and not force each user to go though a painful installation in global location.
The on-disk hierarchy would be:
Applets/AppletA.app
Applets/AppletB.app
Applets/Frameworks/Abracode.framework
The order of finding Abracode.framework by OMC 4.0 Applets would be:
Applets/Applet.app/Contents/Abracode.framework
Applets/Frameworks/Abracode.framework
/Library/Frameworks/Abracode.framework
As of OMC 4.0 Abracode.framework is relocatable. It can be embedded in applet bundle in Applet.app/Contents/Frameworks or can be installed for all users in /Library/Frameworks Each method has its advantages and disadvantages. When embedded in an app:
When installed in /Library/Frameworks:
The idea is to support a 3rd location, which would allow updating all apps at the same time, keep them small (only a single copy of Abracode.framework) and not force each user to go though a painful installation in global location. The on-disk hierarchy would be: Applets/AppletA.app Applets/AppletB.app Applets/Frameworks/Abracode.framework
The order of finding Abracode.framework by OMC 4.0 Applets would be: Applets/Applet.app/Contents/Abracode.framework Applets/Frameworks/Abracode.framework /Library/Frameworks/Abracode.framework