home.social

#turbovision — Public Fediverse posts

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

fetched live
  1. Když jsem kdysi ještě na základce začal programovat propadl jsem kouzlu prostředí #TurboVision . Roky pak běžely a s nimi nové technologie kterým dával nejčastěji vzhled #TwitterBootstrap ale ten přes všechny jeho přednosti je jenom skin na webu. Takže když #AbraFlexi přineslo svoje nové webové rozhraní, často jsem si říkal jak by to vypadalo pokud by technologie šly jinou cestou, jak by asi vypadalo FlexiBeečko pod DOSem ? No soudím, že nějak takhle:

    #ZeŽivotaVývojáře #TUI

  2. Když jsem kdysi ještě na základce začal programovat propadl jsem kouzlu prostředí #TurboVision . Roky pak běžely a s nimi nové technologie kterým dával nejčastěji vzhled #TwitterBootstrap ale ten přes všechny jeho přednosti je jenom skin na webu. Takže když #AbraFlexi přineslo svoje nové webové rozhraní, často jsem si říkal jak by to vypadalo pokud by technologie šly jinou cestou, jak by asi vypadalo FlexiBeečko pod DOSem ? No soudím, že nějak takhle:

    #ZeŽivotaVývojáře #TUI

  3. Když jsem kdysi ještě na základce začal programovat propadl jsem kouzlu prostředí #TurboVision . Roky pak běžely a s nimi nové technologie kterým dával nejčastěji vzhled #TwitterBootstrap ale ten přes všechny jeho přednosti je jenom skin na webu. Takže když #AbraFlexi přineslo svoje nové webové rozhraní, často jsem si říkal jak by to vypadalo pokud by technologie šly jinou cestou, jak by asi vypadalo FlexiBeečko pod DOSem ? No soudím, že nějak takhle:

    #ZeŽivotaVývojáře #TUI

  4. Když jsem kdysi ještě na základce začal programovat propadl jsem kouzlu prostředí #TurboVision . Roky pak běžely a s nimi nové technologie kterým dával nejčastěji vzhled #TwitterBootstrap ale ten přes všechny jeho přednosti je jenom skin na webu. Takže když #AbraFlexi přineslo svoje nové webové rozhraní, často jsem si říkal jak by to vypadalo pokud by technologie šly jinou cestou, jak by asi vypadalo FlexiBeečko pod DOSem ? No soudím, že nějak takhle:

    #ZeŽivotaVývojáře #TUI

  5. 🤯 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

  6. 🤯 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

  7. 🤯 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

  8. 🤯 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

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

  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. @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

  12. @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

  13. @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

  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. 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

  17. 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

  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

  22. @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

  23. @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

  24. @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

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

    #Borland #TurboVision

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

    #Borland #TurboVision

  27. CW: Programming with Java and Dexer textmode GUI: Adding descriptions to the main menu items

    Stumbled on my first Jexer roadblock: Showing a menu item description in the status bar.

    It turns out that this functionality is NOT built-in, and I can't override classes like TMenu or TMenuItem (WTF?), they have final methods and private constructors. Who the hell came up with this idea??? :blobugh:

    So, in order to be able to display a menu item's description text in the statusbar, I had to add an onIdle() event handler to the application's desktop object.

    This handler finds the active menu in the menubar and gets the active menu item's id, then updates the status bar text with a string that I store manually using the menu item id as key.

    It's a horribly complicated workaround, but it works! 😀

    Best of all, since it's called in an onIdle() event, it only gets called after the last event is processed, which means it's efficient and doesn't consume any unnecessary cycles!

    #Java #Jexer #TurboVision #programming

  28. CW: Programming with Java and Dexer textmode GUI: Adding descriptions to the main menu items

    Stumbled on my first Jexer roadblock: Showing a menu item description in the status bar.

    It turns out that this functionality is NOT built-in, and I can't override classes like TMenu or TMenuItem (WTF?), they have final methods and private constructors. Who the hell came up with this idea??? :blobugh:

    So, in order to be able to display a menu item's description text in the statusbar, I had to add an onIdle() event handler to the application's desktop object.

    This handler finds the active menu in the menubar and gets the active menu item's id, then updates the status bar text with a string that I store manually using the menu item id as key.

    It's a horribly complicated workaround, but it works! 😀

    Best of all, since it's called in an onIdle() event, it only gets called after the last event is processed, which means it's efficient and doesn't consume any unnecessary cycles!

    #Java #Jexer #TurboVision #programming

  29. CW: Programming

    I'm progressing with my text-mode #Java GUI application.

    Decided to switch from #Lanterna to #Jexer because the Lanterna API is a blackhole of documentation; there is little to none.

    Jexer, OTOH, is based on #Borland #TurboVision which has plenty of documentation available - Several implementations of the TurboVision API are out there, and it's so damn easy to set up.

    In a couple of hours I'm already adding the Main Menu.

    Piece of cake. :blobcatcool:

  30. CW: Programming

    I'm progressing with my text-mode #Java GUI application.

    Decided to switch from #Lanterna to #Jexer because the Lanterna API is a blackhole of documentation; there is little to none.

    Jexer, OTOH, is based on #Borland #TurboVision which has plenty of documentation available - Several implementations of the TurboVision API are out there, and it's so damn easy to set up.

    In a couple of hours I'm already adding the Main Menu.

    Piece of cake. :blobcatcool: