Create the paper scoresheet

[rikkertkoppes]

Since the we also want to be able to produce paper versions of scoresheets, this is a case to do that

• a first approach may be to create a xsl stylesheet to reproduce the current form. Target is found here, xml definition is found here
• generate a pdf using node webkit, the browser we use for the desktop version. This should be a part of the print module.

Also, think about a join with the team list and / or competition schedule

[rikkertkoppes]

First throw at it using @robvw his work: d399430a61ad5199ee79b9410b84f807bb674f14

Mainly an exercise to check the xml for this use case

[rikkertkoppes]

This was updates and workshop with the new XML format.

@kmeesters: do we need more on this sheet before calling it done? Think headers, footers? imagery?

[rikkertkoppes]

@kmeesters can you provide answers to the above? Then assign it back to me? also see #36

[kmeesters]

@rikkertkoppes Must haves: Input fields for (i.e. room on the paper form the write):

• Referee name
• Table name
• Team name
• Round number
• Signature of team
• Signature of Ref

Next:

• Ensures it fits on one page (or make sure/instruct that people select the 'fit to page' option)

Nice to haves in a seperate issue

[rikkertkoppes]

Would it be enough for a first effort to have this available on desktop only (ie the single desktop scenario)?

Cloud printing from mobile devices may be a bit of a challenge

[kmeesters]

I did not even consider that ;). No indeed I see this a part of the (extended) tournament administration options, which we (for now) can assume willl take place on desktop / laptop enviroments. (wedstrijdsceretairaat / scorekeeper)

[rikkertkoppes]

Creating a two step process for this:

1. Generate html using saxon (in a grunt task)
2. Generate pdf using phantomjs (in a grunt task also)

This will result in a two build tasks that will generate challenge html and pdf files. We may need to think a bit on how to store localized xml files

Also see #50 for file structures. Html and Pdf files can be stored under challenges/html and challenges/pdf respectively

[rikkertkoppes]

Added html and pdf scoresheet generation scripts, see 7b89f958097266be965b23cc16bc42cb1fbe41e0

I'm parking adding the input lines for various other data for now

[rikkertkoppes]

@kmeesters Any wishes on the positioning of

• Referee name
• Table name
• Team name
• Round number
• Signature of team
• Signature of Ref

Working on creating the pdf's now, also on prefilling. Got this so far (whitespace in the right column hopefully accommodates for possible future expansion of missions)

[robvw]

Could you have another look at WC mission 13, something's wrong with options being drawn on top of other things.

I'm attaching an example of a (manually prepared) scoresheet. Maybe that can serve as inspiration / template for where to put the "boilerplate" fields?

Bunch of fields redacted (I have no idea how paranoid we are about these forms not "leaking"), but the idea should be clear.

[rikkertkoppes]

Its work in progress. I'll fix the overlapping text.

[kmeesters]

Request to also add a line for the team name... As verification for the number. We had some illegible scribblings past weekend. A team name is good for verification (even if it is short)

Posititoning, i'd keep it as close to the orginal as possible (see github repo):

• Top:
  • Team nr, team name
  • Round
  • Referee, table
• Bottom:
  • Sig team
  • Sig refee is not needed see #51

[rikkertkoppes]

Update from last weekend:

The location is a bit different. @kmeesters is this ok? Putting the bulk of the fields "at the end" allows us to scale easier over years.

[kmeesters]

It looks perfect! Just a minor request (if possible): could you swap Table with Team? I.e. at the top: Team (Nr+ Name) and Round Bottom: all the other stuff? 'Cause the team NR and Round is critical.

[rikkertkoppes]

That breaks symmetry. I'd like to keep team name, number and signature together.

We can move things around off course, but I think it's good to keep related stuff together.

Which fields are used when calculating scores and rankings? In other words, what is the order of grouping keys you need to do that. E.g. first group by round, then by team, or vice versa

[robvw]

When I input scores I primarily work per round (get all scores for round 1 entered, produce intermediate results, then start on round 2). In my mind "round + team nr" is like a primary key, all the rest (team name, referee, table, time stamp) is "data", which is only used for verification (read: to recover from unreadable writing).

At the moment you have a field "team"; would it be possible to split this into explicitly asking for both team number and team name? Otherwise (especially beginning) referees tend to only enter either value, which increases the issue of bad writing a lot.

Personally I wouldn't mind having team number (and round number) at the top of the sheet, with team name (and signature) at the bottom, but I understand your reasoning as well. To be perfectly honest, so long as all the necessary information is available, I think it doesn't really matter all that much where on the sheet it is.

[kmeesters]

I'm sorry, what @robvw says is what I meant. Top: team nr (+ ideally name to verify) and round nr (could even be a radiobutton, but would be difficult when using different stages)

in other words: it is the same as our current scoring sheet implementation

EDIT: looks really nice!