Template talk:MoveData/testcases: Difference between revisions
Oldmanwang (talk | contribs) m (→New design) |
Oldmanwang (talk | contribs) |
||
| Line 11: | Line 11: | ||
Issues I'm aware of but not sure of how to fix: | Issues I'm aware of but not sure of how to fix: | ||
* startupRoot's push parameters down, obscuring which is which. I don't see the value in having the startupRoot displayed personally, when there are several other indicators of where the move stems from. | * startupRoot's can push parameters down, obscuring which is which. I don't see the value in having the startupRoot displayed personally, when there are several other indicators of where the move stems from. | ||
* Moves with large inputs (i.e. 10hit combos) go off screen on phones. | * Moves with large inputs (i.e. 10hit combos) go off screen on phones. | ||
* " | " after target and before damage, shows even when those parameters aren't described. This is mainly an aesthetic issue for moves like stances. | * " | " after target and before damage, shows even when those parameters aren't described. This is mainly an aesthetic issue for moves like stances. | ||
* Move No. is harder to read on the light color-scheme, would be better if it was white on light-scheme, black on dark. | |||
Ideas I'd like to implement that I think require altering Javascript: | Ideas I'd like to implement that I think require altering Javascript: | ||
Revision as of 05:53, 2 February 2021
I moved the following from Template talk:MoveData to get around the conflicting stylesheets. RogerDodger (talk) 15:29, 1 February 2021 (UTC)
New design
See here for intended look.
I wanted to make it so each parameter fell in the same place, regardless of what was and wasn't defined, so that the user always knows where to look. The parameters I've put in the column before the frame data are just what I figured were the most common to be added to notes, let me know if you think they could be used better. The two main columns I named 'frames' and 'whiff', I figure the frames info is more useful at close range and the whiff is more useful at a distance.
Issues I'm aware of but not sure of how to fix:
- startupRoot's can push parameters down, obscuring which is which. I don't see the value in having the startupRoot displayed personally, when there are several other indicators of where the move stems from.
- Moves with large inputs (i.e. 10hit combos) go off screen on phones.
- " | " after target and before damage, shows even when those parameters aren't described. This is mainly an aesthetic issue for moves like stances.
- Move No. is harder to read on the light color-scheme, would be better if it was white on light-scheme, black on dark.
Ideas I'd like to implement that I think require altering Javascript:
- Display Notes toggle: (show/hide) and (all/all) buttons on the far right column of the first row which toggle display of notes for particular moves or toggle display for all moves.
- A stance button shortcut: a script that can recognise when something has been put into the move name parameter between brackets i.e. Hitman (HMS), so that anytime HMS is written inside an input-ctn parameter, it would become a link that scrolls to the point of the page where that stance is first described in brackets as a move name. This could also help with follow up moves and chain throws for finding move roots. Could even have it so that the brackets abbreviation was hidden for a cleaner design.
Whaddya think? Oldmanwang 10:44,1 Feb 2021 (UTC)