You've poured your creativity into a new plugin for Rhino for Mac, and now comes the exciting part: getting it into the hands of users. While Rhino for Mac doesn't boast a flashy, built-in Plugin Manager like some other software, the process of installing plugins is surprisingly straightforward. Think of it less as a technical hurdle and more as a simple packaging exercise.
Let's dive into how this works, keeping in mind that the older .macrhi format is being phased out in favor of a more robust Package Manager. However, understanding the .macrhi method is still valuable, especially if you're working with existing workflows or older versions.
The .macrhi Method: A Step-by-Step Walkthrough
Imagine you've successfully built your plugin, let's call it HelloRhinoCommon, and it's sitting in a folder, perhaps labeled 'Release' or 'Debug'. The first step is to give this folder a special identity. You'll rename it by adding the .rhp extension. So, HelloRhinoCommon becomes HelloRhinoCommon.rhp. Don't worry, macOS will ask if you're sure about this change – just click 'Add'. You'll notice the folder's icon might change, signaling its new role.
Next, we need to package this up. Right-click (or Option-click) on your newly renamed .rhp folder and select 'Compress'. This creates a standard zip archive. Now, just like before, we're going to rename this archive. Single-click its name and change the extension from .rhp.zip to .macrhi. Again, macOS will prompt you to confirm this change; select 'Use .macrhi'. The icon should transform into a distinct Rhino RHI icon, a clear sign that it's ready for installation.
Installing Your Plugin
This is where the magic happens. If Rhino for Mac is already open, you can simply drag this .macrhi file directly onto the Rhino application's icon in your Dock. Alternatively, if Rhino isn't running, just double-click the .macrhi file. Rhino will launch automatically and guide you through the installation process. You'll likely see a confirmation dialog – click 'OK'.
Crucially, for your plugin to become active, you'll need to Quit and Restart Rhino. Once it relaunches, your plugin should be ready to go.
What's Happening Under the Hood?
So, what exactly is a .macrhi file? Essentially, it's a clever disguise. Rhino for Mac recognizes this extension and knows that the file is actually a compressed archive. When you install it, Rhino unpacks it and places the plugin files in a specific location: ~/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/. When Rhino starts up, it scans this directory, looking for .rhp files (which are themselves packages containing your plugin's core assembly). If it finds them and can load them successfully, your plugin is ready for use.
It's worth noting that the User Library folder is hidden by default. To access it, navigate to your Home folder in Finder, press Command+J to open View Options, and check 'Show Library Folder'. You might want to add it to your Finder sidebar for easier access later.
While the .macrhi method is still functional, the future for plugin management in Rhino for Mac points towards a more integrated Package Manager, which offers more advanced features, including version-specific and platform-specific installations. But for now, this packaging trick is a reliable way to share your creations.
