[Mr. V]

@Mr. V - My own preference is to provide all artwork types based on the widgetType property, primarily because it's and doesn't support (for example, at the moment selecting Skin Helper Service through video add-ons will only offer a couple of art choices, though its widgets actually returns all of them. Whilst it may mean an extra entry on a FAQ (if the add-on you've selected doesn't support the art type you've chosen -- choose again), it means that the artwork types are never artificially limited.

Right now I believe the code is almost exactly identical to yours. It would be great to keep it so so that both Nox mods can benefit from your widget work. And if you're serious about helping out, just say the word and I'll give you push rights to the repo where we're doing the work, so you can take on any jobs that take your interest

I actually use the both 'widget' and 'widgetype' for artwork choices. So for example library data provider in <widget-groupings> widget="library" widgetType="movies".

But yeah my main point was exactly as you said "impossible to know what artwork a given add-on does" that's my reasoning for using <widget-groupings> so I can set both values. It was a pain to have to code in all the groupings but it is easy to limit artwork choices then. It would be great to keep the code the same and future updates will be really easy.

Alternatively i could change it so any artwork is selectable for any widget. There is enough fall-back values in place so you should always see artwork. (not my preference though)

I am more than happy to help out and do some updates on git. I could update nox silvo and mad nox widgets at the same time. Time might be a bit limited over the next week though. But I'm sure I could squeeze in a few hours or so on madnox to get all the nox silvo options working.