How javicone/galeriafotos works
Project type and purpose
• This is a single‐repo Godot Engine (v4.x) 3D application written in GDScript.
• Purpose: take a folder of user-provided images, analyze their dimensions, and procedurally build a first-person 3D art gallery with correctly sized picture frames.
File structure
• Top level:
• project.godot – Godot project entry
• .gitignore*/.gitattributes – source control metadata
• README.txt – project description
• Camera3D.gd, ControladorCuadros.gd, controlador_imagenes.gd – standalone scripts
• addons/… – Godot Git Plugin for editor integration
• “assets/” & “textures/” – 3D models and texture source files
• “escenas/” – all .tscn scene files and corresponding GDScript controllers
• “personaje_asset/” – imported rigid character body plugin with example scenes
• “example/” – minimal example scene to demonstrate character controls
Extract key insights from the README
• The user drops images into a folder → system auto-analyzes → gallery built in real time.
• First-person navigation (WASD + mouse).
• Modular, dynamic gallery construction; image proportions drive frame sizes.
Main components
a. User Input (File System)
b. Image Loader & Analyzer (controlador_imagenes.gd)
c. Gallery Builder / Scene Controller (ControladorCuadros.gd, ControladoEscenas.gd)
d. Godot Scene Graph (escenas/*.tscn)
e. Player Controller (Camera3D.gd + personaje_asset scripts)
f. Asset Manager (loading assets/models/textures)
g. Render Engine (Godot Core)
h. Editor Addon (godot-git-plugin) – development-time only
Relationships & data flow
• User drops images → Image Loader reads files → Analyzer extracts width/height → Gallery Builder spawns frame nodes with proportional scaling → Scene Graph updates → Render Engine draws frames, floor, walls → Player Controller handles user input & camera moves → continuous Render loop.
• Asset Manager services the Builder and the Player by loading meshes, materials, textures.
• Editor Addon plugs into Godot Editor, does not participate at runtime.
Architectural patterns & principles
• Modular scene-based architecture: each functional area lives in its own scene (.tscn) + script.
• Separation of concerns:
• File I/O & analysis (controlador_imagenes.gd)
• Scene construction (ControladorCuadros.gd)
• Input handling (Camera3D.gd + character plugin)
• Event/driven initialization: on game start the loader fires, then builder subscribes.
Detailed checklist
• .tscn scenes are represented (mainEscena, paredCuadro, suelo, etc.) under “Scene Graph.”
• Asset folders feeding into an Asset Manager block.
• Feedback loop: user input → camera movement → continuous rendering.