home.social

#turbovision — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #turbovision, aggregated by home.social.

  1. 🤯 Wow, a terminal emulator for your terminal! 🚀 Because clearly, what we needed was more terminals inside our terminals, powered by the revolutionary Turbo Vision. 🦄 Next up: a browser that lets you browse browsers, because who doesn't love a good recursive loop? 🙃
    github.com/magiblot/tvterm #terminalemulator #TurboVision #recursiveinnovation #techhumor #futureoftech #HackerNews #ngated

  2. 🤯 Wow, a terminal emulator for your terminal! 🚀 Because clearly, what we needed was more terminals inside our terminals, powered by the revolutionary Turbo Vision. 🦄 Next up: a browser that lets you browse browsers, because who doesn't love a good recursive loop? 🙃
    github.com/magiblot/tvterm #terminalemulator #TurboVision #recursiveinnovation #techhumor #futureoftech #HackerNews #ngated

  3. 🤯 Wow, a terminal emulator for your terminal! 🚀 Because clearly, what we needed was more terminals inside our terminals, powered by the revolutionary Turbo Vision. 🦄 Next up: a browser that lets you browse browsers, because who doesn't love a good recursive loop? 🙃
    github.com/magiblot/tvterm #terminalemulator #TurboVision #recursiveinnovation #techhumor #futureoftech #HackerNews #ngated

  4. 🤯 Wow, a terminal emulator for your terminal! 🚀 Because clearly, what we needed was more terminals inside our terminals, powered by the revolutionary Turbo Vision. 🦄 Next up: a browser that lets you browse browsers, because who doesn't love a good recursive loop? 🙃
    github.com/magiblot/tvterm #terminalemulator #TurboVision #recursiveinnovation #techhumor #futureoftech #HackerNews #ngated

  5. Okay, is giving me some serious (with a side order of ) vibes and I like it.

  6. @pascaldragon
    @whitequark Turbo Vision is the most advanced and best designed TUI widget toolkit of all times! Nothing else comes even close to it. I also miss the tiny improvements that they added in TV2.0 (part of Borland Pascal 7) which AFAIK wasn't open sourced. Improvements like changing the window close symbol from [■] to [☼] while it's being clicked.

    I guess one can even forgive it's pascalish `#define Uses_TWindow` quirks...

    #TurboVision

  7. @pascaldragon
    @whitequark Turbo Vision is the most advanced and best designed TUI widget toolkit of all times! Nothing else comes even close to it. I also miss the tiny improvements that they added in TV2.0 (part of Borland Pascal 7) which AFAIK wasn't open sourced. Improvements like changing the window close symbol from [■] to [☼] while it's being clicked.

    I guess one can even forgive it's pascalish `#define Uses_TWindow` quirks...

    #TurboVision

  8. @pascaldragon
    @whitequark Turbo Vision is the most advanced and best designed TUI widget toolkit of all times! Nothing else comes even close to it. I also miss the tiny improvements that they added in TV2.0 (part of Borland Pascal 7) which AFAIK wasn't open sourced. Improvements like changing the window close symbol from [■] to [☼] while it's being clicked.

    I guess one can even forgive it's pascalish `#define Uses_TWindow` quirks...

    #TurboVision

  9. @pascaldragon
    @whitequark Turbo Vision is the most advanced and best designed TUI widget toolkit of all times! Nothing else comes even close to it. I also miss the tiny improvements that they added in TV2.0 (part of Borland Pascal 7) which AFAIK wasn't open sourced. Improvements like changing the window close symbol from [■] to [☼] while it's being clicked.

    I guess one can even forgive it's pascalish `#define Uses_TWindow` quirks...

    #TurboVision

  10. @pascaldragon
    @whitequark Turbo Vision is the most advanced and best designed TUI widget toolkit of all times! Nothing else comes even close to it. I also miss the tiny improvements that they added in TV2.0 (part of Borland Pascal 7) which AFAIK wasn't open sourced. Improvements like changing the window close symbol from [■] to [☼] while it's being clicked.

    I guess one can even forgive it's pascalish `#define Uses_TWindow` quirks...

    #TurboVision

  11. Why can't I recompile #ctran for 16-bit #DOS? Because many of #FreePascal's libraries are too big to fit into 64 KiB data blocks, and won't compile no matter which memory model I use.

    There is a chance I'll rewrite ctran in the future. #FreeVision (the #Borland #TurboVision "clone") with #ObjectPascal is certainly an option. I could also rewrite the lot in C or C++.

    But today is not that day. For now, I'd rather just rewrite a Makefile.

    #dosbox #retrocomputing

  12. Why can't I recompile #ctran for 16-bit #DOS? Because many of #FreePascal's libraries are too big to fit into 64 KiB data blocks, and won't compile no matter which memory model I use.

    There is a chance I'll rewrite ctran in the future. #FreeVision (the #Borland #TurboVision "clone") with #ObjectPascal is certainly an option. I could also rewrite the lot in C or C++.

    But today is not that day. For now, I'd rather just rewrite a Makefile.

    #dosbox #retrocomputing

  13. Why can't I recompile #ctran for 16-bit #DOS? Because many of #FreePascal's libraries are too big to fit into 64 KiB data blocks, and won't compile no matter which memory model I use.

    There is a chance I'll rewrite ctran in the future. #FreeVision (the #Borland #TurboVision "clone") with #ObjectPascal is certainly an option. I could also rewrite the lot in C or C++.

    But today is not that day. For now, I'd rather just rewrite a Makefile.

    #dosbox #retrocomputing

  14. Why can't I recompile #ctran for 16-bit #DOS? Because many of #FreePascal's libraries are too big to fit into 64 KiB data blocks, and won't compile no matter which memory model I use.

    There is a chance I'll rewrite ctran in the future. #FreeVision (the #Borland #TurboVision "clone") with #ObjectPascal is certainly an option. I could also rewrite the lot in C or C++.

    But today is not that day. For now, I'd rather just rewrite a Makefile.

    #dosbox #retrocomputing

  15. Why can't I recompile #ctran for 16-bit #DOS? Because many of #FreePascal's libraries are too big to fit into 64 KiB data blocks, and won't compile no matter which memory model I use.

    There is a chance I'll rewrite ctran in the future. #FreeVision (the #Borland #TurboVision "clone") with #ObjectPascal is certainly an option. I could also rewrite the lot in C or C++.

    But today is not that day. For now, I'd rather just rewrite a Makefile.

    #dosbox #retrocomputing

  16. Idle thought today re #ctran:

    I wonder if it's worth making a little interface using #FreeVision (the #TurboVision-compatible library that comes with #FreePascal) to display information about #Psion OO category (class definition) files?

    Yes, I realise this is feature creep. But currently I'm outputting a lot of information to the terminal that the original CTRAN.EXE doesn't do. How much do I leave in as a "verbose" option, and how much to I move to a shiny TUI?

    Something for another time.

  17. Idle thought today re #ctran:

    I wonder if it's worth making a little interface using #FreeVision (the #TurboVision-compatible library that comes with #FreePascal) to display information about #Psion OO category (class definition) files?

    Yes, I realise this is feature creep. But currently I'm outputting a lot of information to the terminal that the original CTRAN.EXE doesn't do. How much do I leave in as a "verbose" option, and how much to I move to a shiny TUI?

    Something for another time.

  18. Idle thought today re #ctran:

    I wonder if it's worth making a little interface using #FreeVision (the #TurboVision-compatible library that comes with #FreePascal) to display information about #Psion OO category (class definition) files?

    Yes, I realise this is feature creep. But currently I'm outputting a lot of information to the terminal that the original CTRAN.EXE doesn't do. How much do I leave in as a "verbose" option, and how much to I move to a shiny TUI?

    Something for another time.

  19. Idle thought today re #ctran:

    I wonder if it's worth making a little interface using #FreeVision (the #TurboVision-compatible library that comes with #FreePascal) to display information about #Psion OO category (class definition) files?

    Yes, I realise this is feature creep. But currently I'm outputting a lot of information to the terminal that the original CTRAN.EXE doesn't do. How much do I leave in as a "verbose" option, and how much to I move to a shiny TUI?

    Something for another time.

  20. Idle thought today re #ctran:

    I wonder if it's worth making a little interface using #FreeVision (the #TurboVision-compatible library that comes with #FreePascal) to display information about #Psion OO category (class definition) files?

    Yes, I realise this is feature creep. But currently I'm outputting a lot of information to the terminal that the original CTRAN.EXE doesn't do. How much do I leave in as a "verbose" option, and how much to I move to a shiny TUI?

    Something for another time.

  21. @liying
    #TurboVision was and still is the best TUI framework system, by a huge margin.
    The love that has been put into the widget design, especially in the 2.0 release, still mesmerizes me.

    The C++ port lost some of the elegance of the Pascal API, but it's still in a different world than any other TUI framework ever made. I'm looking at you, ncurses!
    @nixCraft