Enhancement: Node group assignment

[Zentheon]

I've been building up a library of node groups that, while easy enough to access through the popout menu, would be super cool to have expanded upon. A few ideas I had for this:

1. Using the popularity system to fill a dedicated category out with custom groups whenever at least one has been selected.

2. Manually assigning groups to a dedicated category.

3. Automatically adding groups to categories based off the respective color those groups are assigned.

4. A separate pie menu for asset libraries instead. Root catalogues would be assigned their own categories, and then sub-catalogues could just be popout menus, like what Math and Mix nodes have.

I hesitate to suggest just throwing all node groups present in a file into the menu since that would create far too many entries in larger projects, and adding them based on certain criteria would be a lot more manageable. Otherwise, the feature could just be turned off.

I'm not sure how easily any of this could be adapted into the code, so if it's not within scope feel free to close!

[strike-digital]

This is something I would like to add, but you're right that it's a bit tricky to come up with design that doesn't result in massively bloated pie menus.

I think I would lean towards either having a separate menu for node groups, or allowing the user to choose which groups show up where in the menu.

I would like to come back to this in the future, but unfortunately I don't think I've got the time to develop this at the moment, as I'm pretty busy with work.

Thank you for the interest though, and feel free to give more suggestions, it's always useful to know what people want in the addon!

[Zentheon]

Glad the suggestions are taken into consideration! The two methods you pointed out both sound very convenient. Personally I use a number of utility groups very frequently alongside other basic nodes. An entirely separate menu could be useful for those who have various material libraries and prefer the pie workflow, though in my opinion the asset browser already exists for that kind of use case and should be taken advantage of instead.

Likewise, if adding custom groups to categories were ever implemented, having a user-defined blacklist for rarely (if at all) used default nodes would also be really nice. Though again, the popularity system works super well so it's not as important.