GLFW

[dandymcgee]

Has anyone here heard of GLFW before? Does anyone use it along-side OpenGL? If so, why?

Personally I'm still leaning towards SDL, partly because I already know a good portion of it, and partly because
of it's support for handling many things in addition to application windows.

NOTE: I don't really know what I'm talking about, just curious if anyone uses something other than SDL to
handle windows, input, sound, and networking with OpenGL.

[JS Lemming]

I prefer SFML to SDL.

[RyanPridgeon]

I think SDL is the norm around here, so if you want more help here it's probably best that you stick to that. Just learn how to init OpenGL in SDL, then use common sense and logic to learn from standard OpenGL tutorials.

Heck... the PC build of ES uses SDL

[Ginto8]

I prefer SFML to SDL.

one thing though... SFML uses std::string, which is more bloated than falco's mother. SFML is easy to use (for the most part), but if you want a high-efficiency game engine (like the ES engine), SFML is just going to weigh you down.

Just thought I'd throw that out there.

[dandymcgee]

Yeah, I think I'll stick with what I already know for now. Maybe sometime in the future I'll check out GLFW or SFML and compare them for myself.

Note to future repliers:
My intention was not to start another SDL vs. SFML thread, so if you have any input on GLFW feel free to reply, otherwise post your opinions elsewhere. Thanks.

[avansc]

I prefer SFML to SDL.

one thing though... SFML uses std::string, which is more bloated than falco's mother. SFML is easy to use (for the most part), but if you want a high-efficiency game engine (like the ES engine), SFML is just going to weigh you down.

Just thought I'd throw that out there.

okay, thats fat joke was not that funny the first time, so i think its time you lay it to rest.
secondly.. how fat is std::string really??? and i dont think its goinf to affect performance that much.