ducklet
4908b1fc6e
In its current state the implementation should allow a user to resume their session if the websocket connection is reset, for whatever reason. This could be expanded to allow session sharing (multiple agents logging in to the same client), or manual session resume via some sort of password (encode uid & key to some pass-phrase kinda thing, or QR code).
33 lines
798 B
HTML
33 lines
798 B
HTML
<meta charset="utf-8" />
|
|
<link rel="stylesheet" type="text/css" href="buzzer.css" />
|
|
<body>
|
|
<div id="error">
|
|
Error:
|
|
<code></code>
|
|
</div>
|
|
<div id="info">
|
|
<label
|
|
>You:
|
|
<input
|
|
type="text"
|
|
name="username"
|
|
id="username"
|
|
placeholder="Please put your name here ..."
|
|
/></label>
|
|
<h2>All Players</h2>
|
|
<ul>
|
|
<!-- players will be inserted here -->
|
|
</ul>
|
|
</div>
|
|
<div id="buzzbox">
|
|
<p id="active">BZZZZZ!</p>
|
|
<p id="ready">Press <strong id="bkey">{key.name}</strong> to activate buzzer.</p>
|
|
<p id="inactive">Please focus the window to allow the buzzer to work.</p>
|
|
</div>
|
|
</body>
|
|
|
|
<template id="player">
|
|
<li data-cid="client ID">player name</li>
|
|
</template>
|
|
|
|
<script type="module" src="./buzzer.js"></script>
|