How czechbluebear/noneuclidean works
Project type and purpose
• NonEuclidean is a native C++ Windows demo application and rendering engine built on OpenGL.
• It provides a “non-Euclidean” demo environment where the user can move around and switch between rooms, featuring a platform abstraction layer (SDL2 or Win32), rendering, input, physics, scene management, and a resource loader.
File structure
• Top-level files:
• NonEuclidean.sln / Makefile – build system for Visual Studio or make.
• README.md / .gitignore / LICENSE.
• NonEuclidean/ folder breakdown:
• Platform layer: Engine_SDL2.{cpp,h}, Engine_Win32.{cpp,h}
• Core engine and main loop: Engine.{cpp,h}, Main.cpp, GameHeader.h, Timer.h, FrameBuffer.{cpp,h}
• Input subsystem: Input.{cpp,h}
• Resource loading: Resources.{cpp,h}, Mesh.{cpp,h}, Texture.{cpp,h}
• Shaders: Shaders/*.vert & .frag
• Scene & levels: Scene.h, Level1–Level6.{cpp,h}, Floorplan.h, House.h, Tunnel.h, PillarRoom.h, etc.
• Physics & collision: Physical.{cpp,h}, Collider.{cpp,h}
• Camera and rendering support: Camera.{cpp,h}, Shader.{cpp,h}
• Assets on disk: Meshes/*.obj, Textures/*.bmp
Key insights from the README
• Written in C++ with OpenGL, expects GLEW in the root directory.
• Uses mouse & keyboard for navigation and room switching demos.
Final advice
• Essential architectural elements: platform abstraction, main loop, subsystems, asset flow, and rendering pipeline.
• Avoid over-splitting; show each major function as its own component and connect them clearly.