Add clarification about widget types

[WoosterInitiative]

Help users save time in the event that they're trying to use these extra features with a light widget where it will not work.

[codingjoe]

Hi @WoosterInitiative,

Thanks the pull-request. I always appreciate people improving the documentation.

Reading your change I notice, maybe documenting the "light" widgets does more harm than it does good. I always felt, the abstract inheritance structure is very difficult.

I'm not saying you should fix all that in your pull-request. I'm just curious to get your input on that.

Cheers,
Joe

[WoosterInitiative]

Not sure why I didn't see a notification for this I'll give it some thought. Thanks for the feedback.

[WoosterInitiative]

@codingjoe

I always felt, the abstract inheritance structure is very difficult.

I guess I'm not quite sure what you mean by that. Because it's been a while (my fault), I don't remember exactly which fields I was wishing to do this with, so I don't remember the context, but I do remember my frustration. This page makes it feel like I should be able to chain any two select2 fields, so I spent a considerable amount of time trying to do so, thinking I was making some silly mistake (as is so often, so very, very often, the case), only to discover that I was trying to do something that wasn't possible.

I'm not able to see the harm yet.

[codingjoe]

@WoosterInitiative never mind then. It's a good improvement to the docs, we don't need to make it anymore complicated. Thanks :)