FTXUI VS tcod-cpp-engine-2022

GitHub repo: ArthurSonzogni/FTXUI

Background: I want to make a NES Tetris) clone for the terminal, with full resolution, this is achievable through using this ▀ character, and defining back and foreground color. This would result in a 1x2 pixel and by making the game width 256x120 characters this would provide full resolution. I made some tests, creating my own encoding for the different sprites and optimizing everything, which resulted in very quick printing times, even with a normal terminal. Nearly fast enough for the full 60Hz that the NES has, when printing the whole screen. The fact that i don't need to reprint the background (except maybe a tetris), makes 60Hz a kinda realistic goal. My main concern is, that there could occur kind of a screen tearing effect, which i really want to avoid. AFAIK, ncurses has a way to print the whole "window" with a function call to avoid this issue, however I had a lot of issues when trying to use ncurses to print the entire background and figured, that there are better alternatives. I also tried FTXUI and whilst the experience of giving each "pixel" a fore- and background color was much better, i didn't quite find a way to refresh the screen like ncurses. (i think there is some kind of way with the ScreenInteractive class, but i didn't get that to work, and it seemed like there was not a way to color each pixel. with InteractiveScreen you can make your own components with the whole "text()" thing, but this isn't really what i need)

Try this library for console https://github.com/ArthurSonzogni/FTXUI

Depends on which level of "UI" you want. Personally I like https://github.com/ArthurSonzogni/FTXUI , but if you want to do those old TUI things then probably the (n/pd)curses libraries.

I find openMVG very decent, FTXUI might be a good one and nlohmann's json library is also pretty nice. I don't really know of any project that strictly adheres to the core guidelines, except maybe for some of Jason Turner's (sample) projects.

Okay stupid suggestion I know but I've recently been learning the FTX UI library which basically adds a little bit of UI programming to the terminal and it has canvas that lets you plot pixel by pixel.

No affiliation with any ponzi schemes https://github.com/ArthurSonzogni/FTXUI

I ended up following the C++ tutorial and creating a custom engine with the newer libtcod API. Writing the event API from scratch also let me compile with Emscripten to make a web build of my C++ libtcod projects. The resulting engine demo can be played online here. I lost steam near the end of the project since I was unsure how I should handle a database and because I tried too hard to keep saves compatible even though this was supposed to be a prototype. The main thing I learned is that serialization is difficult with C/C++ and it would've been easier to do had I used an ECS library.

The libtcod maintainer just finished a new C++ engine as part of this year's tutorial event. Or did you have to have videos? There are newer video series as well, but not C++.

I used and followed the instructions of this library. Nearly all of my serialization code ended up in one file.

I only develop on Windows right now, so I often miss feedback from the GCC and Clang compilers unless I check the workflow logs. All the platforms on Itch (win/mac/linix/html) are enabled by this GitHub Actions workflow which automatically deploys everything that's pushed to the main branch and just compiles and uploads test builds for any other branch. It's been modified from the libtcod template project to support Itch, but I can probably backport that feature. You can view the build logs from these workflows here.

GitHub | Playable

GitHub | Screenshot (Cave generation)

I'm working in C++17 and doing the ancient C++ tutorial on RogueBasin. I'm starting from the libtcod C++ template and plan on using the latest libtcod features rather than the older ones taught by that tutorial. My new repository is here.