📄 Files

• ⏭️ (keine Markdown-Dateien im Projekt-Root)

DOCS

• 📚 Docs Home

📁 ADR

• 🗂️ Overview
• 📝 ADR 0001: Tauri Target Architecture
• 📝 ADR 0002: Repository and Tooling Boundaries

📁 DEV

• 🗂️ Overview
• 📝 Implementation Order
• 📝 Porting Workflow
• 📝 Prototype Architecture (Headless)

📁 Tools

• 🗂️ Overview
• 📝 Control CLI Command Matrix
• 📝 Environment Variables
• 📝 Tool Selection Guide

📁 USR

• 🗂️ Overview
• 📝 Run and Play Guide

TauriTwoer

TauriTwoer is a desktop porting and productization project. The current Python/Pygame game is a gameplay prototype and reference source. The target product is a Tauri 2 desktop app with a TypeScript + Canvas runtime.

Target Architecture

• Desktop container: Tauri 2
• Frontend runtime: Vite + TypeScript
• Rendering/UI: HTML5 Canvas
• Native integration: Rust commands for desktop-only concerns (save/load, file access, packaging)

Python is allowed for project tooling, installers, diagnostics, and build helpers. Python is not part of the intended game runtime architecture.

Quick Start

1. Run environment checks:

python3 tools/control.py --doctor

2. Prepare Linux Tauri prerequisites and scaffold app (Linux only):

python3 tools/control.py --tauri

3. Start development runtime:

python3 tools/control.py --start

4. Run tests:

python3 tools/control.py --test

5. Build artifacts:

python3 tools/control.py --build-lin
python3 tools/control.py --build-win
python3 tools/control.py --build-win -p
python3 tools/control.py --build-mac
python3 tools/control.py --build --winlinux

6. Copy generated artifacts to external targets:

export TAURITWOER_COPY_TARGETS="/abs/path1,/abs/path2"
python3 tools/control.py --build --copy

Repository Layout

• apps/tauritwoer-desktop: target desktop app (scaffolded/generated by tooling)
• prototype/: gameplay prototype reference implementation
• tools/: operational tooling (doctor/install/run/build/test/fixes)
• docs/: architecture records, developer docs, tooling docs, and user docs
• .archive/: retired/legacy helper scripts kept for traceability

Documentation Map

• Documentation Index
• ADR 0001: Tauri Target Architecture
• ADR 0002: Repo and Tooling Boundaries
• Developer Workflow
• Prototype Architecture (Headless)
• Tooling Overview
• Run & Play Guide

Core Rule

When architecture decisions conflict, prefer the simpler and cleaner long-term solution. For this project that means: port gameplay logic into TypeScript/Canvas instead of carrying Python into runtime.