> I have found ( while fixing the corpse problem correctly ) that we had a
> very deficient way of managing containers relations, and I have *fixed* it
> by adding isContained, getContainer that returns teh object that contains
> this one and getContainerSlot.
> I am anyway really unsatisfied with the way slots works and I think that we
> need a better way of handling containers that slots, I mean, I think of
> something that really belong to RPObject instead of a different class... I
> have to think about it... just thinking aloud...
I'll try to test and view the code of other engines to see how they handle this.
> The other motivation of my post is the Stendhal API that has started to be
> created on my holidays.
> I created Stendhal as a way of testing Marauroa ( and not the other side ).
> Most of the code on Stendhal does really sucks and unfortunatelly is very
> ill commented ( Matthias has put an awesome effort on fixing that ).
> The point is that I think the idea of an API is a good idea, but I think the
> project ( Stendhal ) is a bit inmature for that attemp. Anyway, I think that
> as the job is already there the less we can do is use it. So my propose is
> to extend and embrace the API with new methods and remove functionality from
> StendhalRPRuleProcessor and StendhalActions.
> Any disagree?
No, I think your observation this is very, very true, and a good attempt in the right direction.
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!
Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130
Get latest updates about Open Source Projects, Conferences and News.