Template talk:Gecko: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 21: Line 21:


:: One thing I'm unclear of would be unnecessary classification, I'd guess in some cases memory addresses are handled similarly across regions and codes work the same way across them. The current design can handle that with duplication, but we might want to alternately handle it to avoid separate edits. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 12:44, 1 January 2018 (CET)
:: One thing I'm unclear of would be unnecessary classification, I'd guess in some cases memory addresses are handled similarly across regions and codes work the same way across them. The current design can handle that with duplication, but we might want to alternately handle it to avoid separate edits. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 12:44, 1 January 2018 (CET)
Look's like Xerces was able to convert the set region inputs to be handled more generically, allowing for arbitrary inputs. Is that a satisfactory solution here, or does this need more discussion / review? [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 10:12, 3 January 2018 (CET)


== Quality Categories ==
== Quality Categories ==
If you want to turn gecko codes into a template (not a bad idea), it might be good if you're going to try and integrate quality checks to hook it into [[Template:Problems/GC Widescreen Auto]] and [[Template:Problems/GC Widescreen 16-9]]. If the game supports 16:9 already but also has widescreen codes for whatever reason, then the template should generate flags to show that the widescreen gecko codes aren't needed. That would give the template tangible benefits rather than just style compared to the current way of doing it. I don't know how to handle that with Wii though, but I don't really know how widespread the creation/desire for widescreen Wii codes is when most games already support it (I think?). - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 04:17, 30 December 2017 (CET)
If you want to turn gecko codes into a template (not a bad idea), it might be good if you're going to try and integrate quality checks to hook it into [[Template:Problems/GC Widescreen Auto]] and [[Template:Problems/GC Widescreen 16-9]]. If the game supports 16:9 already but also has widescreen codes for whatever reason, then the template should generate flags to show that the widescreen gecko codes aren't needed. That would give the template tangible benefits rather than just style compared to the current way of doing it. I don't know how to handle that with Wii though, but I don't really know how widespread the creation/desire for widescreen Wii codes is when most games already support it (I think?). - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 04:17, 30 December 2017 (CET)
:Good idea, if this new template is going to make it to game pages then we can add additional qualility checks regarding games that already support widescreen. We may like another category for whether it's used in Wii game pages. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 03:29, 31 December 2017 (CET)
:Good idea, if this new template is going to make it to game pages then we can add additional qualility checks regarding games that already support widescreen. We may like another category for whether it's used in Wii game pages. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 03:29, 31 December 2017 (CET)

Navigation menu