How jatzuk/game-talk-playground works
Project type and purpose
• This is an Android “playground” app that embeds a small 2D game engine. It’s meant as demo code for a talk, showcasing core ideas: different game-loop implementations, an Entity-Component-System (ECS) architecture, a processing pipeline, and multiple rendering strategies (Canvas vs Compose).
File structure
• Top level: standard Android module (app/) with Gradle scripts, resources, manifest.
• app/src/main/java/dev/jatzuk/gametalk/engine: the engine library subdivided into:
• ecs (components, entities, systems)
• gameloop (ComposeGameLoop, SurfaceGameLoop, ViewGameLoop)
• pipeline (EngineProcessingPipeline)
• renderer (CanvasPipelineRenderer, ComposeDrawScopePipelineRenderer)
• scene (Scene, AbstractScene, SceneConfigRepository)
• scripting (game-object factories like CarGameObject)
• telemetry (Telemetry, TelemetryRepository)
• util (Clock, Safe, CanvasUtil)
• app/src/main/java/dev/jatzuk/gametalk/playground: demo entrypoints and UI
• entrypoint packages for Compose / SurfaceView / Android View game loops
• scene packages for sample scenes (StressTest, Showcase)
• ui for Activity, ViewModel, routing and UI components (DropDownList, Theme, etc.)
README for additional insights
• Confirms this is demo code for a talk, highlights where to find core theory (GameLoops101.kt), engine architecture, and sample scenes.
• Labels: use clear names matching package or class names.
• Blue for Presentation
• Green for Engine Core
• Yellow for Data/Repositories
• Gray for Utilities
• Rectangles for modules/packages