@chriswmackey most of what I asked, think and found out about how Materials are handled in Pollination is written down here in this forum. I have to admit it’s a bit scattered and unanswered, but let’s have a look if I can condense it.
If I do that it looks like shown
This means to me the material is saved somewhere?
Only available in this particular file.
And in six months I need to know which file to start to have access to the saved materials?
(OK concrete maybe not the best example for a specific material…)
Right this works like you indicated.
I’ve created a grasshopper file to manage my Materials the way I like them to be sorted.
Leading to 11 .json to be managed.
But, if I have to follow this advice by @ayezioro
It’s either 11 Files with a relatively complex .gh structure, not very comfortable to handle and devellop.
Or someday 200 files with different names to be picked up by Pollination?
Yes, of course I can dump everything in one large file. => Handling?
Do you know of a way when two instances are running parallel?
Leads to this statement
This also occurs when I’m working on a new project and realize I forgot to define a material.
Is there a way to reload the user libraries in an open instance?
Out of my still limited perspective it looks like currently there is no overall picture on how to effectively handle user defined materials without much effort.
Like I said. In my opinion, for general use, concrete only needs to be defined once. Rest is about thickness?
Maybe it makes sense to question grown paths at the moment and take a look from scratch if there might be a more convenient and up to date way to handle Materials in Pollination (Grasshopper)?