How bardsoftware/ganttproject works
Main Components
• Presentation (UI) Layer:
– This module contains desktop-specific code (see directories such as “biz.ganttproject.desktop” and “ganttproject/src/main/java/biz/ganttproject/app”).
– It includes the main entry point (for example, “GanttProjectFxApp.kt”, “GanttProject.java”) and the various UI panels, dialogs, and charts.
• Core Business Logic Layer:
– Modules in “biz.ganttproject.core”, “biz.ganttproject.task”, “biz/ganttproject/customproperty”, “biz/ganttproject/chart” and “biz/ganttproject/storage” hold the primary scheduling algorithms, dependency processing, task hierarchy, calendar & timeline calculations, and persistence.
– This layer encapsulates the functional “engine” behind Gantt chart rendering, resource assignment, cost calculations, and schedule recalculations.
• Import/Export Modules:
– Organized as separate packages such as “biz.ganttproject.impex.ical”, “biz.ganttproject.impex.msproject2”, “ganttproject/src/main/java/biz/ganttproject/impex/csv”, “org.ganttproject.impex.htmlpdf” and others.
– These modules manage data serialization and conversion to/from formats like CSV, MS Project files, HTML/PDF documents, etc.
• Cloud and Collaboration Components:
– Found in “cloud.ganttproject.api” and “cloud.ganttproject.colloboque”, this part implements project file updating, remote API interactions (e.g., PostgreStorageApi.kt), and collaboration.
– They likely talk to a database and use web service protocols.
• Build & Packaging Infrastructure:
– “ganttproject-builder” contains Ant/Gradle build scripts, packaging for different platforms (Linux, macOS, Windows), installer scripts and property files.
– Also note the Gradle build system overall (build.gradle files at multiple levels).
• Auxiliary & Plugin System:
– The presence of plugin.xml files in multiple modules implies that there is dynamic or static plugin support.
– External libraries (“biz.ganttproject.app.libs”, “ganttproject/lib”, “biz/ganttproject.mxgraph”, etc.) provide additional reusable functionality such as UI widgets, CSV processing, and PGP or cryptography support.
Architectural Relationships and Data Flow
• The build & packaging system is separate from the runtime components, but it has dependencies on all of the above modules to generate the final executable/distribution. Represent it as an external process that “assembles” the modules.