15,189
edits
 |
Progress Continues
We've already had 21543 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
no edit summary
No edit summary |
|||
| Line 23: | Line 23: | ||
::We now have one, from a video of 4 Swords on Android, but that's from ~2.5 years ago. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 13:41, 2 December 2015 (CET) | ::We now have one, from a video of 4 Swords on Android, but that's from ~2.5 years ago. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 13:41, 2 December 2015 (CET) | ||
:::I think I found a way to account for Android test entries, what about adding a new <code>device=</code> parameter to {{tl|Testing/entry}} that get the device model (in the common format <brand> <series> <model> and if necessary <variant> -- but only if that specific variant ships with a different SoC)? When specifying a device this entry would span across CPU and GPU columns (to prevent breaking current table), solving the issue of different phones with the same SoC performing different while maintaining simple for the user (which will need to know only his phone model). Also, a tech-savvy reader could quickly search for the phone model if he wants to know that CPU/GPU that specific device has. I didn't code a sandbox but that's what I mean: | :::I think I found a way to account for Android test entries, what about adding a new <code>device=</code> parameter to {{tl|Testing/entry}} that get the device model (in the common format <brand> <series> <model> and if necessary <variant> -- but only if that specific variant ships with a different SoC)? When specifying a device this entry would span across CPU and GPU columns (to prevent breaking current table), solving the issue of different phones with the same SoC performing different while maintaining simple for the user (which will need to know only his phone model). Also, a tech-savvy reader could quickly search for the phone model if he wants to know that CPU/GPU that specific device has. I didn't code a sandbox but that's what I mean: | ||
:::{|class="wikitable sortable mw-collapsible" style="font-size:90%" | :::{|class="testresults wikitable sortable mw-collapsible mw-collapsed" style="font-size:90%" | ||
! colspan="6" | Test Entries | ! colspan="6" | Test Entries | ||
|- | |- | ||
| Line 64: | Line 64: | ||
::::I'm not sure this will work out. Try using the "Collapse" button, it seems to cause the full table to disappear now. Didn't investigate further to try to see why. Perhaps you just missed pulling in one of the relevant classes here, but I'm not sure. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 18:54, 6 December 2015 (CET) | ::::I'm not sure this will work out. Try using the "Collapse" button, it seems to cause the full table to disappear now. Didn't investigate further to try to see why. Perhaps you just missed pulling in one of the relevant classes here, but I'm not sure. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 18:54, 6 December 2015 (CET) | ||
:::::When implemented it'll work fine without breaking any functionality we currently have, this table from the example I put above isn't actually calling {{tl|Testing/entry}} <s>and I was too lazy to actually check and include all required classes</s> (fixed, should mimic {{tl|Testing}} correctly now). I want to hear about possible points you may have in favour/against of this approach before moving further (and if possible, address possible complaints)... - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) 19:23, 6 December 2015 (CET) | |||