Sounds good to have all the options. I also expect to be able to set properties like description, category, subcategory or icon (and hopefully more metada and even better using RDF languages) so it could be found in the components ribbon, used as a normal document, and maybe as a file as well? not sure if it is worth it.
To me what sounds better is to use URL rather than local paths, which is something that the food4rhino server could offer. It miss a private repository and a way to create invitations to private Hops definitions so that just those with that invite can run it, with an optional expiration date or by uses. If that is the case, the user should be able to upload/download to F4R from the rhino app, as if it were a cloud folder just for hops definitions. The rhino license could give limit space or a limit number of files, and to pay for more. It also could be paying creators to access the url/authorization.
It also demands a snippet manager to avoid continuing in the jungle with a machete and finally start building villages. This process library/searcher could be local and online. For example, the user rather than to come here or google to find examples of “parametric facade”, they could search there and to find all public access definitions in food4rhino about it, with a preview of its inputs and outputs. And allows to make advanced searches via webhooks.
Well maybe that’s too much for the moment, but yes please make the URL option working with a google drive shared link or any other repository.