I see a variety of references as supporting different workflows; we all do things in different ways. For example, I've got a couple of QB64 projects on the burner ATM, and a lot of the time when inspiration hits I'll open the appropriate file(s) in Notepad++, since I frequently have it open anyway and I'm not planning on immediately compiling. (Even though I DO have NPP set up to compile QB64, I usually compile from the QB64 IDE, since its immediate feedback is QUITE useful.)
MS's HTML Help Builder chokes on the Wiki (getting THAT to work is on my list of rainy weekend projects), and I'm not a big fan of using PDFs for reference, so a text version is a potentially useful idea. Having a list of keywords in a convenient format can be a time saver, especially when one is exploring areas of QB64 that one has never been to before and may be unsure of the appropriate command to type into the QB64 help system.
(The original intent of my last post was to add tag stripping to Steve's program and post the results, to create another QB64 programming example, but pragmatism won out in the end and the cleaned-up word list was all I ended up with.)
MS's HTML Help Builder chokes on the Wiki (getting THAT to work is on my list of rainy weekend projects), and I'm not a big fan of using PDFs for reference, so a text version is a potentially useful idea. Having a list of keywords in a convenient format can be a time saver, especially when one is exploring areas of QB64 that one has never been to before and may be unsure of the appropriate command to type into the QB64 help system.
(The original intent of my last post was to add tag stripping to Steve's program and post the results, to create another QB64 programming example, but pragmatism won out in the end and the cleaned-up word list was all I ended up with.)