How naminginprogress/engine works
VKE is a Java engine framework for applications, with window and renderer lifecycle management and APIs for rendering, ECS, audio, events, and asset/file handling. Its main workflow is an application starting the engine: the engine creates a window, fires lifecycle events, initializes the app, obtains the renderer, and later frees app and engine resources. The README is empty, and sampled source is limited, so several subsystem relationships are intentionally not inferred.
Main entry points: VKEngine.java Engine lifecycle · app Application API · pipeline Pipeline config · window Window API
Components 15
Engine runtime
- Engine lifecycle
src/main/java/com/vke/core/VKEngine.java - Application API
src/main/java/com/vke/api/app - Window API
src/main/java/com/vke/api/window - Event system
src/main/java/com/vke/api/event - Service API
src/main/java/com/vke/api/services2
Rendering
- Renderer API
src/main/java/com/vke/api/rendering/abstraction/renderer - Pipeline config
src/main/java/com/vke/api/rendering/vulkan/pipeline - Vulkan backend
src/main/java/com/vke/core/rendering/vulkan
Game systems
- Entity component system
src/main/java/com/vke/core/ecs - Scene API
src/main/java/com/vke/api/scene
Media and data
- Audio system
src/main/java/com/vke/core/audio - File decoders
src/main/java/com/vke/core/file - Config parsing
src/main/java/com/vke/api/parsing/config - VKZ archives
src/main/java/com/vke/api/vkz
Other components
- Application developer
Connections 7
- Application developer → Engine lifecycle: starts
- Engine lifecycle → Application API: initializes
- Engine lifecycle → Application API: frees
- Engine lifecycle → Window API: creates window
- Engine lifecycle → Event system: fires lifecycle
- Engine lifecycle → Renderer API: obtains renderer
- Pipeline config → Config parsing: parses config