Talk:Super Smash Bros. Melee/sandbox

WIP: AR codes section

So, this is a WIP of a tabbed approach to the AR codes, mainly to make pages with huge codes and multiple regions less crowded. Its formatting isn't too good yet but the concept is there (e.g. I wanted to have another set of tabs inside the NTSC tab to handle different ISO revisions but I didn't fully understood how to nest things yet). On to-do list is also limiting the height of huge multiline codes (I plan in limiting to 5 lines, then scrolling codes bigger than that). What do you guys think? Anything you want me to take into consideration? - mbc07 (talk) 00:14, 11 May 2016 (CEST)

Seems like tab is a silly addon... Personally I wasn't bothered over the fact that page is getting crowded. It's either split or deal with it. I wouldn't even mind to see the "Expand" button on top right corner of test case table to go. I'm not fan of having to click more and it's not good for browser's 'find in page' function. Lucario (talk) 00:49, 11 May 2016 (CEST)

How is the new game article layout?

Some could be refined more. I like how the new "Compatibility" section can cover three sections the old layout has and it can reduce lot of writing. Lucario (talk) 04:38, 17 August 2019 (CEST)

Sorry if this sounds harsh, but it's still a big NOPE for me. In fact, the whole page looks so messy right now that I don't think there's anything currently "worthy" of being deployed outside of this sandbox. - mbc07 (talk) 05:07, 17 August 2019 (CEST)

I think Compatibility as a replacement makes sense on paper, but it's pretty jumbled in practice. Right now, pretty much by accident (after many years of bickering and minor tweaks), we've ended up with a format for game pages that's really easy to read and get exactly what you want from it, with perfect topic splits. I like it a lot the way it is, even the concession for widescreen/60fps codes is perfect.

I think Template:Gecko is the best idea so far and I think it's ready to be deployed, I'll give it a run through in notepad++ again soon. The reasons for the template, as far as I can tell, are: a) ability to address all the codes sections at once without a regex, b) generating useful categories for what pages are missing 60fps/widescreen codes and what games require codes to function (all other codes?), and c) just the nicety of using an actual template, which might be more user friendly. The only thing I know that's really "wrong" with it is that the region sorting by ID doesn't work because game IDs are garbage, it needs to be done more manually. (Though for the record I've never once used a code and I don't know much about them, e.g. the difference between Gecko, AR, and the "dword" codes).

Sorta related: I think the "best" change possible right now would be some kind of split in console accurate config (native res, no AA etc) and enhancement config templates. And even that doesn't really matter because all you have to do is just read the config change to know what the problem is that it's solving, though maybe it's better for less technically proficient users. It's kind of in the air at the moment (afaik) what to do about whether or not enhancement problems should actually be in the config template. - Xerxes (talk) 06:19, 17 August 2019 (CEST)