A little confused with the synergy between these two. I want to upload a Grasshopper plugin. I have read the instructions on how to upload it via the yak utility for the package manager so that it shows within Rhino’s dialog. I then want to also have it on the food4rhino website, but if I go to “Add app” it asks me to upload a zip file again and it also allows me to fill more information than the package manager process (images etc).
My question is: how would I have a single source for my plugin, both in the package manager with yak and on food4rhino with the extra image info without having to upload separately?
The steps in the FAQ suggest that I upload my plugin to food4rhino first (using the “Add App” button and uploading a .zip I presume), and then make it into a package from the website’s functionality. So no need to use yak am I correct?
Is the reverse possible? Upload through yak and make it into an app in food4rhino later?
I do not want to make an installer. I have a zip archive with the .gha and all other required files. Can I upload that by itself and what will happen when the user downloads it? Is the user going to have to know how to unzip the contents to an appropriate folder? This would not work for me in that case. What would be my alternative in this case?
Scenario 2 yak:
By using a yak upload to the package manager server, I assume the installation will be automatic without the user having the know anything about the installation folders or me having to make an installer.
If I go this route and later want to also link this to a food4rhino app entry, how will the installation take place (refer to Scenario 1 above)?
If you upload your Zip file on food4Rhino and then send it to YAK, the users will never see your zip file as the link on food4Rhino will open Rhino and run the command Package Manager looking for your package name.
If you use a YAK upload, when you Add a page on food4Rhino from this YAK package, the result is the same, a link to open Rhino > Package Manager > search for your Package.