GitLab

Currently a bit ugly because we're essentially polling the future, but
it'll do for now ...

Remove the previous PoC code as this will now be handled by the "state
machine".

Pretty graphics and it already exists so why not

No more mouse-clicks needed!

Remove the `context` resource and instead use the Rendering API
everywhere.  For now, expose the `ctx` field for direct access but of
course this change should be reverted in the long run.

Add a StateMachine for managing game-states.  Not all features are
implemented yet.

These are meant for "Headlines and Buttons".

See merge request rust/webassembly-game!4

Current stable rustfmt removes the `async` keyword inside the extern "C"
{} block.  Add a marker to ensure this won't happen by disabling
formatting for this section for now.

rustfmt behaves correctly on nightly.

See merge request rust/webassembly-game!3

More utils

See merge request rust/webassembly-game!2

Add a request_animation_frame() function which properly mirrors the
behavior of JavaScript's requestAnimationFrame().

The function takes care of repeated scheduling which differs from the
javascript requestAnimationFrame() equivalent.  Rename it to make this
more clear.

See merge request rust/webassembly-game!1

It is good practice to keep the cargo lockfile in version control for
application projects.  This allows rebuilding the project exactly as
upstream builds it, without dependency updates implicitly getting pulled
in.

This is all still a huge hack but demonstrates that the idea works:  We
synchronize all entities with a collider to the ncollide CollisionWorld
and the use it to find potential targets for mouse clicks.

This way we can properly see the message in case a panic occurs.