How acaudwell/gource works
Project type and purpose
• The README confirms its domain (version control visualization), key features (OpenGL rendering, multiple VCS support, extensive CLI options), and its modular design around log parsing, data modeling, rendering, and user interaction.
File structure
• Top‐level directories:
• cmd/ – platform‐specific launchers (Windows batch and UNIX shell)
• contrib/ – utility scripts (e.g., svn-gource.py)
• data/ – runtime assets (fonts, shaders, example files)
• dev/ – packaging and build scripts (tar, NSIS, etc.)
• m4/ and configure.ac, Makefile.am, autogen.sh – autotools build system
• src/ – all C++ source code, subdivided into:
– formats/ (VCS adapters: git, svn, hg, bzr, cvs2cl, custom)
– core/ (DirNode, file tree data structures)
– tinyxml/ (embedded XML parser)
– test/ (unit tests)
– other helpers (action, bloom, caption, camera, spline, slider, key, logmill, main, user, textbox)
• scripts/ – post‐processing scripts (e.g., gource-ps.pl)
• resources/ – source images for assets
• tests/ – input logs and images for automated testing
• Configuration and packaging: configure.ac, automake files, .gitattributes, .gitmodules, etc.
README for additional insights
• Dependencies: OpenGL (GL, GLU, GLUT), FreeType (for fonts), C++11, autotools.
Final advice
• Be exhaustive: list each formats/* adapter, each rendering shader stage, each input handler.
• Flow from “gource [options]” all the way to the OpenGL swap‐buffers call.
• Non-obvious dependencies (e.g., TinyXML used by caption parsing).