If there's more than 100 submissions in a language, the default 20 tick size is too low.

Really one tick is enough, so you could round the actual number of submissions down to a multiple of 100 (or 10 if it's less than 100).

This should be respected in the view shown when the tool has access to hidden data including disabled teams.

The contest downloader has to do a lot of guesswork when it's run without credentials. It can mostly work things out, but some things like WA/RTE/TLE distinction are msising and there may be other bugs as it doesn't get a lot of testing in reality.

We should warn if a user runs the tool like this, just in case they have credentials available to plug in.

Currently it looks like this:

\newcommand{\solvestatsC}{\printsolvestats{0}{0}} % +0?

It should look like this:

\newcommand{\solvestatsC}{\printsolvestats{0}{0}{0}}

Forked from #3

all the example command lines need to be updated since we updated our demoweb instance recently. Also the resolver from the end of this command line needs to be removed:
https://github.com/hex539/scoreboard/tree/master/scoreboards/resolver

The example command line needs to pass in "NWERC - Eindhoven University of Technology" or (less transparently) "14550" instead of just "Participants" like it used to.

For BAPC I created a run.sh script as follows (login params omitted)

bazel run analysis:activity -- \
~/git/bapc/2019/bapc/solve_stats

bazel run analysis:activity -- \
--solvestats > ~/git/bapc/2019/bapc/solve_stats/problem_stats.tex

It would be really nice to directly create the problem_stats.tex (or probably solve_stats.tex) when running analysis:activity. The output I used was:

\newcommand{\solvestatsD}{\printsolvestats{26}{1}{11}}
\newcommand{\solvestatsH}{\printsolvestats{100}{26}{29}}
\newcommand{\solvestatsB}{\printsolvestats{57}{56}{0}}
\newcommand{\solvestatsL}{\printsolvestats{3}{2}{0}}
\newcommand{\solvestatsF}{\printsolvestats{100}{20}{27}}
\newcommand{\solvestatsC}{\printsolvestats{1}{1}{0}}
\newcommand{\solvestatsI}{\printsolvestats{20}{1}{7}}
\newcommand{\solvestatsJ}{\printsolvestats{80}{56}{0}}
\newcommand{\solvestatsE}{\printsolvestats{124}{23}{37}}
\newcommand{\solvestatsA}{\printsolvestats{15}{3}{8}}
\newcommand{\solvestatsG}{\printsolvestats{52}{10}{22}}

Just noticed it's using a thin (serif) font. It's not super readable I think.

The default language out-of-the-box if locale isn't set should be some kind of universal emoji-based theme using "🕐", "🎈", "✔", and "✘".

Nice-to-have to make putting together solution slides easier after contests.

It would make it simpler to use since all you need is java.

Depending on the contest size and size on the slides it would be nice to customize SECONDS_PER_BAR.

Running bazel run scoreboards/resolver -- --url https://www.domjudge.org/demoweb/api/ --groups="NWERC - Eindhoven University of Technology" gives:

Fetching https://www.domjudge.org/demoweb/api/contests...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/state...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/scoreboard...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/judgement-types...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/languages...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/problems...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/groups...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/organizations...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/teams...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/submissions...
Fetching https://www.domjudge.org/demoweb/api/contests/nwerc18/judgements...
Exception in thread "main" java.lang.IllegalStateException: There is no OpenGL context current in the current thread.
	at org.lwjgl.opengl.GL.createCapabilities(GL.java:378)
	at org.lwjgl.opengl.GL.createCapabilities(GL.java:322)
	at me.hex539.resolver.ResolverWindow.run(ResolverWindow.java:62)
	at me.hex539.resolver.Executive.main(Executive.java:64)

btw. all the example command lines need to be updated since we updated our demoweb instance recently. Also the resolver from the end of this command line needs to be removed:
https://github.com/hex539/scoreboard/tree/master/scoreboards/resolver

This is so that downstream slide templates can go modify them (eg. black/white backgrounds make for different ideal colour setups)

Please provide more detailed document, cause i am not very familiar with java.

Performance is OK when running as a standalone desktop app connected to HDMI. Still, things get a little bit choppy if casting the screen to another device at the same time, and this is one of the main use cases for the program.

On an i7-6770HQ iwth software rendering, the desktop app can do 4K60fps but the above flame graph shows that it spends a lot more time than it should rendering fonts and using OpenGL 1.1 immediate mode APIs.

Next steps are to:

1. Add a benchmark target for rendering N frames and then exiting.
2. Switch all of the glBegin/glEnd usage into VBOs.