PortableGL
learn-wgpu
Our great sponsors
PortableGL | learn-wgpu | |
---|---|---|
7 | 75 | |
919 | 1,378 | |
- | - | |
9.0 | 8.0 | |
25 days ago | 14 days ago | |
C | Rust | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PortableGL
-
Olive.c: a simple graphics library that does not have any dependencies
Yeah PortableGL will never be completely fully featured, not even for OpenGL 3.3 since I'll definitely never do the geometry shader and probably not the transform feedback. But specifically it'll never have the earlier immediate mode stuff, or some of the big 4.0 stuff like the tessellation shaders. I have been meaning to add the DSA functions where they make sense. They'd be really simple to implement.
Actually a few days ago someone sent me a pull request adding an interesting project to my README
https://github.com/rswinkle/PortableGL/commit/e0652b4dff266d...
So now if I were to try to sum up all the OpenGL software implementations I can think of,
TinyGL (and modern improved forks) = OpenGL 1.1-1.3 ish
-
Hacker News top posts: Dec 31, 2021
PortableGL: An implementation of OpenGL 3.x-ish in clean C\ (23 comments)
-
PortableGL: An implementation of OpenGL 3.x-ish in clean C
Not entirely related to the subject of OpenGL, but I really like how the author has decided to lay out this project. It's pretty hard to beat the convenience of a single header (or single header/single source) distribution for C libraries, but library development gets progressively harder as the project gets bigger as more code is added to the (usually hard to navigate) header file. Here, the author does their development with multiple files as one normally would, but when a new version is released they run the generate_gl_h[1] script that concatenates everything into a .h file for distribution. Simple yet flexible! This is also how SQLite[2] distributes its builds. It's a pattern that I'm using myself in some unreleased projects.
[1] https://github.com/rswinkle/PortableGL/blob/master/src/gener...
- Any OpenGL implementations for vector-drawing hardware?
learn-wgpu
-
Practicing Rust, Learning Bevy, Creating a WASM Snake Game for the Browser
Nice.
Speaking of Snake game, if you want to go even deeper, you can try to use the wgpu crate to combine Rust and WebGPU to write everything from scratch. Here is the tutorial:
https://sotrh.github.io/learn-wgpu/#what-is-wgpu
I once wrote a code editor with wgpu, from font rendering to char/line state management (very rough) for music live coding:
https://github.com/glicol/glicol-wgpu
It runs in browsers, even including Safari!
- Please review my ECS geospatial engine so far
- Help me get started with 3D graphics in Rust
-
Realtime Ray Marching implemented with Rust and wgpu
https://sotrh.github.io/learn-wgpu/ This is probably the best resource out there for learning wgpu specifically. If you're unfamiliar with graphics, the learnopengl one is good. If you've got experience though, jumping right into that one is a shout or looking at some vulkan ones as they're pretty similar in terms of architecture.
-
Is it possible and realistic to learn independent of an API?
- https://sotrh.github.io/learn-wgpu
-
What would be a good project structure/ design for a game engine using WebGPU?
Most of The WGPU I learnt is from https://sotrh.github.io/learn-wgpu/ but it doesn't really talk about designing n stuff, I thought of checking out the source code for Bevy or even games like veloren. But well, their codebases are pretty big to get started in the first place.
- Learn Wgpu
-
Learning OpenGL before wgpu?
So I was wondering if opting for option 1 would be better to begin with. OpenGL has a much bigger community and wgpu only has its documentation which I hear is not quite up there yet. There is this excellent tutorial for wgpu that I read through, but it seems like wgpu can be a lot more complicated than starting with OpenGL.
-
Getting started with computer graphics with Rust
I started with wgpu tutorial (https://sotrh.github.io/learn-wgpu/) since I like the idea of portability and it's a Rust-first library, but it seems I'm missing some foundations of how CG works in general: the code is given, a little of explanation like it assumes I already know something, maybe I'm wrong, but I wish there was a longer explicit version.
-
Trying to learn wgpu
If you haven't seen it: https://sotrh.github.io/learn-wgpu/ is a good introduction that will explain most of what you asked, then can refer to rend3d or bevys renderer to see how a render graph works.
What are some alternatives?
tinygl - TinyGL : a Small, Free and Fast Subset of OpenGL*
ash - Vulkan bindings for Rust
tinyraytracer - A brief computer graphics / rendering course
glium - Safe OpenGL wrapper for the Rust language.
GLM - OpenGL Mathematics (GLM)
SDL - Simple Directmedia Layer
tinyrenderer - A brief computer graphics / rendering course
winit - Window handling library in pure Rust
rusterizer - Bare-bones software renderer written in Rust
egui - egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
RetroFPSStudio - The public repo of Retro FPS Studio (RFS), for educational reading and not for reuse. See license.
wgsl-mode - Emacs syntax highlighting for the WebGPU Shading Language (WGSL)