How enekgonztolosaldea/alaiktomugi works
Project type and purpose
• This is a Java desktop (Swing/GForms) application (“praktikak”/“alaiktoMugi”) that manages users (“Erabiltzaileak”) and drivers (“Gidariak”) data in a MySQL database. It uses the Java module system, JGoodies Forms for UI layout, and JDBC (mysql-connector) for data access.
File structure
• Top-level folders:
• praktikak/src – Java source
– datubasea – data-access layer (DBGestorea, DB_Erabiltzaileak, DB_Gidariak)
– praktikak – UI package (MenuNagusia, ErabiltzaileLehioa, GidariLehioa, HistorialErabiltzaileLehioa)
– module-info.java – Java 9+ module descriptor
• praktikak/lib – external JARs (MySQL connector)
• praktikak/com.jgoodies.*.jar – JGoodies libraries
• praktikak/config/config.properties – DB connection settings
• praktikak/bin – compiled classes
(minimal) README
• It only lists the project name (“alaiktoMugi”), confirming this is a small standalone client.
Main components & their relationships
a. Presentation/UI layer
• MenuNagusia (main menu)
• ErabiltzaileLehioa (user window)
• GidariLehioa (driver window)
• HistorialErabiltzaileLehioa (user-history window)
– Uses JGoodies Forms for layout
b. Business/Data-access layer
• DBGestorea (central DB manager)
• DB_Erabiltzaileak (user DAO)
• DB_Gidariak (driver DAO)
– Loads config.properties for connection params
c. External service
• MySQL database server
– Accessed via mysql-connector-j JDBC driver
d. Libraries/frameworks
– JGoodies (UI)
– JDBC (mysql-connector)
Architectural patterns/design principles
• 2-tier architecture: desktop client ↔ database
• Layered separation:
– UI layer calls business/Data-Access layer
– Data-Access layer interacts with DB via JDBC
– Configuration externalized in properties file
• Modularization via module-info.java