Great, the documentation blows - not even a faq. Well, you've got a pretty long road ahead. You're going to need know the MOOP class hierarchy so that you can implement your own 'specialized' objects via inheritance. For example....

The point if Muds - although I am not sure how far this one was implemented - is that objects are created and modified on the fly by folks who have permission.

So, in moopdirect.py (or you can run moopsoc) at the prompt - as a wizard - I could make a new room by:

@dig s to Lobby

And then I can edit the description of the lobby with an edit command.

For a gun I did (I think)

@create $agent as Gun

It mods the game on the fly - no restart. So now I have a gun - I can carry it, drop it, pick it up. Thats it.

I was told that if I can master MOOP, I will fully understand OOP. I think it means I will have to delve into the code as well. Its commented OK, but I didn't see a module organization. Like, I know what moopsoc does, but thats only cus I opened it first. I'm not totally daft, but knowing the organization would help mucho.

You're right - the docs suck for this.

Check out the code for moopsoc.py. I was wondering if I could mod it to use for SMUG.

Anyways - maybe this weekend I will toy with it again. I did finally manage to log on remotley.

I was thinking about this for a bit the other day when I read the web page. On the one hand, this isn't too impressive since dynamic binding is required for all OOP languages. OTOH, it is a bit of a tricky implementation issue. See below.

MantaBase wrote:

I was told that if I can master MOOP, I will fully understand OOP.

There is a lot more to OOP then just creating and instantiating objects. The syntax is easy. Understanding OOP is about understanding OODesign. It is about understanding the differences and appropriate use of assocations, composition, inheritance, polymorphism, etc. How to increase modularity, improve code reuse, etc. There is a lot to OOP, and I would venture to say that most professionals tend to screw it up.

Initially, I would say that you should learn the terminology, the goals of OOP, how it achieves the goals, and then write the classic shapes exaple found in many books.... triangle, square, rectangle, circle, be able to compute the area and perimeter/circumference of each.

MantaBase wrote:

I wonder what the security issues are?

That is one of the tricky implementation issues. Java, for example, has mechanisms to help prevent class spoofing. Without better understanding their code and how Python loads classes, it is hard to say what level of security is involved here. The other issue that applies to non-interpretted languages is how do you compile the classes.

Who is online

Users browsing this forum: No registered users and 4 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum