Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Doing a Talk at Meetup on QB64
#1
Hey All,

I'm involved in a local tech meetup and will be giving a talk on QB64 (tomorrow evening). It'll be introductory - some history of BASIC/QB64, a tutorial on using QB64, and demonstrating some cool things about QB64.

If anyone has things they think would be worth mentioning - I'd love to hear them!

For example, I'd love to hear what some of the most impressive projects built with QB64 are, unique features of the language, cool libraries or tools one should try out, great tutorials, etc.
Reply
#2
If the talk mentions other Retro community subject I would like to give a shout to my X16 Movie Maker project.    

Its a custom Video Convertor that takes  MP4, AVI, MOV, MPG...  etc... (any format supported by ffmpeg really) and converts
them to a format playable on the Commander X16    Neo retro 8 bit computer by David Murray (aka The 8-bit Guy)

Its easily the most complex QB64PE project I have ever done,   But it also built on some Image conversion code I also
did previously in support of the X16.    

The resulting output files can only currently be played on the Commander X16 with my Player Code.   But the convertor
can be compiled and run on Any Windows 7 or higher and any Linux or MACOS platform with enough storage space to
hold the temporary video conversion files.

Project located here: https://cx16forum.com/forum/viewtopic.php?t=8226
Reply
#3
Not sure if it helps you, but if someone asks about professional usage:
I am using QB64 for years professionally. Several big companies use console based tools (win/mac/linux) I've created for them.
Most deal with huge files in one way or another;
- comparing / merging / converting 100GB+ logfiles
- SEPA/SWIFT payment-batches
- import/export conversions
- automated backup/copy processes
QB64 is one of the most performant environments for complex huge file processing and compiles same source to linux/mac/windows.
Of course main reason to use QB64 is because I natively speak it :-) No google needed
45y and 2M lines of MBASIC>BASICA>QBASIC>QBX>QB64 experience
Reply
#4
@ahenry3068 - I'll definitely take a look!

@mdijkens - That is great! Curious, do you have any suggestions on how folks could find this sort of work? I know there is a lot of old code out there, but how does one find these sort of projects to work on?
Reply
#5
(03-31-2025, 01:53 PM)davidshq Wrote: @ahenry3068 - I'll definitely take a look!

@mdijkens - That is great! Curious, do you have any suggestions on how folks could find this sort of work? I know there is a lot of old code out there, but how does one find these sort of projects to work on?
I have good contacts with these customers so I hear what they're running into and can propose to make small utility-programs for them.
I only do small tools with very clear scope and definition; I hate project teams, meetings, reports, management, scope creep, etc.
In the years I've build my own QB64 library of functions to get maximum performance and flexibility. Mostly on file-processing, csv/json/xml, https and serial
45y and 2M lines of MBASIC>BASICA>QBASIC>QBX>QB64 experience
Reply
#6
You should definitely talk about its easy learning curve, its easy to learn the basics in a month and make games/programs in the same year
I have a good game project, just not sure if you'll it the most impressive. First video is actual gameplay (from last year) and the second video is my lighting showcase, you can use them if you wish, just credit me
Tongue

Vantiro Showcase:
https://www.youtube.com/watch?v=PEgLEPXg2Ns
Vantiro Lighting Showcase:
https://www.youtube.com/watch?v=rvt3Ikdz6mY
Reply
#7
Much like mdijkens, I've also used Qbasic, QuickBasic 7.1, and more recently QB64 professionally, for years. In my case, for navigation or tactical software, military programs. The test scenarios, test results, listing of the code, do become included in formal reports, contract deliverables, which detail the requirements for operational software. I also provide the .exe files with these reports, if it helps the users to run their own tests, to double check the algorithms.

The actual software development team have always transcribed these to either C or C++, depending on the programmer involved. The point I wanted to make is that I've never had the slightest problem with the QB64 code listed in the deliverable reports. The software guys have never had trouble understanding the code or even just transcribing it verbatim and then verifying the results with the ones documented in whatever report.

I think that one big advantage of using Basic this way, similar to Pascal in this regard, is that just about any programmer can decipher the Basic code easily enough.

I'd almost describe it as a lingua franca, for this type of work anyway.
Reply
#8
If you wish to mention any tutorials or such, be certain to place Terry Ritchie's at the top of the list: https://www.qb64tutorial.com
Reply
#9
Thanks everyone! Looking forward to sharing tonight, definitely planning on sharing Terry Ritchie's tutorial.
Reply
#10
And don't forget to mentioned SCREEN 0 is the only screen you'll ever need! Actually with the addition of hardware accessibility, that's almost true.

Best wishes with the broadcast,

Pete
Reply




Users browsing this thread: 1 Guest(s)