How firepixel85/tasker-labs works
Project Type and Purpose
• This is a standalone Godot Engine application (“Tasker Labs”) that implements a task‐management UI.
• It consists of multiple Godot Scenes (tscn files), GDScript logic modules, visual assets (textures, shaders, fonts), and a single‐hosted addon plugin.
File Structure to Extract Components
Top‐level directories each correspond to a Scene “module”:
• Main (launch/entry scene + scripts: Greeting.gd, Saving.gd, Warnings.gd, rtv.gd)
• Orientation (tutorial/privacy pledge)
• Daily UI + Daily Task (daily task presentation & instantiation)
• Overview (aggregate view of tasks)
• New Task / Edit (task creation & editing)
• Pop Up (modal dialogs)
• Settings (preferences UI + toggles)
• Sidebar (navigation panel)
• Update (app version update scene)
• Debug (development/debug tools + Theme Debug scene)
• addons/SmoothScroll (plugin providing scroll container and dampers)
Core config files: project.godot, export_presets.cfg.
README for Insights
• No external services or microservices—pure single‐binary Godot app.
• Persistence is file‐based (likely using Saving.gd to write JSON or Godot’s ConfigFile).
• UI navigation flows from Main → Orientation (once) → Sidebar‐driven Scenes.
Main Components & Their Relationships
a. Godot Engine Runtime (host)
b. Scene Modules (Main, Orientation, DailyUI, Overview, NewTask, PopUp, Settings, Sidebar, Update, Debug)
c. Script Modules (GDScript files under each Scene directory)
d. Asset Resources (Textures, Shaders in Theme; plugin assets)
e. Persistence Layer (Saving.gd + local JSON/ConfigFile)
f. Addon Plugin (SmoothScroll)
Relationships & Data Flow:
• The Godot Engine loads project.godot → Main.tscn.
• Main.gd scripts initialize global state (load saved data via Saving.gd).
• Sidebar navigation emits signals to swap child Scenes in the root viewport.
• Each Scene’s controller scripts (e.g., Daily Handler.gd, Task Instantiator.gd, Overview Task Instantiator.gd) read from/write to the in‐memory task model.
• On user actions (add/edit/complete task), scripts update model then invoke Saving.gd to persist changes.
• The SmoothScroll addon interposes on UI containers to provide custom scrolling behavior.
Architectural Patterns & Principles
• Scene‐Tree Modularization: each feature lives in its own Scene directory with its tscn + scripts.
• Signal‐Driven Navigation: Scenes communicate via Godot Signals (Sidebar → Main → Scenes).
• Single Source of Truth: a central “task model” loaded/saved by Saving.gd.
• Resource Separation: Theme folder holds all visual styling; Addon folder is isolated.
• No external dependencies—pure client app.
Be Detailed, Yet Structured
• Call out shared scripts (e.g., Saving.gd is a shared service).
• Plugin as “attaching” to UI container nodes rather than being in the Scene‐tree itself.