Difference between revisions of "Template talk:Config"

From Dolphin Emulator Wiki
Jump to: navigation, search
(Outdated Talk clean-up)
(Outdated Talk clean-up)
Line 1: Line 1:
==To Do==
 
*Add "Resolution" setting for titles like Mega Man, which are sensitive to particular resolutions.
 
*Fix alternate row shading. Unfortunately the nested if's/tables make this complex.
 
*Add pop-up descriptions to config settings
 
*Address bolding of sections beyond first shown /wo including excessive white-space
 
**The wiki will apparently only appropriately parse "===" enclosed titles as titles if line feeds occur between each section outside of the if's. This unfortunately inserts excess white-space in cases where no sections are shown. Attempted corrections that fail include:
 
***Adding white-space to the beginning/ends of sections within ifs
 
***Adding white-space between sections via a secondary set of ifs
 
*Generate error category for non-compliant settings: Most settings have limited valid values (i.e. On/Off,RAM/Texture/"Texture/RAM";etc.). it would be good to parse for such and output error categories for non-complaint pages.
 
----
 
: Is "fix alternate row shading" still an issue?  Looks okay to me.
 
::The table rows aren't alternately shaded, so yes, but it's a minor issue. Possible fix described at [http://en.wikipedia.org/wiki/Template:Alternating_rows_table_section Wikipedia:Template:Alternating_rows_table_section]. [[User:Kolano|Kolano]] 04:37, 17 August 2011 (CEST)
 
: Can you provide more detail for 'Address bolding of sections beyond first shown w/o including excessive white-space'?
 
::I've updated the sandbox test page to show the problem. It's related to the spaces between config sections. I was able to resolve this by purging the whitespace but doing so resulted in the alternate issue of section titles not being styled as headings (i.e. bolded/font-size increased).[[User:Kolano|Kolano]] 04:37, 17 August 2011 (CEST)
 
: I've create [[Template:Config/sandbox-todo]], [[Template:Config/sandbox-todo/testing]] specifically for work on ToDo list issues
 
--[[User:Keller999|Keller999]] 02:35, 16 August 2011 (CEST)
 
 
 
== Config List ==
 
== Config List ==
 
Remember the [[Dolphin Manual]]? Well, I've thought about it a lot since that project failed, and really the dolphin manual was only two things.
 
Remember the [[Dolphin Manual]]? Well, I've thought about it a lot since that project failed, and really the dolphin manual was only two things.

Revision as of 22:56, 16 January 2015

Config List

Remember the Dolphin Manual? Well, I've thought about it a lot since that project failed, and really the dolphin manual was only two things.

1. A list of instructions for set up and doing various things. The wiki already has most of that in Help:Contents via our tutorials.

2. A list of functions in the emulator and what they do and where they are.

We already have #1. However, it occurred to me that we already have #2 as well... right here. Template:Config. It lists all of the options in the emulator, shows where they are (general location via categories anyway) and describes them. The problem is that it is very user unfriendly. It's designed to display stuff in wiki pages, and it does that job very well but it's not very friendly for other purposes. So, here's my question to you guys - how hard would it be to make a page that automatically displayed every Template:Config entry? That way, any time Template:Config is updated, the big user-friendly list would be updated as well. With a little tweaking to make it more presentable, we take what we already have and maintain and suddenly it's a one-stop shop for Dolphin help, fulfilling everything the Dolphin Manual set out to achieve! But uh, I don't know how to do that. You know, artist and all. What do you guys think? - MaJoR (talk) 15:23, 13 July 2014 (CEST)

It'll need some refactoring to automatically add new option to a list and the template's code is messy at the moment. A temporary solution is creating a page and include Config template with every possible entry and then update accordingly whenever we add new options. It's a quick way to archive #2 until we refactor the template's code. Jhonn (talk)