xll VS textual

My guilty secret is to use Excel for my quick and dirty GUIs. I wrote a library to make that easy if you know C++. https://github.com/xlladdins/xll.

Please tell Satya to show the ancient C SDK a little love. I'd hate to see this disappear: https://github.com/xlladdins/xll#fp-data-type

If you want to throw an exception instead of calling `abort` you can use https://github.com/xlladdins/xll/blob/master/xll/ensure.h When running in a debugger it can break execution when it fails and you can inspect the values of relevant variables.

xll appears to be MIT according to the nuspec. xll_sqlite doesn't have a license, so the author hasn't given anybody to use it.

Excel. C++ can be embedded in Excel and used interacively. It is more useful than old-fashioned python programming. I wrote something that makes this easy; https://github.com/xlladdins/xll

This is quite clever, and probably a joke that I'm not getting, but the Excel C SDK lets you call C/C++ from Excel and vice versa. This is one of my bread and butter tools, and I like nice tools, so I wrote a C++ wrapper around the SDK. It also lets you embed C++ objects in Excel: https://github.com/xlladdins/xll

A C++ library that lets you embed C++ objects in Excel. https://github.com/xlladdins/xll.

Welcome to my world: https://github.com/xlladdins/xll

The Textual project has a lot of screenshots in its documentation. These screenshots are built with the docs, so they are always up to date.

https://textual.textualize.io/

Textual[0] does this for CLI apps. That’s not for full GUI apps, but it’s very DOM-like, uses CSS selectors, etc. and a cool option when it meets your needs.

[0] https://github.com/Textualize/textual

For future projects that need a TUI beyond normal printing to a terminal, I'd recommend taking a look at Textual.

https://jupyterbook.org/en/stable/content/code-outputs.html#...

`less -R` is not the default.

FWIW, textual (and urwid) does ANSII escape codes well: https://github.com/Textualize/textual

  touch file$'\n'name

After installing logmerger, you can run a self-contained demo by running logmerger --demo, to view two log files before and after they are merged, and to play with the user-interface features provided by textual.

I think it just survived naturally, filling in the cracks left by Java / C++.

And not the era of Textual (https://textual.textualize.io/) is here, python may get the spotlight even more.