Difference between revisions of "User talk:Seb26"
Discordance (talk | contribs) m (→Dictionary) |
Discordance (talk | contribs) (→Dictionary) |
||
| Line 40: | Line 40: | ||
Hi, Cruelcow has been telling me about the wikis performance issues and the new dictionary template you added. [[Template:Item price]] style templates need to be done away with as fast as you can, displaying all n values on a page would take switching n! which can be a huge number, compared to something like dictionary which can display all values by switching at most n_Keys*n. The dictionary template is setup in a similar fashion to metadata I manage on a different wiki, but I'm not sure why you are keeping all the values in the same template still. Editing a single high use template whenever a new item comes out is only going to cause mass disruption. I would suggest instead storing metadata for a single item at a single location, this way when a new item is added no edits to high use templates are required. For example data for the [[Scattergun]] could be stored at [[Data:Scattergun]]. I store all metadata in a switch at that location but using your dictionary bot you could automatically fill data to [[Data:Scattergun/name/en]] which is trivial for a template to look up. You would lose the advantage of being able to edit all item names on a single page but I dare say those pages are too big, grouping all information about an item to a single page is an advantage in itself, and mitigating disruption when adding new items is a serious advantage. [[User:Discordance|Discordance]] 02:22, 20 March 2011 (UTC) | Hi, Cruelcow has been telling me about the wikis performance issues and the new dictionary template you added. [[Template:Item price]] style templates need to be done away with as fast as you can, displaying all n values on a page would take switching n! which can be a huge number, compared to something like dictionary which can display all values by switching at most n_Keys*n. The dictionary template is setup in a similar fashion to metadata I manage on a different wiki, but I'm not sure why you are keeping all the values in the same template still. Editing a single high use template whenever a new item comes out is only going to cause mass disruption. I would suggest instead storing metadata for a single item at a single location, this way when a new item is added no edits to high use templates are required. For example data for the [[Scattergun]] could be stored at [[Data:Scattergun]]. I store all metadata in a switch at that location but using your dictionary bot you could automatically fill data to [[Data:Scattergun/name/en]] which is trivial for a template to look up. You would lose the advantage of being able to edit all item names on a single page but I dare say those pages are too big, grouping all information about an item to a single page is an advantage in itself, and mitigating disruption when adding new items is a serious advantage. [[User:Discordance|Discordance]] 02:22, 20 March 2011 (UTC) | ||
| + | :Ah whoops, pilk just pointed out that the template is not transcluded either, so performance would be identical. Editing wise though I think my structure is far easier to deal with an edit but thats a matter of taste I suppose. [[User:Discordance|Discordance]] 02:32, 20 March 2011 (UTC) | ||
Revision as of 02:32, 20 March 2011
Contents
Hero's Hachimaki image
I highly disagree that the second image is better than the first, the low resolution textures on the Soldier's head are very noticeable, the resolution on the original does not matter as it's sized down to 250px anyway. The image uploaded is the one found on Homefront's store page, and the image that Valve choose to illustrate the Hero's Hachimaki with, so why is it not good enough for us? – Smashman (talk) 20:44, 1 March 2011 (UTC)
- If it's scaled down to 250px then the lower quality textures won't be that noticeable (and they aren't anyway). The original isn't bad, but nVis' is a lot better because it actually shows the hat. seb26 20:49, 1 March 2011
- The image is screwed up now, how do you plan to solve this now that we can't revert it? Corkscrew 12:44, 5 March 2011 (UTC)
Delete image
Can you delete http://wiki.teamfortress.com/wiki/File:Item_icon_Emperor%27s_Assortment.png it is a duplicate of http://wiki.teamfortress.com/wiki/File:Item_icon_The_Emperor%27s_Assortment.png KillerKooK 21:53, 13 March 2011 (UTC)
Done. seb26 21:54, 13 March 2011 (UTC)
Appreciate it.
Thanks for the advice Pierow 06:31, 16 March 2011 (UTC)
Yes
Though that account is associated with my real name, and I keep this gaming identity separate. I probably shouldn't even have mentioned it. Pez 21:16, 18 March 2011 (UTC)
Would like to know which pages use different capitalisation
With the help of Godlike, we quashed any instance of lower case item names being called to the {{Item icon}} template. At this point the last bit to check for is instances where they call "baTTER's helMET" etc. I attempted to do it but managed to break localization of the {{item name}} template (does it actually work?). I'm sure I had more but I'm tired and will see you tomorrow anyway. -- Pilk (talk) 13:54, 19 March 2011 (UTC)
Dictionary
Hi, Cruelcow has been telling me about the wikis performance issues and the new dictionary template you added. Template:Item price style templates need to be done away with as fast as you can, displaying all n values on a page would take switching n! which can be a huge number, compared to something like dictionary which can display all values by switching at most n_Keys*n. The dictionary template is setup in a similar fashion to metadata I manage on a different wiki, but I'm not sure why you are keeping all the values in the same template still. Editing a single high use template whenever a new item comes out is only going to cause mass disruption. I would suggest instead storing metadata for a single item at a single location, this way when a new item is added no edits to high use templates are required. For example data for the Scattergun could be stored at Data:Scattergun. I store all metadata in a switch at that location but using your dictionary bot you could automatically fill data to Data:Scattergun/name/en which is trivial for a template to look up. You would lose the advantage of being able to edit all item names on a single page but I dare say those pages are too big, grouping all information about an item to a single page is an advantage in itself, and mitigating disruption when adding new items is a serious advantage. Discordance 02:22, 20 March 2011 (UTC)
- Ah whoops, pilk just pointed out that the template is not transcluded either, so performance would be identical. Editing wise though I think my structure is far easier to deal with an edit but thats a matter of taste I suppose. Discordance 02:32, 20 March 2011 (UTC)
