Wrong index check function (for associative array rather than array)
meant that pages were overwriting each other and the table only showed
one user score per page.

If there's just a comment, the RankedChoice->getChoice function throws
a warning (no actualy error) into the logs.  Doing a quick check
beforehand to make sure the choice actually exists is cleaner.

Small bug that made the scoring a little unintuitive.  Fixes
ots/clients/lfc/torque-tracker#151

ots/clients/lfc/torque-tracker#151: Scores seem to be 0–4 instead of 1–5

Style widget selection

See merge request !3

Make save friendlier

See merge request !2

Apply Jim's requested changes

See merge request !1

Also includes a little class naming fix.