Archives
Welcome to all users! This page is where you can ask StrategyWiki-related questions to the staff and senior community figures, and they will do their best to answer. If you want to raise a topic for discussion (rather than just ask about it), please use the community issues forum instead. New issues are entered here, with the most recent at the bottom of the page. If your question does not pertain to editing StrategyWiki (e.g. asking for hints or game-specific information), please ask on the guide's talk page or on the forums.
Please review the Table of Contents to see if your issue has already been raised; also check the archives (to the right) in case it was discussed some time ago.
To facilitate ease of browsing and replying, please:
- Place your question at the bottom of the list.
- Title the question (by placing the title between equals signs: ==Title==).
- Sign your name and date (by adding four tildes: ~~~~).
Controls tables - REDUX
Bringing this up again. There are discussions all over the place about it. But Skizzerz has put together a mockup here. Lets pick one and update the guide. Personally, I prefer the first or the last ones. -- Prod (talk) 02:16, 25 December 2012 (UTC)
- I personally like the last one the best (Action column on left, with right-aligned text). For a left-to-right language, we start reading from the left hand side of the page/screen. Therefore, let us consider what I think would be the most common use case for a controls page -- trying to find a control to do a particular thing because you don't know/forgot it. I don't have any sort of hard evidence that this is the most common use case for a controls page/listing, but I can't really think of any other use cases. For that particular use case, you are first searching for what you are trying to accomplish, and then how to accomplish it. When reading left-to-right, then, you would like the first thing in each row you read to be the what so you then can make a decision on whether or not to continue reading that row more quickly than if you had to first scan to the end of the row to determine the what and then look backwards on the same row for the how. So by having the Action column as the leftmost column, it requires less work to find information by what first and how second, and thus is faster. As for left-aligned vs right-aligned, I prefer right-aligned because it leads more into the table itself and is just more aesthetically pleasing (I could go into another not-researched usability talk of the benefits of right-aligned vs left-aligned for the first column based on personal experience/opinion, but this is already getting pretty lengthy). --Skizzerz 04:02, 25 December 2012 (UTC)
- Since most games have a tutorial or controls list available, I think control references are definitely to a) refresh peoples memories and b) to note controls (such as button combos) that may have been excluded from the in-game list/tutorial. As for left or right, we've always put our controls on the left. This is the natural way - most new people start control pages that way. It's because we think/say it in a syntax like "this button/combination does this". We don't think/say it like "this action requires this button/combination". I don't think we need to switch our standard. It is equally as efficient and logical. I wouldn't mind the change - if you guys want to do it and bot all of the pages into the switch that'd be fine. Note that at the end of this discussion we need to update StrategyWiki:Guide/Getting Started pages#Controls. --Notmyhandle (talk • contribs) 19:52, 27 December 2012 (UTC)
Can't work out how to add back boxart
I created http://strategywiki.org/wiki/Frontier:_Elite_II but I don't know how to add a second image in the info box. I tried separating them with a comma, or writing "Image2" or two lines of "image:". Hydrogyrum (talk) 20:31, 8 February 2013 (UTC)