How smartqubit/projectlibre works
Main Architectural Layers/Modules
• Core Module (projectlibre_core): Contains the domain and business logic such as task management, scheduling (including PERT, earned value costing, resource and calendar management), hierarchical structures, and time management. This layer represents the “engine” of the application.
• Exchange Module (projectlibre_exchange and projectlibre_converters within openproj_exchange): Responsible for import/export capabilities from formats like MSPDI, MPX, Primavera, and other industry standards. It adapts external data to the internal core data model.
• UI Module (projectlibre_ui): Provides the graphical user interface, including the Gantt chart, ribbon-based interactions, dialogs, charts, and other visualization components. It interacts directly with the core to display project management data and receive user commands.
• Reports Module (projectlibre_reports): Handles report generation and visualization, likely relying on the data provided by the core and presenting it in various formats.
• Supporting Libraries and Third-Party Components: Numerous libraries, as seen in the file tree (for instance, mpxj packages for handling imported/exports, Apache Batik for SVG, and other utilities), which support particular functionality in data transformation, rendering, or file operations.
• The UI layer communicates with the core module by issuing commands (e.g., update tasks, alter schedules, open project files) and receiving data (project state, scheduling results, resource information).
• The exchange module interacts with the core layer for data persistence and conversion. For example, an “importer” may take an external file, convert it using specific converters (like the MPX or Primavera converters) and then call the core business logic to create or update a project’s state.
• The reports component pulls data from the core and may also integrate with exchange utilities to generate, format, and display reports (such as Gantt charts or earned value costing reports) in printed or electronic form.
• Libraries and utility packages provide domain-specific functions (e.g., scheduling algorithms, time utilities, resource allocation routines) that are invoked by core logic and even by some UI components.
Architectural Patterns/Principles Used
• Layered Architecture: There is a clear separation between the presentation (UI), business logic (core), data import/export (exchange), and reporting functionalities.
• Modular Organization: The project is divided into separate sub-projects/directories, each handling a distinct responsibility.
• MVC-Like Pattern in UI: Within the UI module, aspects such as dialogs, renderers, and controllers are present, likely providing a separation of model (project data), view (Gantt charts, dialogs) and control (user interactions and menu actions).
• Use of Design Patterns: The codebase suggests use of patterns such as Factory (for creating nodes in the hierarchy, fields, converters), Observer (for UI-listeners and event management), and perhaps Adapter (in the exchange modules to interface with various file standards).