Project:General Discussions: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 25: Line 25:
:::::::::By the way, I've read your and Jhonn's comment in other discussion pages (and I'm still catching up). That null rating system that you've mentioned there. I bet the admin won't even be able to batch replace all the problem subsections to include the null rating system. What's the regex code? Yes, you may have guessed correctly, a simple regex code probably will replace ALL the subsections literally everywhere outside the problem section by accident! However I have an idea that maybe everyone will be happy with: a label with bold red "Critical!" text that comes in before the summary of the problem, possibly in the same line. It doesn't require us to batch replace the null rating system to all the game pages and will not clutter up at all if implemented correctly. What about it? It's a lot more efficient solution. But still not feeling like it though. We're not sure which problem to label with. Why don't we just let the reader read the context of the problem or head over to the issue report if they want to determine how bad is the problem? Also I've said other time (forgot where it is in this Wiki) that we can always use the game's compatibility rating system for the problem overall. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 04:19, 7 November 2015 (CET)
:::::::::By the way, I've read your and Jhonn's comment in other discussion pages (and I'm still catching up). That null rating system that you've mentioned there. I bet the admin won't even be able to batch replace all the problem subsections to include the null rating system. What's the regex code? Yes, you may have guessed correctly, a simple regex code probably will replace ALL the subsections literally everywhere outside the problem section by accident! However I have an idea that maybe everyone will be happy with: a label with bold red "Critical!" text that comes in before the summary of the problem, possibly in the same line. It doesn't require us to batch replace the null rating system to all the game pages and will not clutter up at all if implemented correctly. What about it? It's a lot more efficient solution. But still not feeling like it though. We're not sure which problem to label with. Why don't we just let the reader read the context of the problem or head over to the issue report if they want to determine how bad is the problem? Also I've said other time (forgot where it is in this Wiki) that we can always use the game's compatibility rating system for the problem overall. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 04:19, 7 November 2015 (CET)
::::::::::Another good point. Doing a regex to get all level 3 titles isn't that hard, but it would also catch a lot of false positives (like global problems, enhancements, etc). And about the red thing before the title, also unnecessary from my point of view. Critical problems still are the top-most entries in the problems section in almost all cases (to make the visitor quickly find the most common problems). Putting a red, bold label will just serve to draw unnecessary attention since in most cases that info already is the top-most entry in problems section. We would also get into the "what should be marked as critical" discussion, with potential edit-wars. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]])
::::::::::Another good point. Doing a regex to get all level 3 titles isn't that hard, but it would also catch a lot of false positives (like global problems, enhancements, etc). And about the red thing before the title, also unnecessary from my point of view. Critical problems still are the top-most entries in the problems section in almost all cases (to make the visitor quickly find the most common problems). Putting a red, bold label will just serve to draw unnecessary attention since in most cases that info already is the top-most entry in problems section. We would also get into the "what should be marked as critical" discussion, with potential edit-wars. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]])
:::::::::::I've completely forgotten about the problem listing priority. Thanks for pointing that out! [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 05:17, 7 November 2015 (CET)
::::::::::We kind of do. ''It's like you're trying to shove the details of the emulation problem into there.'' Is that any different than including developer, publisher, series, release date, etc. into the infobox? The only Dolphin-specific useful parameters of the current infobox are the compatibility rating and Dolphin forum link. The 16:9 and dual-layer banners are emulator-specific things.
::::::::::We kind of do. ''It's like you're trying to shove the details of the emulation problem into there.'' Is that any different than including developer, publisher, series, release date, etc. into the infobox? The only Dolphin-specific useful parameters of the current infobox are the compatibility rating and Dolphin forum link. The 16:9 and dual-layer banners are emulator-specific things.
::::::::::I was thinking infobox initially to put MD5 checksums but how to make it look presentable? I mean SSBB has two MD5 good dump checksums due to a small change made. It would make more sense to create a table further down the page. I already have an idea how to construct the table. Stay tuned.
::::::::::I was thinking infobox initially to put MD5 checksums but how to make it look presentable? I mean SSBB has two MD5 good dump checksums due to a small change made. It would make more sense to create a table further down the page. I already have an idea how to construct the table. Stay tuned.
6,576

edits