11-22-2023, 11:52 PM
That's an interesting question. What is QBJS today started as an extension to the GX game engine that I'm working on. Essentially, I wanted to be able to take games made in QB64 and compile them for the web. (The web IDE grew out of the nerdy idea of having the qb2js compiler compile itself to JS so it could run in the browser.)
I intend for the compiler (qb2js.bas) to always be separate from the IDE. It can be run from the command line today and could certainly be invoked from within the QB64 IDE. It's inclusion in this manner would be a question for the QB64 devs.
I will say that, while it's come a long way and you can run a lot of QB64 programs in QBJS today, there is still quite a way to go to yet to achieve the goal level of compatibility with QBasic/QB64. And there are going to be some areas where, due to the nature of the web and JS, that 100% compatibility is just not feasible. So there would have to be that understanding that not all features will be available for "compile to web".
I do see it as continuing as a separate project as there are a lot of possibilities for future functionality specific to QBJS.
I intend for the compiler (qb2js.bas) to always be separate from the IDE. It can be run from the command line today and could certainly be invoked from within the QB64 IDE. It's inclusion in this manner would be a question for the QB64 devs.
I will say that, while it's come a long way and you can run a lot of QB64 programs in QBJS today, there is still quite a way to go to yet to achieve the goal level of compatibility with QBasic/QB64. And there are going to be some areas where, due to the nature of the web and JS, that 100% compatibility is just not feasible. So there would have to be that understanding that not all features will be available for "compile to web".
I do see it as continuing as a separate project as there are a lot of possibilities for future functionality specific to QBJS.