Forum:Consistency and revamp to Graphical Updates

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > Consistency and revamp to Graphical Updates
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 13 May 2012 by Urbancowgurl777.

Our graphical updates subpages are fairly inconsistent and a mess to edit. I propose we use a template to create the table header and rows, making it easier to add new entries, as well as to read the entries. This template also ensures the size of the images is consistent, preventing the need to "pop" the table out, which is really quite a pain for viewers, especially with such long tables.

The template, currently located at User:Hofmic/Sandbox2, simply asks for the name of the two images (and they can be excluded, causing the template to create blank cells) and the names of the new and old images (without "File:" prepended). To ensure consistent formatting, when multiple updates occur to the same subject, they'll get multiple cells on the table.

As with most of my content proposals, I'll handle the conversion to the template if this thread passes.

Updated: As per Ben below, as well as mentions in [[Special:Chat]], the pages are also very long and thus very laggy. I'd like to split them. As per Ben, the easiest way to do so, when possible, is to categorize with subcategories such as splitting the gnome images, etc.


This is the first two rows of Graphical updates/Items created with my template:

{{User:Hofmic/Sandbox}} {{User:Hofmic/Sandbox2 |image1name = Strange box |image2name = Dragon scimitar |image1old = Strange Box Old.png |image1new = Strange Box.gif |image2old = D scim.png |image2new = Dragon scimitar detail.png |image2small = 1 }} {{User:Hofmic/Sandbox2 |image1name = Dragon longsword |image2name = Rune longsword |image1old = Dragonlong.png |image1new = Dragon longsword detail.png |image2old = Runelongsword.png |image2new = Rune longsword detail.png |image2small = 1 }} |}

The code used to make that is:

|image1name = Strange box
|image2name = Dragon scimitar
|image1old  = Strange Box Old.png
|image1new  = Strange Box.gif
|image2old  = D scim.png
|image2new  = Dragon scimitar detail.png
|image2small = 1
|image1name = Dragon longsword
|image2name = Rune longsword
|image1old  = Dragonlong.png
|image1new  = Dragon longsword detail.png
|image2old  = Runelongsword.png
|image2new  = Rune longsword detail.png
|image2small = 1

While the code the page currently uses is:

<div style="padding:0 25px 0 25px;">
{|class="wikitable" style="width:100%; text-align:center; white-space:nowrap;"
![[Strange box]]
![[Dragon scimitar]]
|[[File:Strange Box Old.png|125px|Strange box (before)]]{{right}}[[File:Strange Box.gif|125px|Strange box (after)]]
|[[File:D scim.png|Dragon scimitar (older)]]{{right}}[[File:D scim big.png|Dragon scimitar (old)]]{{right}}[[File:Dragon scimitar detail.png|150px|Dragon scimitar (current)]]
![[Dragon longsword]]
![[Rune longsword]]
|[[File:Dragonlong.png|100px|Dragon longsword (before)]]{{right}}[[File:Dragon longsword detail.png|80px|Dragon longsword (after)]]
|[[File:Runelongsword.png|Rune longsword (before)]]{{right}}[[File:Rune longsword detail.png|100px|Rune longsword (after)]]


Support - As nominator. Hofmic Talk 20:49, April 28, 2012 (UTC)

Support - Hopefully, it will be easier to find images and to AWB... currently, it makes me flip out. Hair 20:51, April 28, 2012 (UTC)

Comment - Well, I think it does look bad to have the images 125px no matter what. The stretched old images would look ugly. Images like File:Ogbody old.png or File:Philop old.png with that size would look terrible. JOEYTJE50TALKpull my finger 20:53, April 28, 2012 (UTC)

I seriously question if we should even keep such an image, as they're far too rediculously small to even really make out, but I could add an override if the image is smaller than 125px. Hofmic Talk 20:55, April 28, 2012 (UTC)
Done. The image1small and image2small parameters will, if true, cause the image to show at a size smaller than 125px, instead of being scaled larger. The example above utilizes this new parameter. Hofmic Talk 21:11, April 28, 2012 (UTC)

Conditional support - What about images that aren't images but archived files? (i.e., to take a random image) Also, will that mean that we'd have to change ALL current entries? And I think the size should be adjusted per subpage, i.e. 125px is too small for GU/Locations. But aside from that, it seems like a very good idea. What exactly are these inconsistencies in current code, though? User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 06:38, April 29, 2012 (UTC)

Images that are a direct link into the file history of another file will have to be saved as a new image (really, why aren't they in the first place?). Yes, 125px is small, but is the largest the file can be fitting it in the tiny work area wikia gives us. The advantages of the small size is that the numerous images on the page load faster, the size of the images is consistent (provided that the images are at least 125px wide), which looks better in the large tables, and ensuring that there is two images side by side, on the same line, including the arrow, is more aesthetically pleasing than cases where the images are on separate lines, etc. Yes, it's rather small for locations, but you can expand the image by clicking on it, if you care about that specific image (in the Wikia skin, which the majority of users use, this is opens in a lightbox instead of having to open the file page). The main advantage of the small size is that the Wikia skin majority isn't stuck with the horrendous pop out table, while still functioning for the monobook users. As for the consistency comment, it's mostly referring to the differing sizes of images and the way many don't even appear on the same line as each other (so we have an old image, an arrow, then way below it is the new image; looks terrible). Hofmic Talk 06:50, April 29, 2012 (UTC)
OK. On a side note, we should take the direct links and make images of them first before implementing this. (I don't want to do that, btw... :P) User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 10:04, April 30, 2012 (UTC)

Support - Graphical updates is a mess! I hate how the updates "Stretch" off the page. We could also create more subpages for some Races, so for example Gnomes would have their own page due to how many updated Gnomes there have been. Adventurer's log Wahisietel (Talk) Quest map icon.png 11:25, April 30, 2012 (UTC)

Support - This seems particularly beneficial. Matt (t) 04:07, May 2, 2012 (UTC)

Comment - Will this apply to GU/Chatheads too? They mustn't be resized and the page is fine as it is already. User_talk:Fswe1 Fswe1 Brassica Prime symbol.png 11:41, May 4, 2012 (UTC)

Seeing as it stretches off the page, yes. Adventurer's log Wahisietel (Talk) Quest map icon.png 12:51, May 4, 2012 (UTC)

Closed - There is consensus for Hofmic to go ahead and make these changes. sssSp7p.pngIjLCqFF.png 06:25, May 13, 2012 (UTC)