WHy RapidQ2?

RapidQ2 IS just RapidQ, but just a set of include files that are supposed to work together and a good set of documentation to go with it.

Often people complain that a RQ program doesn't work and "how to fix it." Another complaint was RQ was not open source and a new compiler was not going to be released.

RapidQ2 was intended to fix old bugs, show how to do a work-around, and make it more open source. Lots of code has been generated by talented programmers to fix RQ, but the problem was:

-How do you get the latest version of a fix?

-How do you keep upgrading the documentation for bug fixes/work arounds? Couldn't the docs include more tutorials?

-Often the code or new components needed debugging, or were incomplete.

-What if you knew how to add good functionality to the language so everyone could use it?


RapidQ2 was intended to fix all this, (but there are other projects too like Andrew's RQDP, which gives RapidQ2 a lot of its code and docs)

-I put together some of the most common components into one include file (RapidQ2.inc)
-try to debug them and make it more complete
-added a new CHM file with bug fixes/limitations of RQ
-I have nothing to gain personallly from this project -- it belongs to the RQ community. If you want to add something, just propose it, debug it, make good documentation to it, then add it to RapidQ2.inc or make a new include file that works with the others. If you have a new version, correct RapidQ2 collection, everyone knows where to get the update.

Here are some problems:
-Adds a little more memory to your app (15-20K)
-It is easy to just improve the language with the Include file with this line:
$DEFINE QForm newQform
'now Qform works with all the new functions....

BUT!!!
-You cannot have arrays of new components (like QFormEx)
-Multiple WndProcs (see hooking discussion, we might get a better fix here).

So should you use RapidQ2? Why not? Just look at the code in the file and you could learn alot about the power of RQ.

-happy computing JohnK