Talk:Combat system: Difference between revisions
Jump to navigation
Jump to search
VANKRASN39 (talk | contribs) m (wrong slash) |
VANKRASN39 (talk | contribs) mNo edit summary |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
Didn't you want \cdots and not Xs? Spaces are also much easier to read. [[User:VANKRASN39|VANKRASN39]] ([[User talk:VANKRASN39|talk]]) 13:36, 6 October 2016 (CDT) |
Didn't you want \cdots and not Xs? Spaces are also much easier to read. [[User:VANKRASN39|VANKRASN39]] ([[User talk:VANKRASN39|talk]]) 13:36, 6 October 2016 (CDT) |
||
I tried a few ways of formatting these formulas and prefer this over the alternatives, and it has to do with the multi-word variable names. |
|||
*While <math>a \cdot b + c</math> is better than <math>a \times b + c</math>, I don't think <math>\mathrm{VeryLongVariableName} \cdot \mathrm{AnotherVariableName} + \mathrm{YetAnotherVariableName}</math> is necessarily more intuitive, and since the reader won't mix up <math>x</math> with <math>\times</math> if all the variables are long words it's fine to let stand. |
|||
*Subscript scoping makes more sense in non-spaced variables. Compare: <math>\mathrm{ShieldSizeModifier}_{\mathrm{Ranged}}</math> vs. <math>\mathrm{Shield\ Size\ Modifier}_{\mathrm{Ranged}}</math>: it's more obvious in the first case that the subscript applies to the entire variable name. |
|||
[[User:ZHOUY1|ZHOUY1]] ([[User talk:ZHOUY1|talk]]) 13:52, 6 October 2016 (CDT) |
|||
:How about only bunching when there's a subscripted part? It's really rough to read. I also really prefer brackets instead of double parentheses [( ... )] vs (( ... )). [[User:VANKRASN39|VANKRASN39]] ([[User talk:VANKRASN39|talk]]) 14:27, 6 October 2016 (CDT) |
|||
::Is it better with brackets around the variables? <math>[\mathrm{Shield\ Size\ Modifier}]_{\mathrm{Ranged}}</math> [[User:ZHOUY1|ZHOUY1]] ([[User talk:ZHOUY1|talk]]) 14:31, 6 October 2016 (CDT) |
|||
:::Yes, that's much better. [[User:VANKRASN39|VANKRASN39]] ([[User talk:VANKRASN39|talk]]) 14:39, 6 October 2016 (CDT) |
|||
::::I'll make the changes and also restore the <code>\quad</code> spacing edits. [[User:ZHOUY1|ZHOUY1]] ([[User talk:ZHOUY1|talk]]) 14:52, 6 October 2016 (CDT) |
|||
:::::Sure :) I put the \quads in there because I was trying to figure out why there was an extra space before Base Value. I have no clue. [[User:VANKRASN39|VANKRASN39]] ([[User talk:VANKRASN39|talk]]) 14:59, 6 October 2016 (CDT) |
Latest revision as of 13:59, 6 October 2016
Didn't you want \cdots and not Xs? Spaces are also much easier to read. VANKRASN39 (talk) 13:36, 6 October 2016 (CDT)
I tried a few ways of formatting these formulas and prefer this over the alternatives, and it has to do with the multi-word variable names.
- While is better than , I don't think is necessarily more intuitive, and since the reader won't mix up with if all the variables are long words it's fine to let stand.
- Subscript scoping makes more sense in non-spaced variables. Compare: vs. : it's more obvious in the first case that the subscript applies to the entire variable name.
ZHOUY1 (talk) 13:52, 6 October 2016 (CDT)
- How about only bunching when there's a subscripted part? It's really rough to read. I also really prefer brackets instead of double parentheses [( ... )] vs (( ... )). VANKRASN39 (talk) 14:27, 6 October 2016 (CDT)
- Yes, that's much better. VANKRASN39 (talk) 14:39, 6 October 2016 (CDT)
- Sure :) I put the \quads in there because I was trying to figure out why there was an extra space before Base Value. I have no clue. VANKRASN39 (talk) 14:59, 6 October 2016 (CDT)