First of all, MQ2 will stay how it is and will continue to be free to use, updated how it currently is each patch, etc.
ISXEQ is a sister project to MQ2, using most of the same code but running in Inner Space. Inner Space, my friends, is some of my commercial software, available only to subscribers and is of course closed source. ISXEQ however is open source, and distributed with MQ2.
ISXEQ is incomplete and needs conversions. Specifically, some commands still need to be converted. Many commands have already been done. The only thing that needs to change in most of these is the actual function prototype, and any parameter parsing. The rest uses the same stuff as MQ2 in most cases.
How would ISXEQ (and thus Inner Space) benefit you?
There are many things built into Inner Space that would benefit MQ2 users. For a few examples on the USER end:
* LavishScript, the internal scripting system used by Inner Space, supports multiple simultaneously running scripts (aka macros in MQ), data types have methods, scripts support while-endwhile with break and continue, as well as switches (e.g. run a separate set of commands depending on a single condition that may have many possible values)
* Inter-process communications are built in. Commands can be relayed between sessions on the same computer (will be extended to include networking later)
For developers:
* LavishScript does command parsing BEFORE commands are executed, rather than requiring commands to do the parsing (a la MQ). Commands, data types, and TLO functions use int argc, char *argv[] just like writing an actual console program (int main(int argc, char *argv[]))
* Services are a graceful way of having separate extensions use detours, rather than trying to detour things multiple times or *ahem* removing specific detours from MQ2Main so that your MQ2 plugin can detour it
Of course that's not everything, but a couple fun things anyway.
