Template talk:Component

Simplify?
I wonder, does the popup provide enough added value to justify the overhead? Each VSM call adds nearly 1000 characters, making it impossible, e.g., for Infobox-spell to test whether the parameter includes a somatic component. I'd be inclined to go back to a simple link. I doubt anyone would miss the popup. (Shoemaker) &rArr; Hoopy Froodle (Contribs • Message • Email ) 14:32, August 3, 2019 (EDT)
 * Instead of passing the template V or S to the spell template parameter, spells should pass a simple V or S with multiple values separated by comma. Then the spell template can easily check what values were passed and call the equivalent templates that display the pop-ups. &rArr; Faltout (Contribs • Message • Email )
 * I agree with you, simpler parameter values are better. Unfortunately, that's not how 400+ spell pages are currently written. ( Infobox-spell is designed to be backward-compatible, accepting any values currently passed into Spelldescription. ) On the bright side, I decided to generate Arcane spells with no somatic component as a DPL page rather than an auto-assigned category, rendering my immediate issue moot. I'd still rather see Component return a simple link, however. Again, simpler is better. &rArr; Hoopy Froodle (Contribs • Message • Email ) 21:07, August 5, 2019 (EDT)

Spells by component
I just came across C:Spells by component, almost entirely unpopulated. The subcategories could be assigned from within Component, I think. Or they could be assigned within Infobox-spell, but only if Component is simplified as discussed above. &rArr; Hoopy Froodle (Contribs • Message • Email ) 13:13, August 6, 2019 (EDT)
 * I reverted later comments that resulted from viewing a work in progress. Thanks, Shoemaker. &rArr; Hoopy Froodle (Contribs • Message • Email ) 18:50, August 6, 2019 (EDT)