How mr-mod/yaslicer works
Project type and purpose
• YaSlicer is a native C++ command-line tool (“Yet Another Slicer”) that generates 2D image slices (PNG) of 3D STL models for DLP/SLA 3D printers.
• It consists of a reusable “Common” static-library module plus a “Slicer” executable that implements GPU-accelerated rendering and multicore optimizations.
File structure
• Top-level directories:
• Common/ – cross-platform utilities, math, file I/O, image writing, rasterization and performance timers.
• Slicer/ – application code (main, CLI parsing, platform-specific GL context, renderer, shaders, job export).
• Solution & build scripts: Tools.sln, make.sh, .vcxproj files for Visual Studio, vcpkg integration.
• Platform abstraction: GlContext*.cpp/h for ANGLE (Windows), D3D9/11, Raspberry Pi, X11.
• Dependencies: Boost (CLI args, threading), glm (math), glew (GL loader), libpng (image output), ANGLE (D3D-backed GL).
Extract README insights
• Core features: fast slicing, large STL support, antialiasing toggle, printer profiles, simulation mode, PNG output, low dependency count.
• Requirements: Windows 64-bit, D3D9/11 drivers, Visual Studio 2017 + vcpkg.
• Usage: slicer.exe CLI → produces PNG slices and optional job files.
Main components & interactions
a. Components:
1. CLI Frontend – parses arguments, loads STL.
2. Model Loader (Common/Loaders) – reads binary STL into mesh data.
3. Geometry & Cache (Common/Geometry, Common/CacheOpt) – builds slice geometry, optimizes reuse.
5. GL Context Layer (Slicer/GlContext*) – abstracts platform-specific OpenGL/D3D initialization.
6. Shader Pipeline (Slicer/Shaders.h) – GPU programs for slicing and antialiasing.
7. Image Writer (Common/PngFile) – handles PNG output.
8. Job Exporter (Slicer/Utils) – optional Envisiontech job file generator.
9. Performance & Logging (Common/PerfTimer, Common/ErrorHandling).
10. External Dependencies – Boost, glm, glew, ANGLE, libpng.
b. Relationships & Data Flow:
• CLI Frontend → invokes Model Loader → mesh → Geometry & Cache → Renderer Core → submits to GL Context → Shader Pipeline → framebuffer → Image Writer → disk.
• Job Exporter listens to slice events to create job files.
• PerfTimer wrappers around heavy operations (load, render, write).
• ErrorHandling sits at subsystem boundaries.
c. Architectural patterns & principles:
• Layered architecture: Core logic depends on Common utilities; Slicer application sits above Common.
• Abstract factory / strategy for GL contexts (platform-specific implementations behind a common interface).
• Single responsibility in modules: loading, geometry, rendering, output.
d. Key technologies & libraries:
• C++17 (or C++14), Boost threads/CLI, glm for vector/math, OpenGL (via ANGLE/D3D), glew for GL extension loading, libpng for output.