Viewing profile — colleagueRiley

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 wr…

No lol

Nope, most people using it know how to link and compile libraries. :)

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 com…

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…

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/…

:( That's disappointing, but I understand.

Yes, because MSVC may or may not have stdint.h

Okay, thank you.

https://github.com/SasLuca/glfw-single-header/blob/master/ex...

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.

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…

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.c…

Even then, that's what GLFW is designed to do, and it's entire source code is still far larger than RGFW's.

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.

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…

- 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…

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…

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 t…

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 …

X11 needs a real alternative :(

Sure, but the library is also relatively small, so it compiles quickly. Although if you want to you can compile it on its own. It's also possible to compile it on its own using `gc…

I'm aware of the errors for the micro UI (on the web), it's something I plan on looking into soon!

That's something I plan on looking into at some point. I'm unsure if I want that in the main version or a separate branch for embedded devices. It's low priority though because my …

Thanks :)