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

https://qb64phoenix.com/forum/showthread...66#pid9266

This thread exists because I didn't want to reply to that post, and I selfishly didn't want to post on the dedicated thread about the subject.

Good job with this project, surprised that it's as deep as it is in such a short time. Normally I don't like stunts done by clunky web browsers but this interested me. I visited the page on Github to learn about support for QB64(PE) keywords. These are just my observations.

• "COMMAND$" - not even a special "global" dialog to put in its value? Some programs depend on this, including all-uppercase return value, and it might be difficult to change away from it. Might not have to worry a lot about "COMMAND$(1)" or alike. OTOH Linux is very lame about this sometimes, limiting terminal command line to a maximum of 255 characters.
  
• "IF... THEN" - clarify that it has to be "IF (condition) THEN GOTO (linenum/label)", or "GOTO" cannot be used at all? (OK discovered below "GOTO" and labels aren't even supported.) Does this mean only block "IF" could work? No problem for me but some old programs would need extensive revision then, you know how much colons were loved back then...
  
• "LOCATE" - does this mean changing the cursor shape? Because this is a bit sad this day and age. I mean in graphics mode "druw yer own kersair for krissakes"...
  
• "OPEN FOR RANDOM AS" - this should be easy to implement one way. "TYPE... END TYPE" is supported, am I correct? It must have to do with a security issue. Entire files could be "dowloaded" which isn't as useful to me and I could never get to grips with Internet functionality in QB64PE.
  
• "SELECT CASE" - what is "EVERYCASE"? Do you mean "CASE ELSE"? Must be Visual Basic tendency.
  
• "TIMER" - a few QB64 programs will be broken because of this. So this might mean the QB64-only edition of "ON TIMER" isn't supported neither.
  
• "_MOUSEINPUT" - LOL so this is like being on a Macintosh.
  
• "_OS$" - I think this should work like in normal QB64, some programs depend on this information and don't use the preprocessor.
  

Perhaps not the greatest of keywords to start with, but that's the nature of randomness.  It is what it is, so with no further ado, here's _GREEN32 explained and showcased.

What is _GREEN32?  It's a simple command that takes a color value and returns the green component back to you from it.

When would you use it?  Basically when you have a color (perhaps taken from one of the color names), and you need to know what the green value is in it.

Example:

From the topic here -- Code fix (qb64phoenix.com) -- I was surprised to see both Dimster and OldMoses were both unaware of the INPUT$ function.  It's one of those commands that's been in the language since the beginning of time (back when cavemen used LET and such), so I just assumed everyone was familiar with it by now.  

Fool me once, as they say!

So the question then becomes, "What other keywords are folks missing out on?  And how can we help draw attention to those keywords, to make the user base aware of them?"

My solution??

Keyword of the Day!!  

Every day I'll run the little code below and TRY to write up an explanation and a few simple samples of whatever keyword the list gives me.  If it's a keyword that's already been covered, then YAYYYY -- I get a day off!!  For those that know the keyword, I encourage you to add any explanation and examples that you can with it, to showcase WHY one would use it and WHEN they would use it.  On any day which I might miss due to illness, life, or whatnot, I encourage any other user to feel free to run the code below and put up a sample for a Keyword of the Day!

Let's see how many days in a row we can go without missing one!

Hello
Please modify the code.
Normal inputs are: zero (inclusive) to 6
How to convert the code so that the option without entering digits after pressing the Enter key, T # takes the value 7.
Thank You

PRINT "Enter a digit"
K$ = "": F$ = ""
WHILE LEN(K$) < 1 AND F$ <> CHR$(13)
    F$ = ""
    WHILE F$ = "": F$ = INKEY$: _LIMIT 30: WEND
    IF F$ = CHR$(27) THEN 15
    IF F$ = CHR$(32) THEN 20
    IF F$ <> CHR$(13) THEN K$ = K$ + F$
WEND
T# = VAL(K$): PRINT T#

Looks like you're not sleeping well...

Hi,

I'm (not really) Mike Lindell.

Are you up all night posting on the Phoenix Forums and no matter what you do, you can't stop finding more and more threads to read and respond to? Well have I got a solution for you. Just visit myQB64 Official dot com, register, sign in, and in no time at all your head will smash straight into the keyboard and you'll be fast asleep. My patented lack of content (opposite of fill) will cause your thoughts to vanish and I personally guarantee you'll awaken 8 hours later, completely refreshed and ready to start your day. Just remember to log out immediately to prevent going into a coma.

QB64 dot com. Officially your best night's sleep ever!

Quick Question.

At present is there any version of QB64 that can possibly run on an ARM processor (on some OS)?

Enjoy this tiny little SCREEN 0 MOD Player that I've written entirely in QB64 (well, I re-wrote the mixer in C++ some time ago).

Thank you to @vince for your awesome FFT routines. You can find the good stuff here https://qb64phoenix.com/forum/showthread...05#pid2005

a740g/QB64-MOD-Player: A ProTracker (and compatible) MOD player & library written in QB64-PE (github.com)

Use the attached ZIP file below to get the complete source code. To get the latest source code use the GitHub link above and follow the notes in README.md.

Update:

• Added S3M (Scream Tracker) format support (WIP; no FM yet)
  
• Added MTM (MultiTracker) format support
  
• Can play MODs and MTMs directly from https://modarchive.org/ (many thanks to @DSMan195276 for HTTP support and documentation)
  

Attached Files

  QB64-MOD-Player.zip (Size: 42.91 MB / Downloads: 33)