How ronytic/colegio works
Main Components
a. Presentation Layer (Frontend):
• This includes the PHP pages (the many index.php files in each module directory), HTML, CSS (in folders like css, imagenes, img) and JavaScript (in js, login/js, and assorted plugin directories).
• It covers both desktop and mobile layouts since the README emphasizes responsive adaptation.
b. Application/Business Logic Layer:
• The core business logic is distributed in the “class” and “clases” directories that contain PHP classes for students, teachers, attendance, tuition, scheduling, notifications, etc.
• There are also module-specific controllers within folders such as agenda, alumno, asistencia, docente, curso, notas, etc.
c. Data Access & Integration:
• Files like basededatos.php, class/bd.php, configuracion.php, and database configuration helpers are used to manage database connections and queries.
• External libraries (e.g., PHPExcel in “notas/notasexcel” and phpqrcode in “funciones/phpqrcode”) support functionalities like report generation and QR code creation.
d. Auxiliary/External Services:
• The SMS subsystem (folder “sms”) handles messaging, while modules like “seguridad” offer security, backup, and logging functionalities.
• There are also integration points for printing/impression (in “impresion”) and exporting (in “exportar”, “csv”).
Out Relationships and Flow
a. Frontend Clients (browsers on desktops or mobile devices) interact with the backend via PHP pages and JavaScript.
b. Each module (e.g., “agenda”, “alumno”, “docente”, etc.) encapsulates functionality: form submissions, report generation, data display and update.
c. The Presentation Layer sends HTTP requests to module-specific PHP scripts that call methods on the business logic classes.
d. The business logic layer uses database connectors and configuration files to perform CRUD operations on the underlying database.
e. External libraries (for QR codes, Excel export, etc.) are invoked by various modules when generating documents or reports.
f. Some modules under “seguridad” or “rastreo” handle logging, backups, and auditing, feeding back into the system monitoring side.
Architectural Patterns or Practices
a. Though not strictly following a modern MVC framework, the design separates responsibilities – views (PHP/HTML/CSS/JS) are located in module directories, while data models and business logic are in the “class” and “clases” folders.
b. The modular structure (each folder like “agenda”, “alumno”, etc.) represents functional separation akin to micromodules in a monolithic architecture.
c. There is heavy use of include/require patterns to share common elements like header (cabecera.php) and common functions (funciones/funciones.php).