It would be neat if we had only one Tcl command - the QScript evaluator - and we could access all the CCTW features we need through that interface. Then, cctw_commands.cpp would not need to change as we add features. I will look into this over time as I learn Qt...
This may be harder than it sounds - you'd need a way of automatically mapping all the possible QScriptValue types to tcl types. This would have to be done at runtime by introspecting the QScript value types.
In Tcl, everything is a string. http://wiki.tcl.tk/3018 We could just return a string version of the object (a pointer address, anything) at the end of the cctw{} block.