Template talk:Button

How come the R button on the Nintendo 64 controller has an image, but the L button does not?

Oh, and why are the X and Y buttons on the Gamecube controller different sizes?

09:09, 2 April 2011 (EDT)
 * Because I didn't find the L button anywhere (it should be game rip). All buttons have the same height (16 pixels), that's why it looks so weird.

♥ I love your template! ♥
it works so well! I use it for the microgames mostly. I'd give it...[drumroll]
 * ★★★★★ five stars!!!

SNES Buttons
The, , and  pictures look a little strange. I know they're ripped from Super Mario World 2: Yoshi's Island, but I think we should use something else, like the default ones with Japan colors. If anyone agrees with me, I can upload them.

I think they have to be a game rip, but I don't know.

A lot of them do look like game rips, but the NES, Gameboy and Gameboy Color clearly aren't. The other game rips don't appear to look as odd as these 4, so it wouldn't be a problem to upload new versions of them.

Do it then.

Wait a minute
Why did you remove all the system categories? I think they looked quite nice rather than the same generic button button. It also makes it easier to tell what system a game is on in an article.--
 * Yeah i'm a little confused with the giant change

I didn't like how the buttons looked like on article pages, they were very distracting from the text.
 * Why did you remove so many of them

You didn't like how the buttons looked like on article pages. See, that's the problem. You're disregarding what other peoples' opinions are and thinking about your own.--
 * Shouldn't you have made a talk page proposal or asked an admin

All I have changed is the appearance of the buttons, nothing more, nothing less. This doesn't need a proposal. Conanshinichi didn't make a proposal when changing some buttons, I didn't do it as well. If you need to specify the system, do so in the article.
 * Actually i talked to an admin and it does require a proposal to make that drastic of a change
 * Completely changing the entire layout of the buttons like this would require some sort of talk page consensus since it changes almost everything about the way the template works, as far as I can tell.

No it doesn't. This isn't even a big change: it's just how the buttons look like. It was never a problem before, why is it a problem right now?
 * Because you completly overhauled the look of the template and removed a large number of buttons with out anybody elses opinions
 * Removed a large amount of buttons? I haven't removed even a single one. Can you provide examples?
 * From you edit summery "reworking the template, got rid of the most buttons, it will take forever to fix the buttons on 1000+ articles"
 * By "buttons" I mean, uh, forget, that was a typo.
 * Also you removed a large amount of console specific buttons and i disagree with doing that i think it looks better if you use the console buttons rather than a generic button
 * See UM's post above. Your argument is invalid.
 * Uh, my post was directed at you... "I didn't like how the buttons looked like on article pages, they were very distracting from the text." This is what proposals are for, Watson. To resolve an argument by seeing which side gets the most opinions. But no, instead, you just think about what you want, rather than thinking about the opinions of others and reaching an agreement.--
 * Basically, to sum my above post up, you're pretty much like this: "Screw the opinions of others, I'll do what I want.".--
 * What exactly you don't like in this change?
 * "I think they looked quite nice rather than the same generic button. It also makes it easier to tell what system a game is on in an article."--

"they (buttons) were very distracting from the text." That's the whole point of the change. "If you need to specify the system, do so in the article."
 * "I think they looked quite nice rather than the same generic button."
 * "It also makes it easier to tell what system a game is on in an article."

Notice the bolded I? "But no, instead, you just think about what you want, rather than thinking about the opinions of others and reaching an agreement."

^ Completely disregarding--
 * This discussion goes nowhere. I think I should start a traditional talk page proposal then.
 * Exactly my point, which you also ignored. :S.--

Proposal
I'm proposing to change all of the buttons appearance to how it is on the current Default buttons. The reason behind this is: the appearance of the current buttons is very distracting from the text. The first thing that gets into eye when reading a paragraph is the button, not the text. But the button needs to be highlighted somehow, otherwise it's hard to search for the particular button in the article, that's why this template exist. The redundant number of colors is not needed for that.

You can see the changes in my sandbox.

Proposer: Deadline: February 15, 2012, 23:59 GMT.

Support

 * 1) Per proposal.

Oppose
User: *viewing Super Mario Bros. article with the colorless button changes* User: What the?! That doesn't look like the NES' A button at all!
 * 1) I think it looks better the way it is now
 * 2) Well, elaborate on "distracting". If we want to be a MarioWiki, we have to be true to the franchise; meaning that the colored buttons are official, however, your dull, colorless buttons are unofficial, and as such, they wouldn't really be allowed anyway without being official. For example, look at the way Nintendo inputs their buttons in Mario Party 6; See? They colored the buttons in this screenshot and they're shaped different too, indicating that they're GameCube buttons. It would be much less complex for the reader to determine what system the game is on the perspective article they're reading without having to go all the way back up to the top of the header and reading the system. These colored buttons help us to know much easier. What I'm bascially stating is that these colored buttons are a nifty, unique way to automatically inform the reader of what controller's buttons they're reading about. Colored buttons are very easy to distinguish, which basically will automatically notify the reader of the controller the article is talking about. Colorless buttons blend right in with the article's text, which would make it much more of a hassle to recognize the controller's button input. Here's an example of what I mean: