HackerTrans
TopNewTrendsCommentsPastAskShowJobs

colleagueRiley

no profile record

Submissions

[untitled]

1 points·by colleagueRiley·2 anni fa·0 comments

[untitled]

1 points·by colleagueRiley·3 anni fa·0 comments

Show HN: RGFW – Super Lightweight Single-Header GLFW Alternative

github.com
4 points·by colleagueRiley·3 anni fa·0 comments

RFont – modular easy-to-use single-header font library, OpenGL modern and legacy

github.com
1 points·by colleagueRiley·3 anni fa·1 comments

RGFW – Super Lightweight Single-Header GLFW Alternative

github.com
2 points·by colleagueRiley·3 anni fa·1 comments

comments

colleagueRiley
·anno scorso·discuss
I made RGFW, which calls Objective-C MacOS's API functions in Pure C.

BUT I would also like to mention a project a friend and I made called Silicon. Silicon is a single-header C wrapper around the Pure-C calls, which makes it far more convenient to use.

https://github.com/eimamei/silicon

I no longer use it in RGFW because I wanted to remove the extra dependency.
colleagueRiley
·2 anni fa·discuss
No lol
colleagueRiley
·2 anni fa·discuss
Nope, most people using it know how to link and compile libraries. :)
colleagueRiley
·2 anni fa·discuss
Well for one you're able to easily use macros to customize features you want and don't want. Plus "forcing me to figure out the specific XYZ_IMPLEMENTATION" is a big of a weird compliant. You could say the same thing about linking a library. Besides, it's not hard to figure out and is usually one of the first lines of the file.

The single-header format also gives you MORE ways to compile the library and control which features to use or not use.
colleagueRiley
·2 anni fa·discuss
Oh, I wasn't sure if that was you :)

Thanks for the advice, I'm a little worried about breaking compatibility with compilers that don't support stdint. But if it's standard for C99 thing then sure.
colleagueRiley
·2 anni fa·discuss
I use those by default although I read that MSVC's support for those are iffy. I'm pretty sure STB does the same thing for the same reason.

Source: https://handmade.network/forums/articles/t/7138-how_to_write...
colleagueRiley
·2 anni fa·discuss
:( That's disappointing, but I understand.
colleagueRiley
·2 anni fa·discuss
Yes, because MSVC may or may not have stdint.h
colleagueRiley
·2 anni fa·discuss
Okay, thank you.
colleagueRiley
·2 anni fa·discuss
https://github.com/SasLuca/glfw-single-header/blob/master/ex...
colleagueRiley
·2 anni fa·discuss
Minimal refers to the code itself.

GLFW's codebase is ~10MB while RGFW's is about ~300kb. But RGFW tries to support nearly everything that GLFW supports.
colleagueRiley
·2 anni fa·discuss
I test Windows mainly with MINGW, that might be an issue with MSVC. Feel free to report the issue on the github repository.

I'm pretty sure windows uses "long" for 64 bit but linux uses "long long" for 64 bit
colleagueRiley
·2 anni fa·discuss
Try putting GLFW's source code into one file and then compile it. That will take at least a few seconds, RGFW compiles in less than a second.

Where's the bloat? :)

https://github.com/SasLuca/glfw-single-header/blob/master/ex...
colleagueRiley
·2 anni fa·discuss
Even then, that's what GLFW is designed to do, and it's entire source code is still far larger than RGFW's.
colleagueRiley
·2 anni fa·discuss
I just have the Makefile do the code generation, it would be annoying for the user, but they can complain to Wayland if they don't like it.
colleagueRiley
·2 anni fa·discuss
Sure, but none of these are true alternatives because they are missing a lot of features that libraries like GLFW or RGFW have.

(They may be good alternatives for certain use-cases)
colleagueRiley
·2 anni fa·discuss
- Better API design - Not being experimental after 11 years

I think that Wayland actually has some steps in the right direction, but overall I don't think it's actually a very good alternative. It's way more low-level than X11 and a lot of higher level features, like window decorations, are not even officially supported.
colleagueRiley
·2 anni fa·discuss
We'd be at the same spot, single-header files are still useful.

A single-header file is not a 'full-sized' library compressed into one file it's codebase is designed to actually be minimalist. Many libraries have single files that are the same size as their alternative single-header.
colleagueRiley
·2 anni fa·discuss
It is a single-header library in terms of the format, yes. But it is also not designed to be a single-header library, unlike an STB-style library.

Nuklear is a full-sized library that can be compiled into and used as one file. However, RGFW and STB are designed to be lightweight and minimalistic. That's the distinctive part of single-header libraries, also known as STB-style libraries.

To be clear, I don't mean this to hate on Nuklear, it's a cool UI library, but its design doesn't match the single-header format.
colleagueRiley
·2 anni fa·discuss
As far as I know, RGFW is the only minimal windowing of its kind. I guess I would suggest either targeting XWayland or using GLFW.

The Wayland API itself also really sucks to work with, even more so than Xlib....

But, RGFW's Wayland support will probably be improved in the future. :)