FLTK is really neat and easy to understand. But if something happened, and you don't know why, then it's a huge documentation diving time since almost no one can answer and solve it, because FLTK is somewhat a niche library, unless you know the right person.
Maybe you could consider using a dependency manager instead of, or in addition to, handling the libraries "manually"? I see cmake hunter has support for Qt according to docs.hunter.sh/en/latest/packages/all.html, so if you are missing the handling of it as a dependency, it could be the example of using it.
What about nana also targeting webassembly? Qt started doing this. So you have easy multi-platform, client-server "iot" and if you want and some web technologies and javascript libraries.
No Qt! Arguably, if there should be only one C++ GUI toolkit, it should be Qt. (Really, I worked with most of them and Qt is 'da bomb'). Also QtCreator is very good IDE you might want to cover in another episode (if you do, do not forget the cppreference.com doc integration) Also a small explanation and pros/cons of immediate vs retained UI would have been nice. Good work and thanks.
Qt is the de facto GUI toolkit, It's not even hard to configure and start a project on cmake(instead of qmake/project). I can easily say that I've learned c++ thanks to Qt. The other build tools used by Qt project are automatically handled by cmake. The only thing of Qt I don't like is that it's a sort of sub-language of c++, and all the other unnecessary non GUI Classes(except the ones not handled by the STL). QtCreator is almost the perfect IDE for me(it need some improvemnts on cmake based project IMO). Other toolkits doesn't give the same native look and feel as Qt does.. But for starter projects maybe those toolkits are good, but as I said, I've literally started programming with Qt.
I've used a few of the different toolkits, and in my opinion they are all pretty bad. All of them either have build issues, poor quality of resulting UI, or cross-platform limitations. The world really needs a modern GUI library that is cross platform and has the same native GUI quality that QT brings without the build difficulties.
My vote goes for QT as well, I do VFX as well as code and ALL hardcore 3D and compositing applications are using Qt now, why makes them really simple to have and embedded way to extend them either using PySide or PyQt, so if you're really going to build something BIG, Qt is the way to go.
I love Qt, it's the de facto GUI framework, but when I just started C++ development, FLTK really helped me get up and running, it was a really seamless process. While it's doesn't even come close to Qt, I really had to invest some more time and resources into learning how to use Qt, even though I was a pretty decent C++ developer already. FLTK is definitely the better framework for beginners.
Publish this kind of tutorials on Udemy, the quality is there! Having a full tutorial of some specific topic, episode by episode to follow on our free time would be awesome!
Thank you for great simple gui libraries review! libnana code looks pretty easy and straightforward, unfortunately it's not ported to os x, fltk is nice and fast, but forces to use c++98 style, gtkmm looks good and extensible, but it's hard to compile probjects with gtk if OS is not Linux and it's complex to properly style application on non-windows platforms (fonts, button sizes layouts), qt works relatively fine everywhere but forces to use Qt's containers instead of std:, own ways for network communication.In general all lightweight gui libraries ignoring accessibility problem. I think this is the reason why most of modern C++ startups considered to use electron for gui applications.
What's the point of using imGui *with* SFML for a template GUI project? The "pure" imGUI implementation won't be much longer and won't bring extra dependencies like SFML.
FLTK is really neat and easy to understand. But if something happened, and you don't know why, then it's a huge documentation diving time since almost no one can answer and solve it, because FLTK is somewhat a niche library, unless you know the right person.
nana seems to have the most modern and clean C++ interface
Maybe you could consider using a dependency manager instead of, or in addition to, handling the libraries "manually"?
I see cmake hunter has support for Qt according to docs.hunter.sh/en/latest/packages/all.html, so if you are missing the handling of it as a dependency, it could be the example of using it.
You can also use lambdas in Gtkmm's signal handlers: m_button.signal_clicked().connect([&]{ this->on_button_clicked();});. Which I find pretty cool.
What about nana also targeting webassembly?
Qt started doing this.
So you have easy multi-platform, client-server "iot" and if you want and some web technologies and javascript libraries.
Oh, your linux desktop environment is very beautiful, how to this, I’m very interested in it.
You need to restart your pc first
No Qt! Arguably, if there should be only one C++ GUI toolkit, it should be Qt. (Really, I worked with most of them and Qt is 'da bomb').
Also QtCreator is very good IDE you might want to cover in another episode (if you do, do not forget the cppreference.com doc integration)
Also a small explanation and pros/cons of immediate vs retained UI would have been nice.
Good work and thanks.
Qt is the de facto GUI toolkit, It's not even hard to configure and start a project on cmake(instead of qmake/project). I can easily say that I've learned c++ thanks to Qt. The other build tools used by Qt project are automatically handled by cmake. The only thing of Qt I don't like is that it's a sort of sub-language of c++, and all the other unnecessary non GUI Classes(except the ones not handled by the STL). QtCreator is almost the perfect IDE for me(it need some improvemnts on cmake based project IMO). Other toolkits doesn't give the same native look and feel as Qt does.. But for starter projects maybe those toolkits are good, but as I said, I've literally started programming with Qt.
I've used a few of the different toolkits, and in my opinion they are all pretty bad. All of them either have build issues, poor quality of resulting UI, or cross-platform limitations. The world really needs a modern GUI library that is cross platform and has the same native GUI quality that QT brings without the build difficulties.
Ton's of build difficulties. Would require its own video. Good move not to add it to this.
My vote goes for QT as well, I do VFX as well as code and ALL hardcore 3D and compositing applications are using Qt now, why makes them really simple to have and embedded way to extend them either using PySide or PyQt, so if you're really going to build something BIG, Qt is the way to go.
I love Qt, it's the de facto GUI framework, but when I just started C++ development, FLTK really helped me get up and running, it was a really seamless process. While it's doesn't even come close to Qt, I really had to invest some more time and resources into learning how to use Qt, even though I was a pretty decent C++ developer already. FLTK is definitely the better framework for beginners.
when using SFML , I could recommend SFGUI
can also be found on github
Publish this kind of tutorials on Udemy, the quality is there! Having a full tutorial of some specific topic, episode by episode to follow on our free time would be awesome!
I would like to know what terminal emulator you use in this video?
where is the source code?
Thank you for great simple gui libraries review! libnana code looks pretty easy and straightforward, unfortunately it's not ported to os x, fltk is nice and fast, but forces to use c++98 style, gtkmm looks good and extensible, but it's hard to compile probjects with gtk if OS is not Linux and it's complex to properly style application on non-windows platforms (fonts, button sizes layouts), qt works relatively fine everywhere but forces to use Qt's containers instead of std:, own ways for network communication.In general all lightweight gui libraries ignoring accessibility problem. I think this is the reason why most of modern C++ startups considered to use electron for gui applications.
but electron is based on javascript... right? It uses the chrome engine
gui part done with html/css/javascript and javascript using "nodejs" modules written in c++
What's the point of using imGui *with* SFML for a template GUI project? The "pure" imGUI implementation won't be much longer and won't bring extra dependencies like SFML.
Pretty cool! I had started writing my own portable gui library but I kinda stalled. The code is at DamianReloaded/OwlForms on GitHub.