11–19 of 19 posts
Awesome. Loved Turbo Pascal back in the day. A port happened before didn't it? I remember setedit and rhide about twenty years ago. At that time I was desperate for a CUA editor under Linux. So, I stripped down setedit and made my own simple editor in the tradition of dos edit and nano. That worked for a number of years but the tvision? lib was removed from Debian and I couldn't build the editor any longer. Couple of…
back then I used Turbo Pascal first and dabble in its Turbo Vision before knowing the C++ counterpart. For me, the C++ version looks like a port of the Pascal one. IIRC, it even has "uses" like construct. So, for me, the "true" TV is the Pascal one.
The culture at Borland, and subsequent renamings, was always Object Pascal first and C++ would built on top of it.
Still I keep waiting for the day that Visual C++ actually deserves the Visual moniker by offering a C++ Builder like tooling experience.
Haha nice! I also have been hacking transparency and limited utf8 into the turbo vision source code for my weird kodi like project, but your work seems way better ! https://github.com/ivans5/BitMediaCentre
I was not aware of your project, thanks for sharing it.
Awesome. Loved Turbo Pascal back in the day. A port happened before didn't it? I remember setedit and rhide about twenty years ago. At that time I was desperate for a CUA editor under Linux. So, I stripped down setedit and made my own simple editor in the tradition of dos edit and nano. That worked for a number of years but the tvision? lib was removed from Debian and I couldn't build the editor any longer. Couple of…
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).
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.
Awesome. Loved Turbo Pascal back in the day. A port happened before didn't it? I remember setedit and rhide about twenty years ago. At that time I was desperate for a CUA editor under Linux. So, I stripped down setedit and made my own simple editor in the tradition of dos edit and nano. That worked for a number of years but the tvision? lib was removed from Debian and I couldn't build the editor any longer. Couple of…
> 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 origi…