Difference between revisions of "User:Seb26/Item infobox"
(→Ideas) |
|||
| Line 10: | Line 10: | ||
** Attributes: | ** Attributes: | ||
*** Should be plainly named | *** Should be plainly named | ||
| − | **** {{xt|1={{code|trade}}}} over {{!xt|1={{code|tradable}}}} | + | **** {{xt|1={{code|trade}}}} over {{!xt|1={{code|tradable}}}} |
*** Simple yes/no ('''Issue''') | *** Simple yes/no ('''Issue''') | ||
**** Sometimes this isn't possible, need way to handle these | **** Sometimes this isn't possible, need way to handle these | ||
| Line 24: | Line 24: | ||
** Generate lists and distribute workload | ** Generate lists and distribute workload | ||
* AWB find & replace in-template call | * AWB find & replace in-template call | ||
| − | |||
| − | |||
| − | |||
Revision as of 05:36, 22 October 2010
Ideas
- Item infobox only. Class, maps, websites should be separate.
- Sole important parameter:
type- Determines type (
weapon,hat,misc,taunt,tool,action) - Switches visible fields based on its value
- Determines type (
- Scattered ideas:
- Translations should be defined directly inside the infobox
- No
| weapon-slot = Primärwaffen - Instead:
| slot = primarywhich on German pages generatesPrimärwaffen
- No
- Attributes:
- Should be plainly named
tradeovertradable
- Simple yes/no (Issue)
- Sometimes this isn't possible, need way to handle these
- Possibly "if value != yes/no, display value" (may create issues with translators who translate "yes" and "no")
- Sometimes this isn't possible, need way to handle these
- Should be plainly named
- Translations should be defined directly inside the infobox
Core ideas
- Efficient & translator friendly
- Well-documented – both on template page & on Help:Language translation
Implementation
- Research
- Definite numbers on how many pages to update
- Generate lists and distribute workload
- AWB find & replace in-template call
