Had a few questions regarding the distribution of a plugin. This plugin depends on a console app that is to be installed along with the plugin. The plugin will also need a dedicated space to write/read from for some operations.
What I have seen before is that plugin devs will install program specific stuff into Program Files or Application folders, and user specific stuff (configuration files, temp read / write) to AppData or Documents folders.
I’ve never created an installer before, but I am wondering if there is enough in the rhi framework to help me achieve this, or if I should be looking to create an installer so that everything lands in the right place?
At the moment the plugin is a proof of concept, most Rhino parts working well. My main conundrums deal when considering the potentially limitless configurations, security restrictions, etc users out there might face. While I can imagine I will not get it right the first time, it would be nice to start out with some hints on how to minimize the type of user cases.
This could also serve as a general discussion, not just with my specific plugin concerns. Is the RHI framework meant to be a facilitator for plugin distribution?