Greetings, POOP: Python Object Oriented Programming/Programmer/Program(s)....
I have finished the procedural Python version of the Text Adventure Game. See attached uuencoded zip file which contains tag10.py, data.py and actions.py. [uudecode tag.uue; unzip tag.zip; python tag10.zip] Now I am interested in learning how to DESIGN an object-oriented version of the game in Python. All my Python tutorials show me the mechanics of how to MAKE classes. What I'm interested in is the thought processes and/or guidelines that Tutors employ when they sit down to design a POOP. Can I use the procedural program as a specification? I'd like the input/output and gameplay to be the same. However, I'd like to design the program so it can be expanded in the future. If I'm not mistaken, 'reuse' is a design criteria? My main tutorial is: Programming Python for the Absolute Beginner 2E. Michael Dawson. Boston, MA: Thomson Course Technology, 2006. ISBN-13 978-1-59863-112-8 I also have access to online tutorials. Most of the tutorials I've seen are mainly about how to MAKE a class, ie. the mechanics of POOP. Give a person a fish, feed them for a day. Teach them to fish, and they'll be gone fishing all day. I already have examples of how to make classes. Can you explain how to DESIGN classes. (I see a difference here.) How do you design POOP? What are the guidelines you keep in mind to design "good" POOP? Can an absolute beginner learn to design POOP? 8^D -- b h a a l u u at g m a i l dot c o m "You assist an evil system most effectively by obeying its orders and decrees. An evil system never deserves such allegiance. Allegiance to it means partaking of the evil. A good person will resist an evil system with his or her whole soul." [Mahatma Gandhi]
tag.uue
Description: Binary data
_______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
