15,190
edits
 |
Progress Continues
We've already had 21604 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: February, March, and April 2024 Dolphin Progress Report. |
 |
The Dolphin Emulator Wiki needs your help! Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin. |
Template talk:Testing: Difference between revisions
→##GHz to ## GHz mass edit
| (7 intermediate revisions by 3 users not shown) | |||
| Line 12: | Line 12: | ||
Well, if the user want to upload an Android test then we should require they at least know what CPU and GPU their phone have. Another possible (but a little ugly) solution would be matching CPU and GPU from a table (maybe in a sub template) with phone names to do the thing, so, in the test entry the user would just put something like this: <pre>{{testing/entry|revision=4.0-xxx|OS=Android 4.3|phone=LG G2|result=Black screen, buggy drivers|tester=AndroidUser}}</pre> | Well, if the user want to upload an Android test then we should require they at least know what CPU and GPU their phone have. Another possible (but a little ugly) solution would be matching CPU and GPU from a table (maybe in a sub template) with phone names to do the thing, so, in the test entry the user would just put something like this: <pre>{{testing/entry|revision=4.0-xxx|OS=Android 4.3|phone=LG G2|result=Black screen, buggy drivers|tester=AndroidUser}}</pre> | ||
and in the page it would be replaced by the common template (Revision=4.0-xxx, OS=Android 4.3, CPU=Krait 400 Quad Core @ 2. | and in the page it would be replaced by the common template (Revision=4.0-xxx, OS=Android 4.3, CPU=Krait 400 Quad Core @ 2.26 GHz, GPU=Adreno 330). The main issue with this approach would be the big nightmares we would get, like maintaining the list updated with all of Android phones available, not to mention having a lot of entries for the same phone in the sub template table (Samsung Galaxies for example, flagship models get at least a Qualcomm variant and an Exynos variant in most cases) [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) | ||
---- | ---- | ||
| Line 30: | Line 30: | ||
|{{revision|4.0-3423}} | |{{revision|4.0-3423}} | ||
|Windows 10 | |Windows 10 | ||
|Intel Core i7-3630QM @ 2. | |Intel Core i7-3630QM @ 2.4 GHz | ||
|NVIDIA GeForce GT 635M | |NVIDIA GeForce GT 635M | ||
|Great | |Great | ||
| Line 43: | Line 43: | ||
|{{revision|4.0-7423}} | |{{revision|4.0-7423}} | ||
|Windows 8.1 | |Windows 8.1 | ||
|Intel Core i5-5200U @ 2. | |Intel Core i5-5200U @ 2.2 GHz | ||
|NVIDIA GeForce GT 920M | |NVIDIA GeForce GT 920M | ||
|Great | |Great | ||
| Line 75: | Line 75: | ||
Lately, while reviewing existing testing entries, the way we currently format the CPU speed is bothering me. AFAICT we're one of the few places that "glues" the measurement unit to the number (2GHz, 3.4GHz, etc.), while everywhere else has them separated (datasheets from Intel and AMD, tech sites and so on), and I'm strongly inclined on using the MassEditRegex extension to "unglue" them here too (2 GHz, 3.4 GHz, etc.). Any thoughts, considerations or remarks about that change? | Lately, while reviewing existing testing entries, the way we currently format the CPU speed is bothering me. AFAICT we're one of the few places that "glues" the measurement unit to the number (2GHz, 3.4GHz, etc.), while everywhere else has them separated (datasheets from Intel and AMD, tech sites and so on), and I'm strongly inclined on using the MassEditRegex extension to "unglue" them here too (2 GHz, 3.4 GHz, etc.). Any thoughts, considerations or remarks about that change? | ||
:Alternatively we might want to add more quality checks into the template. Then gauge from there whether we need to resort to regex for mass editing or not. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 06:34, 4 February 2022 (CET) | :Alternatively we might want to add more quality checks into the template. Then gauge from there whether we need to resort to regex for mass editing or not. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 06:34, 4 February 2022 (CET) | ||
:: Though I may have missed a few I had been revising them to be without spaces to maintain consistency. If we want to revise them all that's fine, but we hadn't wanted to attempt to previously as it was before having the mass edit add-on. | :: Though I may have missed a few I had been revising them to be without spaces to maintain consistency. If we want to revise them all that's fine, but we hadn't wanted to attempt to previously as it was before having the mass edit add-on. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 00:17, 5 February 2022 (CET) | ||
::: So, you both are OK in doing the mass edit? Asking one last time before proceeding because reverting the mass edits can potentially be a PITA if we ever need to for whatever reason. [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 04:23, 5 February 2022 (CET) | |||
:::: I don't have a preference. If the regex was written from a paranoid user I don't see why it will fail. [[User:Lucario|Lucario]] ([[User talk:Lucario|talk]]) 12:46, 5 February 2022 (CET) | |||
:::: Yeah, go ahead. I think the older mass edit tool used to provide better review / revert functionality. 🤷 [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 21:26, 5 February 2022 (CET) | |||
::::: I pulled the trigger, seem it went fine (toggle bot edits on the recent pages to see). <s>I'm not sure if the mass edit went through all [[:Category:Wii games]], though, it always finished after editing 1000 pages and we have a bit more than that. Will check this later.</s> '''Edit:''' I've splitted the table from [[Wii]] in two halfs and did the mass edit by specifying the page names directly instead of asking to get everything from a specific category, so I'm 100% sure now it went through all pages - [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 23:54, 5 February 2022 (CET) | |||