5 replies to this topic

[RZR0]

I'm thinking it would be a good idea to add a subtype parameter to the Item template. That way we can have a set of pre-defined subtypes (similar tot he ModLink template), with types like Cosmetic, Generator, Track, Potion, ... Those can then automatically also be added to the appropriate category.

 

Thoughts?

[felinoel]

That way we can call a list of that particular subtype whenever we need it?

[dgelessus]

(What template exactly are we talking about here? I noticed that I might be talking about something different after I was done typing already.)

 

That's kind of what I was originally going for with the whole modular/extensible infobox approach, but then I became lazy, took way too long to finish the base InvItem template, then I realized that my initial implementation was less than ideal in certain regards, then odd bugs started appearing, and then the code editor disappeared. *looks over to RZR0*

 

Anyway, I'd say infoboxes shouldn't do too much automatic categorization. I'm fine with categories like Blocks, Tools, Enchantments, but specific stuff like "Wands (Thaumcraft 4)", "Computer Peripherals", "Spell Components" shouldn't be done by the infobox. Those would require too much specific code in the infobox template that does nothing but add a category.

[RZR0]

I'm not talkign about subclassing the infoboxes, though I also had some ideas about that. But rather add a subtype parameter alongside the type parameter. So it'd say for example Type = Item (Food). And optional, like the ModLink template, we could integrate it with a template that adds [[Category:Food]] on such a subtype.

[dgelessus]

Hm, not sure about that. I can't think of any cases where it would be useful to show a type and a subtype. Why not just show "Food" instead of "Item (Food)"?

As for that categorization thing, do you mean that a template like {{CategoryThing|Tool}} should return [[Category:Tools]]? That could be useful, but would also require a lot of work initially.

[RZR0]

Hm, not sure about that. I can't think of any cases where it would be useful to show a type and a subtype. Why not just show "Food" instead of "Item (Food)"?

Works for me

 

As for that categorization thing, do you mean that a template like {{CategoryThing|Tool}} should return [[Category:Tools]]? That could be useful, but would also require a lot of work initially.

Yup yup