![]() Library/Application Support/Sandvox/PlugIns/.~/Library/Application Support/Sandvox/PlugIns/.Sandvox detects plug-ins in the following locations: Any other keys should be set via the plist editor in Xcode or with Property List Editor.Set Principal Class (NSPrincipalClass) to be that of your SVPlugIn subclass.Set Identifier to be unique to your organization and plug-in.Switching to the Properties tab in the Target inspector: This is how Sandvox discovers how to load your plug-in for use. In the bundle's ist, set NSPrincipalClass to be the name of your custom class. #import MyPlugIn : how you import from Sandvox (rather than Cocoa) to gain access to the SVPlugIn base class. Make such a class its header should look something like this: Your plug-in needs a principal class descended from SVPlugIn, the base class Sandvox provides. Sandvox 2.5 dropped PowerPC (and Leopard) support, becoming solely a 32-bit Intel app.Sandvox 2.0 was a 32-bit app, running on both Intel and PowerPC Macs.We recommend you build your plug-in to match. Sandvox (version 2.8 or higher) is a Universal app, supporting bother 32 and 64-bit. Header Search Paths must include /path/to/Sandvox.app/Contents/Headersīundle Loader must be set to /path/to/Sandvox.app/Contents/MacOS/Sandvox (This Guide assumes Sandvox is installed in /Applications.) Both of these need to point to specific resources inside the Sandvox application. ![]() These are Header Search Paths and Bundle Loader. In order to compile and link correctly, your plug-in needs to set two build parameters for both Debug and Release builds. Keep this panel open you'll need it for the next section!. ![]()
0 Comments
Leave a Reply. |