Template talk:Item/view/tablerow

Image Size

By appending |frameless|96x192px to the end of the [[File:{{{Image}}}]], everything that is outside of those dimensions is scaled down. Items that are smaller like Amulets, Rings and Maps retain their original size, which is fine because they already don't take up a lot of space. Slightly larger but still small items like Daggers and Wands are only slightly reduced in no size but they take up no more pixels than the larger Shields or Two Handed Maces so that's ok, imo. It's not exactly meant to be a permanent solution, though if people think it's ok then I'm fine with it too. It certainly beats the endless scrolling that the newer, higher res images create! If anyone needs to, take a look at the Full Unique Index to get a good grasp on how the 96x192px affects different size images.--FaceLicker (talk) 22:55, 18 April 2013 (UTC)

I have an idea for a better solution, but no time to work on it currently. This will do fine for now. —Vinifera7 (talk) 22:58, 18 April 2013 (UTC)

Capitalisation?

This template is still a template in it's own right, it just happens to be a subtemplate/page of Item. Shouldn't we keep it consistent with the normal capitalisation used for template names? -AnnanFay (talk) 13:07, 28 May 2013 (UTC)

Hmm... I'm sure there was a reason for renaming the page when I did it, but now I can't think of what it was. —Vinifera7 (talk) 16:09, 28 May 2013 (UTC)

I remember now! If, for example, you type "template:item" into the URL or the search bar, it will properly locate "Template:Item" (capital T, capital I). It's the same with template transclusion; if you type "{{item table header}}", it will rightly locate "Template:Item table header". You see? Only the first letter gets automatically converted to capital. However with subpages, if you type "template:item/tablerow", it won't locate "Template:Item/Tablerow". Instead, it will go to "Template:Item/tablerow". Understand my reasoning now? This way people don't have to remember specific capitalisation; they can just type in lowercase and let the wiki software do the work. —Vinifera7 (talk) 06:25, 29 May 2013 (UTC)

In my opinion relying on auto-correction is generally a bad idea though your argument makes some sense.

It is good to use an easy to read convention for templates so code is easier to read. Versionhistorytable is relatively hard to read because it forces you to read letter-by-letter rather than in word chunks. The wiki forces us to have the start letter capitalised and underscores are the same as spaces. So the other options are: VersionHistoryTable, Version history table, Version History Table (currently there are templates using each of these conventions)

The main thing is that all template names are consistent. Do you know if there is an easy way to batch rename templates and references to them? -AnnanFay (talk) 14:24, 29 May 2013 (UTC)

No I don't. I have one other thing to add about the capitalisation of subpages: If you take a sampling of subpages in the Template namespace on Wikipedia, you will find that all of them have lowercase letters following the slash. If you are after consistency in general, I recommend using all lowercase letters, except for the first, which is forced by the wiki software to be uppercase. Then, "VersionHistoryTable" can be renamed to "Version history table", for instance. —Vinifera7 (talk) 14:43, 29 May 2013 (UTC)