Things that haven't been done yet plus long range dreams: ******************** Short Range ******************** - More testing. E.g., have player be called by actors in test.t, to make sure ANSWER PHONE works. - Some TODO's in the code ******************** Medium Range ******************** - Add "(on the phone)" to statusRoot? - Redirect goodbyeverb to hangup! Note that it's not trivial. Changing doGoodbye doesn't work for chatter, because some things call goodbyeResponse without going through doGoodbye. And changing goodbyeResponse doesn't work because then anyone who overrides it will have to put in the call to actor.phone.doHangup(actor) or something. Ick. - Redirect doUnboard to hang up? So that 'get off phone' works. (This seems like overdoing it, but otherwise you get "You're not on the phone!" Of course, another option would be to make a fixed_phone a vehicle!) ******************** Long Range ******************** - One-way phones, which would allow "broadcasting". In that case, you would need separate transmit and receive properties for each phone item. phone_connect/hang_up and the partner property would have to change to reflect whether you're able to hear, able to talk, or both. - Conference calls, broadcasting to multiple people, speaker-phone. (phone.speaker could be a list, allowing > 1 person to be addressed. Then phone.connect would use += or -=.) - Allow a (non-mobile) phone to move around within certain rooms (depending on the cord or cordless reception), via some sort of allowed_room list. - For now, don't let PC pick fixed_phone up at all. We could have a phone_base class, and a receiver that went into the base. However, that would add all sorts of ugliness, because then you can't put the phone anywhere except the base, and you can't leave the room with the receiver, and other complications.