A little context, I am on course to release a plugin that manages some custom geometries for my company’s design process workflow. This plugin will continue to evolve, as our clients evolve.
The issue that I foresee is that at some point, we might need to go back to a project that depends on a plug-in version which isn’t the current one.
When this happens, the user will need to go to PlugInManager, remove the plugin, download the past version, then re-open rhino and work with the compatible plugin. Is this the way it is intended to work?
Yep! As long as you version your plugin you can install/uninstall versions and use whichever one makes sense. In the PackageManager there is a setting to automatically update on load, you’ll want to make sure that is unchecked before someone downgrades.
Then I got another question… For my Plugin to exist inside the package manager, does it need to be public (as in everyone can search for it and see it) or can it be held privately (hidden from everyone)? I don’t think I would be allowed to upload it freely.
You don’t need to publish the plugin to use yak packages and the package manager. yak packages can be drag dropped onto your Rhino, or you can just put the yaks in a folder everyone can access and add that to your yak source paths in the Rhino advanced settings under Rhino.Options.PackageManager.Sources
