Pyogp/Documentation/Specification/pyogp.interop

Things to Do

This is a list of things that could be done.

1. Make a client package in Pyogp that is a high-level package that can be used to create a Pyogp client, or run a Pyogp bot.
   • Move out the following files into the package: test_chat, test_ogp_movement, test_teleport_inter
2. Make the tests that remain in pyogp.interop more test-driven, or more like unit tests that can be automated to check status of an OGP implementation.
3. Make the tests that remain in pyogp.interop better by not duplicating code (such as login) that is common to doing some sort of functionality. This means we may be able to split out some things like login or maintaining presence into high-level classes and putting it in either pyogp.lib.base or into pyogp.client. This is so that we don’t have to duplicate the code for every test we want to run (like we currently do).
4. Fix test_chat
   • find out what is going on with receiving chat messages from other users. The Message is always blank
   • find out why the bot always whispers, rather than just saying the message.
   • find out why the bot always sends a dot at the end of everything he says
5. Fix and extend test_ogp_movement
   • find a way to get the bot to stop when the arrow keys are released (rather than pushing the SPACE bar everytime)
   • find a way to rotate the bot. Currently, only movement is allowed, not rotation, so when the bots eventually get avatars, they will be strafing and such.
   • strip out some of this functionality so that it can be controlled by an automated script
   • give the bot the ability to fly
6. Fix test_teleport_inter and test_chat
   • To teleport in either of these, the user must change a config file (which can be done in real-time). A better approach would be to have the ChatWindow have a text box the user could type in which could be processed to find out what commands the user is trying to send.