the-ray-tracer-challenge-racket
minifb
| the-ray-tracer-challenge-racket | minifb | |
|---|---|---|
| 1 | 10 | |
| 2 | 924 | |
| - | - | |
| 1.7 | 2.8 | |
| 11 months ago | 8 months ago | |
| Racket | C | |
| - | 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.
the-ray-tracer-challenge-racket
-
The joy of building a ray tracer, for fun, in Rust
Yes, the book has both implementations of the required functions (for all the complicated ones you need) and tests all written in pseudocode.
The book is really good. I have a half-finished implementation in F#, and what I find striking is just how close the F# code is to the pseudocode. I have also started an idiomatic port to Racket but have only done the tuples, vector, and point implementations so far. I need to pick these up again.
https://github.com/bmitc/the-ray-tracer-challenge-fsharp
https://github.com/bmitc/the-ray-tracer-challenge-racket
I mean, check this out: https://github.com/bmitc/the-ray-tracer-challenge-fsharp/blo...
I have also worked through pieces of Ray Tracing in One Weekend (what was referenced in this post). They get you going much faster, but the code is written in C++. I found the translation to a functional style was harder (was just using Racket and F#'s mutability features), whereas the way The Ray Tracer Challenge is laid out and specified, I found it much easier to translate to an idiomatic functional style.
minifb
-
creating a free, fast and simple digital painting software (not planned UI/UX yet)
I would also recommend looking into SDL2 or MiniFB for cross-platform support, as not everyone uses X11.
- Minimal Cross-Platform Graphics
- MiniFB: Cross-Platform Rendering Library
-
graphics library for setting pixels on screen
MiniFB is what you want for this.
-
Best way to write a cross-platform graphical program in C while using only bare minimum third-party libraries?
MiniFB maybe?
-
eBook Gentle Introduction to Assembly Language (AARCH64)
But you can have a skeleton program that sets up framebuffer for you (e.g. with minifb or TIGR), then link it that skeleton with your code (in assembly or whatever you prefer).
- The joy of building a ray tracer, for fun, in Rust
-
native web-api graphics (live, not image)
I also saw minifb, which seems like a really to-the-point way to get a buffer I can draw to., so I guess I will go in that direction (rust lib, make FFI bindings for deno, etc.)
-
Can I make graphics without any libraries?
If you just want to push pixel data to a frame buffer then I can highly recommend minifb. MIT licensed, Supports a lot of platforms, and it’s about as simple as you can get. It also handles input if you need it, too.
-
Best libraries for making a raycaster in C
I think this library will fit your goals: https://github.com/emoon/minifb
What are some alternatives?
lisp-sandbox
winit - Window handling library in pure Rust
the-ray-tracer-challenge-fsharp - F# implementation of the ray tracer found in The Ray Tracer Challenge by Jamis Buck
SDL - Simple Directmedia Layer
tev - High dynamic range (HDR) image viewer for graphics people
raytracer-exp - A simple raytracer built as an exercise to learn some Rust
RayTracingWeekend.jl - Ray Tracing in a week-end, implemented in Julia
microui - A tiny immediate-mode UI library
libtcod - A collection of tools and algorithms for developing traditional roguelikes. Such as field-of-view, pathfinding, and a tile-based terminal emulator.
deno-canvas - Canvas API for Deno, ported from canvaskit-wasm (Skia).
deno_sdl2 - SDL2 module for Deno