Coding
Smallest videogame: .KKrieger
Get native look of the current OS in your app: https://stackoverflow.com/questions/18980426/which-if-any-achieves-windows-native-look-gtk-wxwidgets-qt-fltk
Windows specific programming and speed: https://stackoverflow.com/questions/4048231/your-best-library-for-create-gui-gtk-qt-win32-api-etc/5800101#5800101
TESTED by burning prodigy on stackoverflow:
starting time (simple GUI with menu and buttons):
| library | speed |
|---|---|
| GTK+ | 7 secs |
| Qt | 4 secs |
| WxWidgets | 3.32 seconds |
| FLTK | 1 second |
| Win32 Api | 0.34 seconds; |
| library | space taken |
|---|---|
| Gtk+ | 132 kb |
| Qt | 4.5 mb |
| WxWidgets | 4.5 mb |
| FLTK | 54 kb |
| Win32 Api | 6.5 kb; |
esp websocket: https://github.com/espressif/esp-idf/tree/f91080637/examples/protocols/websocket
esp webserver libesphttpd: https://github.com/chmorgan/libesphttpd/tree/esp-idf_chmorgan",
Git submodules
https://git-scm.com/book/en/v2/Git-Tools-Submodules
By default, the git pull command recursively fetches submodules changes, but it does not update the submodules. To finalize the update, you need to run git submodule update:
git submodule update --init --recursive
Note that to be on the safe side, you should run git submodule update with the --init flag in case the MainProject commits you just pulled added new submodules, and with the --recursive flag if any submodules have nested submodules.
Working on submodules
In order to set up your submodule to be easier to go in and hack on, you need
to do two things. You need to go into each submodule and check out a branch to
work on. Then you need to tell Git what to do if you have made changes and then
git submodule update --remote pulls in new work from upstream. The options are
that you can merge them into your local work (--merge), or you can try to
rebase your local work on top of the new changes (--rebase).
git submodule update --remote --merge
Publish submodule changes
If we commit in the main project and push it up without pushing the submodule changes up as well, other people who try to check out our changes are going to be in trouble since they will have no way to get the submodule changes that are depended on. Those changes will only exist on our local copy.
In order to make sure this doesn’t happen, you can ask Git to check that all
your submodules have been pushed properly before pushing the main project. The
git push command takes the --recurse-submodules argument which can be set to
either “check” or “on-demand”. The “check” option will make push simply fail if
any of the committed submodule changes haven’t been pushed.
git push --recurse-submodules=check
If you want the check behavior to happen for all pushes, you can make this
behavior the default by doing git config push.recurseSubmodules check
The other option is to use the “on-demand” value, which will try to do this for
you.