 |
Progress Continues
We've already had 21646 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/entry: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 20: | Line 20: | ||
It looks like you did capture some of the mobile CPU/GPU stuff. This also seems fine, though I also have a bad feeling many folks will have no idea what CPU/GPU are in their phones and we'll be cleaning stuff up a lot. I guess that would be dependent on actually getting some Android test results though. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 15:24, 17 November 2015 (CET) | It looks like you did capture some of the mobile CPU/GPU stuff. This also seems fine, though I also have a bad feeling many folks will have no idea what CPU/GPU are in their phones and we'll be cleaning stuff up a lot. I guess that would be dependent on actually getting some Android test results though. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 15:24, 17 November 2015 (CET) | ||
: I won't work on this for a while, just realized some other issues we'll certainly have in current design (e.g. two different devices may use exactly the same CPU/GPU and Android version and yet may perform completely different because of OEM shipping older/newer GPU drivers or one including optimizations not available in the other). Including device model would fix that but it would also probably require some redesigns. In other words, at least currently it's not worth the work needed, we still don't have any Android testing entry (on the wiki)... - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) | : I won't work on this for a while, just realized some other issues we'll certainly have in current design (e.g. two different devices may use exactly the same CPU/GPU and Android version and yet may perform completely different because of OEM shipping older/newer GPU drivers or one including optimizations not available in the other). Including device model would fix that but it would also probably require some redesigns. In other words, at least currently it's not worth the work needed, we still don't have any Android testing entry (on the wiki)... - [[User:Jhonn|Jhonn]] ([[User talk:Jhonn|talk]]) | ||
== Using Variables == | |||
So I've been contemplating how variables might be used to communicate among templates and get this template to do some more work for us. A couple things to try out... | |||
*Setting a "Last Test Release" variable, and using it to flag when test results are out of release order (things like the 5.0-re releases may muck with such a bit though, since there's a small overlapping range point in time indicators there). | |||
*Use the "Last Test Release" variable in [[Template:Testing/end]] to generate categories indicating an age since the last test was performed (i.e. "Tested within 100 revisions", "Tested within 1000 revisions", etc). [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 22:17, 20 November 2015 (CET) | |||