HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
magiblot
tvision
C++2020–2026
magiblot / tvision

tvision

A modern port of Turbo Vision 2.0, the classical framework for text-based user interfaces. Now cross-platform and with Unicode support.

31Distinct people
40Mentions
0Explicit recommenders
3.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A modern port of Turbo Vision 2.0, the classical framework for text-based user interfaces. Now cross-platform and with Unicode support.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 3:44:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year40 dated mentions

Observed mentions: 2020-09-09 18:53:05 UTC to 2026-04-25 04:18:01 UTC.

024682020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC633
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC707
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC615
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC505
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC817
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC606
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC211

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Turbo Vision A modern port of Turbo Vision 2.0, the classical framework for text-based user interfaces. Now cross-platform and with Unicode support. I started this as a personal project at the very end of 2018. By May 2020 I considered it was very close to feature parity with the original, and decided to make it open. The original goals of this project were: Making Turbo Vision work on Unix/Linux by altering the legacy codebase as little as possible. Keeping it functional on DOS/Windows. Being as compatible as possible at the source code level with old Turbo Vision applications. This led me to implement some of the Borland C++ RTL functions, as explained below. At one point I considered I had done enough, and that any attempts at revamping the library and overcoming its original limitations would require either extending the API or breaking backward compatibility, and that a major rewrite would be most likely necessary. However, between July and August 2020 I found the way to integrate full-fledged Unicode support into the existing architecture, wrote the Turbo text editor and also made the new features available on Windows. So I am confident that Turbo Vision can now meet many of the expectations of modern users and programmers. The original location of this project is https://github.com/magiblot/tvision. Table of contents What is Turbo Vision good for? How do I use Turbo Vision? Releases and downloads Build environment Unix/Linux Windows (MSVC) Windows (MinGW) Windows/DOS (Borland C++) Vcpkg Turbo Vision as a CMake dependency Features API changes Applications using Turbo Vision Unicode support Clipboard interaction Extended color support What is Turbo Vision good for? A lot has changed since Borland created Turbo Vision in the early 90's. Many GUI tools today separate appearance specification from behaviour specification, use safer or dynamic languages which do not segfault on error, and support either parallel or asynchronous programming, or both. Turbo Vision does not excel at any of those, but it certainly overcomes many of the issues programmers still face today when writing terminal applications: Forget about terminal capabilities and direct terminal I/O. When writing a Turbo Vision application, all you have to care about is what you want your application to behave and look like—there is no need to add workarounds in your code. Turbo Vision tries its best to produce the same results on all environments. For example: in order to get a bright background color on the Linux console, the blink attribute has to be set. Turbo Vision does this for you. Reuse what has already been done. Turbo Vision provides many widget classes (also known as views), including resizable, overlapping windows, pull-down menus, dialog boxes, buttons, scroll bars, input boxes, check boxes and radio buttons. You may use and extend these; but even if you prefer creating your own, Turbo Vision already handles event dispatching, display of fullwidth Unicode characters, etc.: you do not need to waste time rewriting any of that. Can you imagine writing a text-based interface that works both on Unix/Linux and Windows (and thus is cross-platform) out-of-the-box, with no #ifdefs? Turbo Vision makes this possible. First: Turbo Vision keeps on using char arrays instead of relying on the implementation-defined and platform-dependent wchar_t or TCHAR. Second: thanks to UTF-8 support in setlocale in recent versions of Microsoft's RTL, code like the following will work as intended: std::ifstream f("コンピュータ.txt"); // On Windows, the RTL converts this to the system encoding on-the-fly. How do I use Turbo Vision? You can get started with the Turbo Vision For C++ User's Guide, and look at the sample applications hello, tvdemo and tvedit. Once you grasp the basics, I suggest you take a look at the Turbo Vision 2.0 Programming Guide, which is, in my opinion, more intuitive and easier to understand, despite using Pascal. By then you will probably be interested in the palette example, which contains a detailed description of how palettes are used. Don't forget to check out the features and API changes sections as well. Releases and downloads This project has no stable releases for the time being. If you are a developer, try to stick to the latest commit and report any issues you find while upgrading. If you just want to test the demo applications: Unix systems: you'll have to build Turbo Vision yourself. You may follow the build instructions below. Windows/DOS: you can find up-to-date binaries in the Actions section. Click on the first successful workflow (with a green tick) in the list. At the bottom of the workflow page, as long as you have logged in to GitHub, you'll find an Artifacts section with the following files: examples-x86.zip: 32-bit executables built with MSVC. Windows Vista or later required. examples-x64.zip: 64-bit executables built with MSVC. x64 Windows Vista or later required. examples-dos.zip: 16-bit DOS executables built with Borland C++. No Unicode support. examples-dpmi32.zip: 32-bit Windows/DOS executables built with Borland C++. No Unicode support. Build environment Unix/Linux Turbo Vision can be built as an static library with CMake and GCC/Clang. cmake . -B ./build -DCMAKE_BUILD_TYPE=Release && # Could also be 'Debug', 'MinSizeRel' or 'RelWithDebInfo'. cmake --build ./build # or `cd ./build; make` CMake versions older than 3.13 may not support the -B option. You can try the following instead: mkdir -p build; cd build cmake .. -DCMAKE_BUILD_TYPE=Release && cmake --build . The above produces the following files: libtvision.a, which is the Turbo Vision library. The demo applications hello, tvdemo, tvedit, tvdir, which were bundled with the original Turbo Vision (although some of them have a few improvements). The demo applications mmenu and palette from Borland's Technical Support. tvhc, the Turbo Vision Help Compiler. The library and executables can be found in ./build. The build re
Read the full README on GitHub

What Hacker News says

6 sources
> A port happened before didn't it? I remember setedit and rhide about twenty years ago. Yeah. SET published their port on GitHub a few months ago: https://github.com/set-soft/tvision One of the motivations to undertake this project was when I realized SET's Turbo Vision didn't support UTF-8 (https://github.com/windoze/tvision/issues/5). > However, 16 colors? This is not a design choice of mine. It's what the original Turbo Vision supported and I still haven't gotten around to extend it. > Also, windows console is in maintenance only these days. Everyone is moving to Windows terminal and for good reason. Using the Win32 Console API doesn't imply that applications will only work in the legacy Windows console. Windows Terminal supports this, as well as any terminal taking advantage of the Windows Pseudo Console (ConPTY) API (i.e. Git Bash).
Read the rest
From a programmer's perspective, using ANSI escape sequences to display text is fairly simple (and is what Turbo Vision does). But processing input is a pain in the ass, as it requires a complex VT sequence parser. So I stuck with the Console API for input. Anyway, there would be no problem in replacing the current console I/O strategy with something entirely different or even having many of them and picking one at runtime. > Unlikely anyone is using DOS any longer, maybe freedos but still. That's what I thought, until someone opened an issue and explained they were building for DOS... (https://github.com/magiblot/tvision/issues/20). But still, I don't see the point in removing features that are already there if they are not a deterrent for further development. So DOS support is staying for now.
In A modern port of Turbo Vision 2.0

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.