15,188
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. |
(Username rename (Jhonn => mbc07)) |
(Username rename (MaJoR => MayImilae)) |
||
Line 9: | Line 9: | ||
We can, I may need to make some template edits to handle categories, documentation updates, and etc for such. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 08:28, 1 May 2014 (CEST) | We can, I may need to make some template edits to handle categories, documentation updates, and etc for such. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 08:28, 1 May 2014 (CEST) | ||
The main problem I see is that... will users even know what's in their phones? Sure they will possibly know what their phone is, so I guess that gives us something to work from, but are you ok with getting CPU and GPU information from a phone name? And how to phone names fit in the template? - [[User: | The main problem I see is that... will users even know what's in their phones? Sure they will possibly know what their phone is, so I guess that gives us something to work from, but are you ok with getting CPU and GPU information from a phone name? And how to phone names fit in the template? - [[User:MayImilae|MayImilae]] ([[User talk:MayImilae|talk]]) 16:30, 5 May 2014 (CEST) | ||
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> |