How xaos-project/xaos works
Project type and purpose
• XaoS is a native C++/Qt “full-stack” desktop application (with an optional web version) for real-time interactive fractal zooming.
• The README describes its core: smooth zooming into fractals, multiple fractal formulas, coloring modes, autopilot, i18n, packaging and web deployment.
File structure
• Top level:
• .github + workflows → CI/build definitions
• CMakeLists.txt, XaoS.pro → build system (CMake & QMake)
• src/ → primary C++ code, subdivided into:
– engine/ (fractal computation core)
– ui/ (Qt widgets, main window, dialogs, resources)
– util/ (image I/O, threading, palettes, error handling)
– formeval/ and sffe/ (specialized math libraries/plugins)
• i18n/ and catalogs/ → translation sources (.ts) and compiled catalogs (.cat)
• installer/ and tools/ → packaging scripts, installer definitions
• examples/, tutorial/, doc/ → data and documentation
• Patterns:
• Layered architecture (UI → Engine → Utility)
• Plugin-like math modules (formeval, sffe)
• Resource bundling (Qt .qrc, .ts/.cat for i18n)
• Automated builds and packaging (GitHub Actions, scripts)
README for additional insights
• Confirms Qt Widgets usage, cross-platform targets, web app variant since v4.3
Elements
• Component blocks labeled: “UI Layer,” “Engine Layer,” “Math Plugins,” “Utility Layer,” “Data/Resources,” “Build & Packaging,” “Web App”
• User Input → UI → Engine → Utility → Engine → UI → Display
• Source files → Build System → Binaries & Resources → Installer/Web
• .ts files → Qt Linguist → .cat → UI
• UI components (blue), compute core (green), utility (yellow), data/resources (orange), build pipeline (gray), external/web (purple)
Final advice
• Be detailed: break down engine submodules (filters, zoom, formulas), UI subcomponents (main window, fractal widget, dialogs)
• Don’t overthink: represent every distinct directory/component in src/ and tools/ as its own block or sub-block to capture completeness