Hi all,

This post is for the users who want to test or use InForm with the latest QB64PE version 3.4.0.

I've updated my multi lingual installation bash script that includes both QB64PE v 3.4.0 and InForm-pe (a fork of InForm v 1.3 that I made to communicate with the latest QB64PE release).

This script allows you to create icons starters for QB64PE, InForm-pe and the QB64PE folder directly on your desktop and adds the ability to invoque QB64PE from any terminal session without being into the QB64PE folder (as you can do with any standard compiler such as gcc).

You can get my pure bash script here: Bash muti lingual installation script.

The script can also cleanly uninstall QB64PE and InForm (they're installed in the /opt/qb64pe folder to not interfer with your own installation folder) as well as their different starters (desktop and programming menu) and you're free to copy their complete install forder to any other location that best suits your needs (then you'll have to modify the different starters).

Note: due to my poor and limited programming capabilities, I do not provide any support for InForm (so, no need for a sub-section for me).

Thank you for your return and enjoy QB64PE v 3.4.0 with InForm-pe when creating event driven GUI applications with the ease of the BASIC language.

Cheers.
Fifi

A question about Select Case. The query should be: Case Is > 5500 but less than 7000

I just can't do it. I even got a compiler error with it.

Attached Files

  SelectCase-Fehler.txt (Size: 1.83 KB / Downloads: 26)

Hi All,

The latest version of QBJS (0.6.0) is now available.  Here are some of the highlights for this release:

File I/O Support
Support has been added for standard QBasic file input/output.  QBJS now has a virtual file system that supports most file system operations.  As part of this update there is now a File tab in the console to manage the virtual file system.  Files can be dragged into the currently selected folder and downloaded by clicking the file name.

What is supported so far:
- INPUT, OUTPUT, APPEND and BINARY file modes

What is NOT supported yet:
- RANDOM file mode


Project Support
Now more complex projects can be managed and shared in QBJS.  There is a new toolbar which allows you to open and save either individual .bas source files or a .zip file containing an entire project.  Additionally, you can share publicly published projects with the src parameter.  Here are a couple of examples:
- Simple Project Example
- Sleighless


Expanded Set of QB/QB64 Keywords
25 new keywords have been included with this release:
_CWD$, _DirExists, _FileExists, _OS$, _StartDir, ChDir, Close, EOF, Files, FreeFile, Get, Input (file statement), Kill, Line Input (file statement), LOF, MkDir, Open, Print (file statement), Put, Name, RmDir, Seek, Write, Write (file statement), XOR (bitwise)


See the full release announcement for a complete list of fixes and enhancements.

Download the latest version of QBJS at: https://github.com/boxgaming/qbjs/releases/latest

Try it out online here: https://qbjs.org

some basic complex math routines to get started

Block stacking game

Yay!  Today, we get one of those keywords that I personally find utterly useless, but it is what it is.

Let's start by talking about how to decipher that long string of random characters, and try and understand what CVSMBF might actually stand for:

CV -- Convert
S -- SINGLE
M -- Microsoft
B -- Binary
F -- Format

So, what does it do?  

It converts a properly formatted string (one stored in Microsoft Binary Format -- which is outdated and obsoleted and thus why I find this to be basically a worthless command, unless one is working with ancient data from the late 70s or early 80s) into a SINGLE precision number.

Let me share an example of this, and its twin function MKSMBF, and then I'll explain a little more about how and where one might use these type commands:

A place for dbox and the creators of other BASIC-variants to come and showcase their projects, offer some demos, and share their vision for what they're doing and where they're going with it.  

If, over time, this little home gets too crowded and it becomes confusing to navigate between QBJS and BAM conversations and such, I'll divide this further into smaller little sub-sections, but until we see how active the developers are going to be, and how much our user base posts here, I think one forum for everything should work as a starting point.  We can always expand and grow from here, if interest develops to that point! 

It is something I have had a devil of a time trying to explain since I started this project back in the late fall of 2021.

So I will start with this, and refactor in an incremental and iterative way to try and get it just right.  (Bear with me: cognitive disabilities make it a challenge to put down into succinct and organised words this mess of intertwingled thoughts in my sponge.)

Imagine if you had the product (not the content) that is Wikipedia, but all in one file.  And that one file had a QB64PE interpreter, IDE, and everything else needed to create a large QB64PE project:  all the stuff you need for project management, task management, source code management (versioning, promotion levels, etc.), project and software documentation, all things needed for all artifacts and all processes related to all of that and everything needed in an end-to-end software development process.

It would be a bit like a bottle garden.  Everything you need is in there, in one file.  And all you need to work with it and all of your programs in it is a web browser.  The web browser can be offline or online, and the one HTML file can be stored anywhere: USB thumbdrive (or whatever other portable storage), file hosting service on the web, storage on whatever kind of device.

The operating system is irrelevant.  And your one standards-compliant file should still work A-1 in whatever web browser 15 years from now.  At worst, browsers no longer exist so you need to find a web browser to run in some virtual machine.

Now replace Wikipedia with TiddlyWiki, which has it's own language for creating whatever kind of user interface you want for all of the things you want this bottle-garden programming environment to be.

And you have access to all of the TiddlyWiki power to use as a meta-programming/scripting/macro-tool during pre-processing of your QB64PE program.  The macro language can be used to dynamically create QB64PE code, or to include all of the program's parts that have been broken down into individual modules,

And the data used to run/test the program exists in the TiddlyWiki, and can be dynamically turned into DATA statements in your program.

Everything is there, in that one file.  And because it is a wiki, you can easily manage it all, categorise, link, transclude, you name it.

And it has a whole bunch of export options, so you can export your program for different purposes: .BAS files for bringing those programs into QB64PE; source code in HTML file as documentation; small HTML application files (the minimal HTML needed, along with the interpreter and the program) for deploying/sharing the program as a single file for running in an offline/online web browser.

(The export options are limitless and ridiculously easy to develop: imagine the ability for all of the previous exports to include a language option for localisation!)

And so much more.  How do I wrap that nicely into a short paragraph?  Yikes ...

I didn't want to risk clogging "JavaScript-ing it, I need to get with it" with anything of no interest to anybody (or of interest and creating a whole discussion maybe not fitting the OP in that thread.

To me, every BASIC implementation out there that isn't "dead" is filling a place for however many folk that no other BASIC implementation can.

I can imagine that some folk might very well use one ore more BASIC implementations, each for one or more specific purposes.

Although both BAM and QBJS can outright stand on their own for what they are good at, I think both of them also have the potential of being great sidekick helpers for QB64/QB64PE/QBASIC (the big boys) programming.

If not 100% compatible with the big boys, then at least compatible enough for coding certain snippets of code.  Why?  To be able to create/edit those snippets of code from anywhere anytime (you just need a web browser), regardless of device and without an available install of "a big boy" BASIC.

This is a pretty big deal not just for anywhere-programming-anytime, but also for testing algorithms/functions/subroutines/whatever.  You can put the code on the web not just for viewing the code, but also running it.  That kind of world-wide access/availability means you can get collaboration from anywhere at any time easy peasy.

In my mind, QBJS and BAM are otherwise very different beasts.  I think:

• QBJS is and will be the cat's meow for compatibility and performance
  
• BAM is and will be the cat's meow for serious project management, source code management, and all things software development process, including documentation (being a TiddlyWiki instance, BAM inherits all of the core TiddlyWiki goodies, and the goodies from whatever TW plugin's get added as you make BAM your own)
  

The game that I've been making continuously for about a month is ready.
I used a lot of things in it that I haven't used before. I still only used _maptriangle command for graphics.
Find Waldo! I wonder who will succeed and how long it will take!




download:
https://drive.google.com/file/d/1zzE6Czi...sp=sharing