How ustc-cg/ustc_cg_24 works
1. Two major frameworks (Framework2D and Framework3D) that seem to act as libraries or reusable components for rendering and interactive assignments.
2. A large number of homework assignments (organized under Homeworks), which make use of these frameworks (and sometimes have their own demos, experiments, and tests).
3. Supporting “Softwares” and documentation directories to help students set up the development environment (e.g., CMake configurations, Git instructions, etc).
Main System Components
• Framework3D: A more complex system with several libraries (GCore, RCore, SCore), GUI components (including a node-based editor and USD view engine), and a modular “Nodes” system for 3D graphics. There are clear separations for core components (materials, mesh operations, transformations) and rendering pipelines (render delegate, render passes, and shader modules).
• Homework Assignments: These directories (with multiple assignments, e.g., mini_draw, image_warping, poisson_image_editing, character_animation, etc) are self-contained projects that use the provided frameworks to achieve a range of computer graphics tasks. They are also structured with their own CMake files and sometimes include sample data, documentation, and demos.
• Software and Documentation: Contains supporting material for setting up build environments (CMake, Git, Visual Studio) and guides on using Clang-uml and project conventions.
Detail Relationships and Interactions
• Third-party dependencies are integrated at the framework level (both “third_party” and “external”), and the CMake build system ties them together. Diagramming the build configuration flow (from CMakeLists.txt in the root and within each project) can help highlight how components are compiled and linked.
Architectural Patterns and Design Principles
• Clear dependency management with CMake: Illustrate how the build and configuration system ties together the various modules and external libraries.
Relevant Technologies and Libraries
• C++ as the implementation language, with heavy use of CMake for build configuration.
• OpenGL and shader-based rendering (indirectly indicated via use of GLAD, GLFW, and shader sources in Framework3D).
• ImGui and custom node-editing interfaces in the GUI modules.
• External libraries like Eigen, OpenMesh, stb_image, and various others that provide mathematical, rendering, and utility functions.