I've tried to keep the changes to a minimum. A demo is online at https://mccurley.org/iacr2/ using the Asiacrypt 2019 program. There are only a few things dictated by the bootstrap 3=>4 migration.
As it turns out, I think it might be possible to use a much simpler template that does not use the twosessions hack, but I've avoided putting it into this pull request. The idea is to remove twosessions, and have
{{#each session}}
... the dom for a session
{{/each}}
Then we can change the styling on the session based on how many sessions there are.
There are two ways to do this that I can think of:
use an ifCond helper in handlebars to test when the length of sessions is > 1. Then use this helper to apply either col-10 or col-5 on the session. We don't need track1Event and track2Event classes, because we could use css selectors to style the two nodes differently (e.g., nth-child(2)).
use only css selectors to style the node based on how many siblings it has. The only disadvantage of this technique is that we could not switch on the length to apply col-5 classes. I would prefer to keep the bootstrap grid classes, so I don't favor this technique.
I've tried to keep the changes to a minimum. A demo is online at https://mccurley.org/iacr2/ using the Asiacrypt 2019 program. There are only a few things dictated by the bootstrap 3=>4 migration.
As it turns out, I think it might be possible to use a much simpler template that does not use the twosessions hack, but I've avoided putting it into this pull request. The idea is to remove twosessions, and have {{#each session}} ... the dom for a session {{/each}} Then we can change the styling on the session based on how many sessions there are.
There are two ways to do this that I can think of: