GitLab

Also make sure webpack will deploy the resources/ folder alongside
everything else.

See merge request !19

Add more text to the README for people to read.  Adds the following
things:

- Marketing and Branding
- Contact Information
- Update existing parts to reflect current state of the code-base.
- A level design guide with a lot of information about the pitfalls.

Closes #18

See merge request !20

Extract the current version from git during build-time and display it
ingame in the bottom left corner.  Currently, this is done at WASM
build-time so we might not capture changes to the www/ part which
happened after a WASM build.  A possible solution would be to display
a second version from JavaScript if we detect that the two are
different.

Fixes #18.

See merge request !17

Run all the web builds as well, in the pipeline for merge requests.

Cache cargo build directory (`target/`) and npm's `node_modules/`.

See merge request !14

See merge request !15

Spawnpoints and Sanity tracking

Closes #11

See merge request !13

Let's hope we don't make them loose it D:

Make sure the player spawns don't put the player into a wall collider.

Load all spawn positions from the `spawns` layer in the map SVG and
store them as level data.  As a first use, make the player spawn at one
of the player spawnpoints randomly.

Controllable and colliding player entity

See merge request !12

This allows one to debug wrong colliders in-engine.  Quite helpful if
inkscape messed up the SVG again ...

The values passed to Cuboid::new() must be half extents and the position
of the collider must describe the center.  In SVG, rectangles are
described by the top left corner and full extents which was incorrectly
passed to the Cuboid::new() constructor.  Fix this.

Don't move the player if it is colliding with the world

Add a basic level with proper colliders.

Control the player with WASD like a pro gamer.

Add plumbing for the most basic player:

- A `Player` component to mark the entity which is the player.
- A `Player` resource which holds the entity ID of the player.
- A `draw_tmp_player_system` to draw the player as a circle (for now).
- A `create_player` function to create the player entity.
- Update the `moving_system` to put the camera at the player position.

Colliders and Keyboard Events

See merge request !11

Due to the camera translation, the clear is currently not actually
happening over the entire visible canvas.  Reset the transform before
clearing to ensure it's working correctly.

Just as an example to build on.

It's only relevant for mouse events so only make it available there.

During state cleanup, remove all registered handlers from the DOM again.

Turns out that e.g. an out-of-band event() will trigger the loop again,
thus leading to two loops running.  This of course kills performance
really quickly.

Don't ever leak the handlers, keep track of them and drop them when they
are no longer needed.

We currently have a `state` and a `states` module.  This is confusing,
rename the state module to `gamestate` to make a more obvious
distinction.