From 228c44724bca054266d83dd10baee62281c6e09b Mon Sep 17 00:00:00 2001
From: David Thompson
On its own, the kernel does not do very much at all. In order to actually respond to input events, update game state, or render output, -the programmer must provide an engine. But donât worry, you donât +the programmer must provide an engine. But don’t worry, you don’t have to start from scratch! Chickadee comes with a simple engine that uses SDL to create a graphical window and handle input devices, and OpenGL to handle rendering. This default engine is enough for most @@ -122,7 +122,7 @@ and writes to a terminal instead of a graphical window. The game loop kernel makes no assumptions.
Start the game loop. This procedure will not return until
abort-game
is called.
@@ -169,7 +169,7 @@ game controller, Chickadee comes with an easy to use engine just for
this purpose in the (chickadee)
module: run-game
.
#f
] [#:update-hz 60] [#:load] [#:update] [#:draw] [#:quit] [#:key-press] [#:key-release] [#:text-input] [#:mouse-press] [#:mouse-release] [#:mouse-move] [#:controller-add] [#:controller-remove] [#:controller-press] [#:controller-release] [#:controller-move] [#:error]#f
] [#:update-hz 60] [#:load] [#:update] [#:draw] [#:quit] [#:key-press] [#:key-release] [#:text-input] [#:mouse-press] [#:mouse-release] [#:mouse-move] [#:controller-add] [#:controller-remove] [#:controller-press] [#:controller-release] [#:controller-move] [#:error]Run the Chickadee game loop using the SDL engine in OpenGL mode.
-- cgit v1.2.3