Add some sanity around response messages (spoken, screen, and xmpp)

The robot currently generations a lot of instructional messages and there 
is a mess of what is done with them.

Currently:

- Sometimes there are spoken, which can be muted, and repeated messages are 
suppressed.

- Some information goes out to the screen via 'print'. Handy when starting 
up the code or debugging but not practical in live operation where you 
can't see the screen.

- We use makeToast() sometimes to make more obvious on screen messages. 
They are easier to see but go away and any info is lost.

- Reply back via XMPP with the same info as above but only if in XMPP mode.

Somewhere in here is a need for some sanity around which method the user 
wants for communications and what is most helpful.

Original issue reported on code.google.com by team%cel...@gtempaccount.com on 2 Apr 2010 at 5:30

zmxu / cellbots

Add some sanity around response messages (spoken, screen, and xmpp) #17