How tomas-dorado/gestor_clientes works
Project type and purpose
• This is a Python desktop application (“Gestor de Clientes”) that provides a graphical interface to manage a client list.
• It uses tkinter for the GUI, a custom linked‐list data structure for in‐memory operations, and persists data in a CSV file.
File structure
• Top-level:
• ui.py – tkinter‐based GUI entrypoint
• requirements.txt – dependencies (pytest, tk)
• tests/ – unit tests for database layer
• Datos/clientes.csv – the persistent datastore
• Module “Gestor_Clientes/”:
• run.py – application runner (initializes GUI)
• menu.py – controller logic for menu actions
• database.py – CSV‐based CRUD operations
• Nodo.py – linked‐list node definition
• helpers.py – utility functions on the linked list
• config.py – application configuration (file paths, settings)
Extract insights from the README
• Emphasizes four key components: GUI (tkinter), custom data structure (linked list), CSV storage, and client CRUD operations.
• No mention of external services or databases—everything is local.
Main components
a. GUI Layer (tkinter)
b. Controller/Business Layer (menu.py, helpers.py)
c. Data Structure Layer (Nodo.py – the linked list)
d. Persistence Layer (database.py writing to Datos/clientes.csv)
e. Configuration (config.py)
Relationships & data flows
• The GUI Layer sends user actions (Create, Read, Update, Delete) to the Controller.
• The Controller manipulates the in‐memory linked list via helpers and Nodo.
• For each change, the Persistence Layer serializes/deserializes the linked list to/from clientes.csv.
• Configuration settings (file paths, CSV schema) flow into both Controller and Persistence layers from config.py.
• Tests import database.py and helpers/Nodo to validate correctness.
Architectural patterns & principles
• MVC‐like separation:
• View: ui.py + tkinter widgets
• Controller: menu.py + run.py
• Model: linked list (Nodo.py, helpers) + persistence (database.py)
• Single responsibility per module: config, data node, persistence, UI.
• Local file‐based persistence—no remote services.
• Clear component labels (e.g., “tkinter UI”, “Linked List Model”)
• Arrowheads showing direction of calls/data flow