Anyone know how to make an "or" statement?

Currently, this template works perfectly fine in terms of individuals - just put {{SSBBMatchupTable|display=mrgame&watch}} on a page and it'll give you his matchups only (works for all characters). However, without an "or" statement, I can't set "display" to "all" and have all the rows appear (for the character matchups page). I've looked around a bit and found nothing. Anyone else have any ideas? Toomai Glittershine Toomai eXemplary Logic 20:34, October 4, 2009 (UTC)

Do you really need it to do that? Why not just keep the matchup article having the full table and this one set up to display an individual row? While it'd be nice not to have to update both when there's a change, it's certainly workable. Miles (talk) 22:13, October 4, 2009 (UTC)
You have to change how it's coded. For example (imagine this is in html instead of wikitable, because this might be a case where html > wikitable):
{{#ifeq:{{{gandw|{{{alldisplay|no}}}}}}|yes|<tr><td>Stuff about op</td><td>Moar stuff</td></tr>}}
{{#ifeq:{{{marth|{{{alldisplay|no}}}}}}|yes|<tr><td>Stuff about op</td><td>Moar stuff</td></tr>}}
{{#ifeq:{{{ike|{{{alldisplay|no}}}}}}|yes|<tr><td>Stuff about op</td><td>Moar stuff</td></tr>}}

This defaults to no, as in no display. The parameter alldisplay can be set on all the variables by |alldisplay=yes, so we can use the flexibility currently in the template. Obviously, you'll have to go around and fix the current usages, but you'll be able to build more out of this. --Sky (t · c · w) 22:25, October 4, 2009 (UTC)

Awesome. This even lets us display more than one row at once, which'll make things look better for two/three-in-one characters. Toomai Glittershine Toomai eXemplary Logic 22:49, October 4, 2009 (UTC)


I appreciate that someone's trying to help out those that have lower resolution monitors and such, but I have to disagree with this.

  1. On high-resolution monitors, the full table just barely has to push out the side of the page space, but that tiny push is being interpreted as needing both a horizontal and a vertical scrollbar for a single row and column.
  2. On low-resolution monitors, you'll be using scrollbars whether they're attached to the table or not. And having scrollbars attached to a table is just ugly.

So unless there's some massive benefit I'm missing, the scrollbars will be removed soon. Toomai Glittershine Toomai eXemplary Logic 15:22, January 2, 2010 (UTC)

I agree scrollbars are bad, but I'm not seeing them anywhere in relation to this... Miles (talk) 18:15, January 2, 2010 (UTC)
Oh, right. Forgot to specify that it only appears when the full table is displayed, that is on the character matchups page. Toomai Glittershine Toomai eXemplary Logic 18:28, January 2, 2010 (UTC)
?? I just looked there; no scrollbars in sight. Miles (talk) 02:06, January 3, 2010 (UTC)
To the 2nd point, it's the difference between a scrollbar on the entire page and on the table. I much prefer the table and I very much doubt you'll find disagreement with me. It is simply more convenient on the majority of pages where this template is used; the character matchups page is not the only one now.
To the first, I'm not sure I understand the problem. There should be no "pushing out the side of the page space"... --Sky (t · c · w) 01:12, January 7, 2010 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.