How teddyara/wyvern works
Project type and purpose
• It integrates windowing (GLFW), extension loading (GLEW), a real‐time renderer, basic physics, UI widgets, and an undo/redo command system.
• Its likely use case is authoring or manipulating a 3D world in real time.
File structure
• Top-level directories:
• Wyvern/Dependencies – external libraries (GLEW, GLFW) for OpenGL context, extensions, and input
• Wyvern/src – all C++ source: divided into subsystems
• Wyvern/Debug, x64/Debug – build outputs and assets (shaders under assets/)
• Sub‐folders under src expose architectural layers:
• core classes (Application, Window, Input, World, Transform, Viewport, Camera)
• renderer (buffers, shaders, framebuffers, skybox, debug overlays)
• physics (colliders, physics engine, hit detection)
• ui (widgets, title bar, toolbars, menus, zone layouts)
• cmds (Command pattern, concrete commands + Undo/Redo, HistoryManager)
• behaviours (pluggable scene behaviours, e.g., camera control)
• Presence of .sln / .vcxproj indicates a Visual Studio solution.
README for additional insights
• No architecture sections provided. All domain insights must come from code organization.