Hacker News new | past | comments | ask | show | jobs | submit login

Author of FTXUI here. Thanks for this answer! This is exactly the right reasons.

Every terminal compatible with the main subset of the various VT specifications should be compatible with FTXUI. If someone can prove this wrong, I must fix this ;-)

I own a Linux machine so this is the "main" target. Support is quite strong. However, I don't own a Windows machine and it's quite painful for me to test on it. Windows support has been added by contributors mostly. That's the reason I say it is still "experimental". The various Windows terminal requires some Windows specific calls to enable VT interpretation, as explained above.

FTXUI can be compiled toward WebAssembly and executed against xterm.js terminal. This proves you can use FTXUI against a compliant terminal and not really depends on OS calls. https://arthursonzogni.com/FTXUI/examples/

There are some function depending on the systems:

- Windows diverges a bit (see above)

- Getting terminal dimensions.

- Getting terminal support for colors.




First, I suggest you try to use terminfo to properly ensure your terminal supports the "main subset" you've mentioned.

Second, I suggest you get in contact with Thomas E. Dickey, the maintainer of libncurses and terminfo, to see how he tests that library - on something like 15 different platforms.

Finally, over time, consider relaxing your set of terminal requirements - either with workarounds or with limitation of functionality for less-capable terminals.


I guess that working with more primitive terminals would make easier to use to drive UIs on embedded targets. The "terminal" Ftxui sees becomes just some LCD-painting primitives.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: