Difference between revisions of "User:Seb26/Item infobox"

From Team Fortress Wiki
Jump to: navigation, search
(Ideas)
Line 14: Line 14:
 
**** Sometimes this isn't possible, need way to handle these
 
**** 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")
 
***** 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 ===
 
=== Core ideas ===

Revision as of 10:42, 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
  • Scattered ideas:
    • Translations should be defined directly inside the infobox
    • Attributes:
      • Should be plainly named
        • trade over 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:
      • name instead of hat-name-override

Core ideas

Implementation

  • Research
    • Definite numbers on how many pages to update
    • Generate lists and distribute workload
  • AWB find & replace in-template call