01-06-2023, 11:15 PM
The code for the IDE isn't included in an user's program's executable file, what made you think that it was?
The QB64 IDE was meant for somebody to start straight away to program instead of having to install Geany, NPPP or some other program like that. People have been crying for an IDE for Freebasic that comes directly from those developers. "Where's the blue screen?" I wince everytime I read that from the Freebasic help file.
You will have to look into that other system instead and forget about QB64PE having a "headless" version. Although this is only an opinion.
Even if there was a "QB64 without GUI" thing, it wouldn't be officially supported by the Phoenix Team or by the "qb64-dot-com" folks and you, or anybody else that decided to depend on that project, would be entirely at the mercy of that program's development. Generally it means becoming one of the dedicated contributors.
About making executable files smaller, just give up with 64-bit. When we all have to move up to 128-bit or something like that, even more memory will be required for everything. The "keep it small" mentality that is enforced by 16-bit has to be ditched in favor of progress. Some people aren't going to like it.
The "keep it small" means QB64PE would have to turn into a payware project that resembles M$ Visual Studio in its early versions. In other words, a compiler that directly takes BASIC code, creates object files, combines them with stuff taken from libraries and spits out an EXE file or a Unix-like executable file. Freebasic is close to that reality. QB64(PE) have different goals to set.
The QB64 IDE was meant for somebody to start straight away to program instead of having to install Geany, NPPP or some other program like that. People have been crying for an IDE for Freebasic that comes directly from those developers. "Where's the blue screen?" I wince everytime I read that from the Freebasic help file.
You will have to look into that other system instead and forget about QB64PE having a "headless" version. Although this is only an opinion.
Even if there was a "QB64 without GUI" thing, it wouldn't be officially supported by the Phoenix Team or by the "qb64-dot-com" folks and you, or anybody else that decided to depend on that project, would be entirely at the mercy of that program's development. Generally it means becoming one of the dedicated contributors.
About making executable files smaller, just give up with 64-bit. When we all have to move up to 128-bit or something like that, even more memory will be required for everything. The "keep it small" mentality that is enforced by 16-bit has to be ditched in favor of progress. Some people aren't going to like it.
The "keep it small" means QB64PE would have to turn into a payware project that resembles M$ Visual Studio in its early versions. In other words, a compiler that directly takes BASIC code, creates object files, combines them with stuff taken from libraries and spits out an EXE file or a Unix-like executable file. Freebasic is close to that reality. QB64(PE) have different goals to set.