Difference between revisions of "User:Seb26/Item infobox"
(Created page with '== Ideas == * Item infobox only. Class, maps, websites should be separate. * Sole important parameter: {{code|type}} ** Determines type ({{code|weapon}}, {{code|hat}}, {{code|mis…') |
(→Implementation) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
*** Instead: {{xt|1={{code|1={{!}} slot = primary}}}} which on German pages generates {{xt|1={{code|1=[[Primary/de|Primärwaffen]]}}}} | *** Instead: {{xt|1={{code|1={{!}} slot = primary}}}} which on German pages generates {{xt|1={{code|1=[[Primary/de|Primärwaffen]]}}}} | ||
** Attributes: | ** Attributes: | ||
| − | *** | + | *** Should be plainly named |
| + | **** {{xt|1={{code|trade}}}} over {{!xt|1={{code|tradable}}}} | ||
| + | *** 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") | ||
| + | ** Param names should not be long & hard to remember: | ||
| + | *** {{xt|1={{code|name}}}} instead of {{!xt|1={{code|hat-name-override}}}} | ||
| − | == | + | === 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 | ||
| + | |||
| + | === Plan 1 === | ||
| + | * Deploy to {{tl|Item infobox}}. All other infoboxes remain as they are. | ||
| + | * Parse through all pages using older infoboxes, change template to {{tl|Item infobox}} and replace code & old parameters. | ||
Latest revision as of 01:55, 30 October 2010
Contents
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
- Param names should not be long & hard to remember:
nameinstead ofhat-name-override
- 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
Plan 1
- Deploy to
{{Item infobox}}. All other infoboxes remain as they are. - Parse through all pages using older infoboxes, change template to
{{Item infobox}}and replace code & old parameters.
