How nesbox/tic-80 works
Project type and purpose
• TIC-80 is a cross-platform “fantasy computer” emulator and development environment.
• It bundles a core emulator, multiple scripting language interpreters, built-in editors (code, sprites, maps, sound), a command-line interface, platform abstraction layers (SDL, libretro, bare-metal Pi, Android, N3DS), and a web-based front-end (WASM + JavaScript).
File structure analysis
• Top-level directories
– src/ : C source for core emulator (core/, cart.c, script.c), language-binding APIs (src/api/*), studio UI (src/studio/*), system abstractions (src/system/*).
– include/ : public headers (tic80.h, retro_endianness.h, types, config).
– build/ : platform‐specific build artifacts and wrappers (android/, baremetalpi/, linux/, macosx/, webapp/, …).
– cmake/ : CMake modules to configure optional dependencies and target platforms.
– tools/ : helper command-line utilities (bin2txt, prj2cart, wasmp2cart, etc.).
– templates/ : starter projects in various languages for cartridges (C, D, Rust, Zig, Nim, etc.).
– demos/, assets/ : sample cartridges and data.
Insights from README
• Supports multiple scripting languages (Lua, JS, Ruby, Python, Squirrel, Wren, Fennel, Janet).
• Cross-platform: desktop (SDL2), console (libretro core), bare-metal Pi, Android, 3DS, web (WebAssembly).
• Build system: CMake driving many optional modules and backends.
a. Main components
1. Core Emulator Engine (C code in src/core, cart.c, script.c)
2. Language Bindings / API Modules (src/api/*)
3. Studio UI (built-in editors under src/studio; code, sprite, map, sfx, music)
4. System Abstraction Layer (src/system/SDL, libretro, baremetalpi, n3ds, android)
5. Web Front-End (build/webapp: WASM-compiled core + JavaScript UI + HTML/CSS)
6. Command-Line & Tools (tool executables under build/tools and tools/)
7. Build System (CMake + platform wrappers under cmake/)
8. Asset & Cartridge Storage (flat files, .tic cartridges, demo assets)
b. Relationships & data flow
• Platform Layer → calls System Abstraction Layer APIs → forwards events (input, graphics, audio) to Core Engine
• Studio UI → uses Core Engine APIs for real-time preview and editing → writes cartridge files
• CLI Tools → call into Core API or manipulate cart files directly → produce binaries or WASM-packs
• Web Front-End → loads WASM module (Core + API modules compiled to WASM) → JavaScript UI wraps built-in editors and runtime loop
• Build System → compiles Core + API + Platform layers into multiple targets (desktop exe, library, WASM, Android APK, etc.)
c. Architectural patterns & design principles
• Modular plugin-style API for each scripting language
• Layered architecture: Core → API → Studio/UI/CLI → Platform
• Abstraction of graphics/audio/input via a small system layer per platform
• Single code-base compiled with CMake into native binaries, shared libraries, or WebAssembly
d. Relevant technologies, frameworks, libraries
• C, C++ (very minimal C++), SDL2, libretro API, WebAssembly (Emscripten), JavaScript, CMake, miniaudio, libpng, GIF, kiss_fft.