Announcing QB64 Phoenix Edition v0.5 Release!

[admin]

Release v0.5.0 · QB64-Phoenix-Edition/QB64pe (github.com)

Another step forward in making our first version "1.0" as the new team working on QB64. This release (version 0.5) now:

• Has swapped out the mingw compilers to updated versions for Windows users.
  
• Reduced the size of the repo considerably for those who wish to download direct and setup QB64 manually, for whatever reason.
  
• Prepacked Linux and max versions of QB64, which come in at less than 10MB each now.
  
• We've swapped out all the references to the now defunct .net and .org sites that we could find, and replaced them to proper, working links which now connect to our new wiki, forum, and all at qb64phoenix.com.
  
• $Color:0 and $Color:32 has now been tweaked to work with $NoPrefix. Color names will remain the same in all cases, if $Color is used without $NoPrefix. When $Color is used in conjunction with $NoPrefix, the colors of Red, Green, and Blue which would normally conflict with the now underscoreless commands of _Red, _Green, _Blue, have been altered to have NP_appended to them (for No Prefix). Example: Color NP_Red, Orange for a red on orange color.
  

Click on the big title above to go directly to the release page and grab yourself a copy of the latest version for all your QB64 needs!

[Coolman]

thank you for your work. is this version based on qb64 2.01?

[PhilOfPerth]

Pardon my ignorance, but what's the simplest way to transition from the old tQB64 to the new one? Will I need to move my "home-grown" files, or anything else, into a new directory?

[Tim]

Pardon my ignorance, but what's the simplest way to transition from the old tQB64 to the new  one? Will I need to move my "home-grown" files, or anything else, into a new directory?

I think all you need to do is copy and paste. That is what I did. I left my old "qb64" file folder alone and made a new "qb64 phoenix v 0.50" folder. And I copied and pasted the new and my own "old" .bas files into it. Do get a second opinion, though!

[SMcNeill]

thank you for your work. is this version based on qb64 2.01?

If this was still under the plain QB64 name, this would be version 2.05, or so.  See my post explaining things here: Who and What is The Phoenix Edition (qb64phoenix.com)

---

Pardon my ignorance, but what's the simplest way to transition from the old tQB64 to the new  one? Will I need to move my "home-grown" files, or anything else, into a new directory?

I think all you need to do is copy and paste. That is what I did. I left my old "qb64" file folder alone and made a new "qb64 phoenix v 0.50" folder. And I copied and pasted the new and my own "old" .bas files into it. Do get a second opinion, though!

That's one way to do things, and a lot of people do exactly that to keep things all together.  

Another, if you have all your files in a separate folder, is to be certain to click the "Output EXE to source folder" option under the RUN menu in the IDE.  Doing so will have your compiled EXEs stay with the source files, no matter where they're at.   In this manner, you can keep all your files in "My Documents/My BAS files/"  (or whatever other folder you like), and then simply load and compile the working EXE to that folder, so that all you have to do when it come time to upgrade is simply to download and extract the latest, greatest version of QB64 available. 

[Tim]

thank you for your work. is this version based on qb64 2.01?

If this was still under the plain QB64 name, this would be version 2.05, or so.  See my post explaining things here: Who and What is The Phoenix Edition (qb64phoenix.com)

---

Pardon my ignorance, but what's the simplest way to transition from the old tQB64 to the new  one? Will I need to move my "home-grown" files, or anything else, into a new directory?

I think all you need to do is copy and paste. That is what I did. I left my old "qb64" file folder alone and made a new "qb64 phoenix v 0.50" folder. And I copied and pasted the new and my own "old" .bas files into it. Do get a second opinion, though!

That's one way to do things, and a lot of people do exactly that to keep things all together.  

Another, if you have all your files in a separate folder, is to be certain to click the "Output EXE to source folder" option under the RUN menu in the IDE.  Doing so will have your compiled EXEs stay with the source files, no matter where they're at.   In this manner, you can keep all your files in "My Documents/My BAS files/"  (or whatever other folder you like), and then simply load and compile the working EXE to that folder, so that all you have to do when it come time to upgrade is simply to download and extract the latest, greatest version of QB64 available. 

Thanks, Steve. That clarifies and simplifies things for me.

[JRace]

FYI the last line of qb64.1 in the 0.5.0 repo still points to the old .org site.

[SMcNeill]

FYI the last line of qb64.1 in the 0.5.0 repo still points to the old .org site.

It's in a Pull Request to be fixed now, along with the links in copying.txt and samples.txt.