Microsoft BASIC PDS 7.1 User Interface Toolbox - Printable Version +- QB64 Phoenix Edition (https://staging.qb64phoenix.com) +-- Forum: QB64 Rising (https://staging.qb64phoenix.com/forumdisplay.php?fid=1) +--- Forum: Code and Stuff (https://staging.qb64phoenix.com/forumdisplay.php?fid=3) +---- Forum: Programs (https://staging.qb64phoenix.com/forumdisplay.php?fid=7) +---- Thread: Microsoft BASIC PDS 7.1 User Interface Toolbox (/showthread.php?tid=1919) |
Microsoft BASIC PDS 7.1 User Interface Toolbox - a740g - 08-19-2023 This was supposed to go in the Museum a long time ago. However, I never got to re-implementing the assembler routines that this uses... until now. I've included the assembly sources as comments in General.bas. Below those comments you can find the QB64 function ports. From MS PDS 7.1 Getting Started docs: Quote:User Interface ToolboxPlease note that this is by no means a perfect port. There are a few differences and quirks. Happy tinkering! RE: Microsoft BASIC PDS 7.1 User Interface Toolbox - bplus - 08-19-2023 Reminds me of VB for DOS using Ansii characters instead of graphics for all the boxes/dialogs. Eric was doing this too and probably Steve. So all that was MS PDS 7.1 inspired? (I'd not had the acquaintance.) RE: Microsoft BASIC PDS 7.1 User Interface Toolbox - grymmjack - 08-19-2023 (08-19-2023, 04:49 AM)a740g Wrote: This was supposed to go in the Museum a long time ago. However, I never got to re-implementing the assembler routines that this uses... until now.Holy cow! This is cool RE: Microsoft BASIC PDS 7.1 User Interface Toolbox - Dav - 08-19-2023 Wow! Nicely done. Great port. - Dav RE: Microsoft BASIC PDS 7.1 User Interface Toolbox - mnrvovrfc - 08-19-2023 (08-19-2023, 10:46 AM)bplus Wrote: Reminds me of VB for DOS using Ansii characters instead of graphics for all the boxes/dialogs. Both toolkits used high-bit ASCII on CP437. But the VB-DOS one went further, had odd-looking dialog buttons that took at least three screen lines. It was quite unlike Turbo Vision with the goofy-looking button with black shadow "underneath". Also VB-DOS began the concept of event-driven programming. Create a few hundred functions per application, meant to be filled in by the programmer, for any response in the GUI program. Meanwhile on earlier BASIC's by M$, BASIC PDS in particular, had to do like Freebasic and C++ and program a big fat "SELECT CASE... END SELECT", into the main module level code. depending on kinds of events generated by the program. I have seen BASIC PDS source code only once for this toolkit, however, so I might be mistaken. But the event-driven thing in VB-DOS discouraged me totally from that one. This was before I discovered that one used "far" strings no matter what, and did a few other things to convince me it wasn't QuickBASIC anymore. Here is a fascinating port of Turbo Vision: https://github.com/magiblot/tvision RE: Microsoft BASIC PDS 7.1 User Interface Toolbox - TerryRitchie - 08-19-2023 (08-19-2023, 06:11 PM)mnrvovrfc Wrote:Visual basic 1.0 for Windows was actually introduced a year earlier than Visual Basic for DOS. The event driven programming was introduced by the Windows version, which I found quite fascinating and very easy to use. I switched to VBDOS as soon as it became available because of this. I mostly wrote programs to track and order inventory, perform purchase orders, create custom quotes, etc.. for the company I worked for at the time. VBDOS (and VBWIN) really streamlined that process for me. The ISAM database included with VBDOS was great too.(08-19-2023, 10:46 AM)bplus Wrote: Reminds me of VB for DOS using Ansii characters instead of graphics for all the boxes/dialogs. RE: Microsoft BASIC PDS 7.1 User Interface Toolbox - a740g - 08-20-2023 magiblot's tvision Turbo Vision C++ port if one of the best ones there is. And then there is Jexer (The Jexer Homepage (sourceforge.io)). Although, this stuff is made in Java. It can do really neat stuff. |