Template talk:Problems/GC Widescreen Auto: Difference between revisions

Template talk:Problems/GC Widescreen Auto (view source)

Revision as of 05:23, 18 November 2015

2,234 bytes added , 18 November 2015

→‎Not a Banner but Should be Something Better

Kolano

Bureaucrats, Administrators

79,225

edits

@@ Line 29: / Line 29: @@
 :*Though I don't think it applies much to this specific problem, unless folks want to add more specific details of enabling 16:9 in game, there may be shared problems that do need to allow for the insertion of game specific details. I presume when that comes up the game specific text can just be added after the related template, or in some rarer cases inserted via template parameters.
 :[[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 23:05, 17 November 2015 (CET)
 ::The problem is the use of headings in a template. You may not see it now but it can break Wikis if you use them. Trust me. I have experience with other Wikis. Sure, nothing is preventing you from doing so, but it's just asking for trouble and is generally frowned upon. Treat templates as you would C++ functions: If you change one thing in the function, everything else can break. I'm sure you have run into those kind of problems before messing with the C++ code. Also, I find this template a Band-Aid to a larger underlying problem that I hope to fix in the highly experimental [[Template:Infobox VG sandbox]]. Ultimately, I see this template, [[Template:WidescreenGCNTag]], and [[Template:DualLayerWiiDiscs]] being merged into the new infobox template. Not in the near future and in its current form, but I think it will happen. --[[User:Wildgoosespeeder|Wildgoosespeeder]] ([[User talk:Wildgoosespeeder|talk]]) 23:33, 17 November 2015 (CET)
-::: The problem this addresses is that there is shared problem text between multiple wiki pages. That's the case for a number of things. I would not put much faith that this sort of info will migrate to the infobox, even if the infobox is revised, and the other similar problem text definitely won't be addressed by that. You have still failed to explain as to how including the heading in the template can "break" anything. Don't just say to trust you (it's that sort of commentary that has really been irking the various admins here), state specifically what the problem with doing so is. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 00:01, 18 November 2015 (CET)
+:: The problem this addresses is that there is shared problem text between multiple wiki pages. That's the case for a number of things. I would not put much faith that this sort of info will migrate to the infobox, even if the infobox is revised, and the other similar problem text definitely won't be addressed by that. You have still failed to explain as to how including the heading in the template can "break" anything. Don't just say to trust you (it's that sort of commentary that has really been irking the various admins here), state specifically what the problem with doing so is. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 00:01, 18 November 2015 (CET)
-::::Click edit next to the 16:9 header on any page. Should I show you by editing and then looking at a few of the pages this template is embedded? I won't do it unless you say it is OK. --[[User:Wildgoosespeeder|Wildgoosespeeder]] ([[User talk:Wildgoosespeeder|talk]]) 00:27, 18 November 2015 (CET)
+::Click edit next to the 16:9 header on any page. Should I show you by editing and then looking at a few of the pages this template is embedded? I won't do it unless you say it is OK. --[[User:Wildgoosespeeder|Wildgoosespeeder]] ([[User talk:Wildgoosespeeder|talk]]) 00:27, 18 November 2015 (CET)
+::: There's nothing on this template that is "asking for breaks". It provides a consistent text for all applicable game pages and at least here (when looking into [[F-Zero GX]]) there's no "edit" next to the 16:9 heading added by the template, and even if there was, what is the problem here? An user adding unnecessary info in the template? A simple revert would fix that and simply protecting the template would prevent any further occurrence as well. And again, I don't care about what experience you have with whichever wiki you've worked, if you think there's a problem, show us a concrete example from our wiki exhibiting the problem, saying that something is wrong and that we need to trust you is just asking me to ignore whatever point you may have. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]])
+::::I remember the template having an edit option right from the page that calls it a short time ago. Anyways, I don't know what else to tell you. It's unconventional by Wiki standards in general, could make that boundary to edit Dolphin Wiki even harder for newcomers, and no other template you have created does this. I see a Band-Aid approach to fixing a problem here. From what I understand from various bug report threads, the idea is to stop Band-Aid or quick approaches to fix problems of the Dolphin executable and try to implement a proper, hopefully permanent, and clean fix. This was made apparent to me with a bug report relating to the flickering coming back to [[Sonic Mega Collection]] and a recent feature request that tells of a more underlying problem with the user-friendliness ({{issue|9083}}). For consistency sake, I would hope that the Wiki follows this too. --[[User:Wildgoosespeeder|Wildgoosespeeder]] ([[User talk:Wildgoosespeeder|talk]]) 02:30, 18 November 2015 (CET)
+:::::You didn't see an Edit button here at least while the templates been implemented, and I'm unclear you would have elsewhere. I'm fairly sure the edit buttons are inserted into the page before templates are processed. Though I guess who knows what wiki software variations are out there. You've been vaguely fuming at people about how this this terribly breaks things for over a week now, and in that time, if that was your real concern, never realized it was not even applicable here. Sigh.
+:::::These sorts of templates can also help standardize text used around issues that effect numerous titles, which over time has been a good number of them. If you paid attention to notes in Revision History you might also know I was able to find 2-3 other shared problems that should get this sort of treatment. That was just across a review of a few pages, so there's likely numerous others. We are unlikely to wedge details for any of these into the infobox, so that's plainly not the solution here. Sigh.
+:::::This template may make it slightly harder to edit these particular problems, but such also saves a lot of maintenance work. Without the template any time a random editor updates one of these pages someone would need to deploy revisions over all the other pages, since random editors are unlikely to know the issue exists elsewhere. Since we were frequently lax in doing so, every page's similar issue would slowly deviate from each other, creating a mess over time. Consistency is valued here, I'm not clear how anything you've raised aids such. I should really just shut up there, as I have no interest in reviewing some pointless, evidence free rant from you assuring me to the contrary. Sigh.
+:::::Please don't just point fingers with comments like "I see a Band-Aid approach to fixing a problem here." and pointless references to unrelated issue treads. You have yet to explain how this template fails to address actual issues the wiki has or how there is any better solution to those problems. And we've now filled another few pages worth of wiki with bantering to no purpose. Sigh.
+:::::This is plainly too much sighing for one response. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 04:23, 18 November 2015 (CET)
-::::: There's nothing on this template that is "asking for breaks". It provides a consistent text for all applicable game pages and at least here (when looking into [[F-Zero GX]]) there's no "edit" next to the 16:9 heading added by the template, and even if there was, what is the problem here? An user adding unnecessary info in the template? A simple revert would fix that and simply protecting the template would prevent any further occurrence as well. And again, I don't care about what experience you have with whichever wiki you've worked, if you think there's a problem, show us a concrete example from our wiki exhibiting the problem, saying that something is wrong and that we need to trust you is just asking me to ignore whatever point you may have. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]])
+:::::In current state the template is consistent (provides same text in all GC games with native support), simple (just call it and it's done) and also future-proof to me (e.g. in future Dolphin changes or rearrange its Aspect Ratio options, a simple change in the template and all applicable game pages will also have the new info). How this can be a Band-Aid if there's no issues? If I understand you correctly, {{tl|GlobalProblems}} is also a "Band-Aid" because it uses headings stored inside variables and yet we hadn't any issue with it since its implementation. Finally, I don't think we need to follow a general "wiki standard" if we already have our own that works very well for what we need. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]])
-::::::I remember the template having an edit option right from the page that calls it a short time ago. Anyways, I don't know what else to tell you. It's unconventional by Wiki standards in general, could make that boundary to edit Dolphin Wiki even harder for newcomers, and no other template you have created does this. I see a Band-Aid approach to fixing a problem here. From what I understand from various bug report threads, the idea is to stop Band-Aid or quick approaches to fix problems of the Dolphin executable and try to implement a proper, hopefully permanent, and clean fix. This was made apparent to me with a bug report relating to the flickering coming back to [[Sonic Mega Collection]] and a recent feature request that tells of a more underlying problem with the user-friendliness ({{issue|9083}}). For consistency sake, I would hope that the Wiki follows this too. --[[User:Wildgoosespeeder|Wildgoosespeeder]] ([[User talk:Wildgoosespeeder|talk]]) 02:30, 18 November 2015 (CET)
-:::::::In current state the template is consistent (provides same text in all GC games with native support), simple (just call it and it's done) and also future-proof to me (e.g. in future Dolphin changes or rearrange its Aspect Ratio options, a simple change in the template and all applicable game pages will also have the new info). How this can be a Band-Aid if there's no issues? If I understand you correctly, {{tl|GlobalProblems}} is also a "Band-Aid" because it uses headings stored inside variables and yet we hadn't any issue with it since its implementation. Finally, I don't think we need to follow a general "wiki standard" if we already have our own that works very well for what we need. - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]])
 ==Inserted Category==
 We may need a parameter or logic to allow using the template without inserting the related category, as we likely don't want it appearing on the Templates documentation for instance (this may actually apply to a few Wiki templates). I think the best way would likely be to look for "Template" in the page title and avoid outputting it if found, but I'm being too lazy to implement such now. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 23:17, 17 November 2015 (CET)
 : Isn't there a way to check from which namespace the template is being called? That could work as well but I don't know if it's possible... - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]])