SourceForge has been redesigned. Learn more.

Interface proposals and other stuff

  • Anonymous

    Anonymous - 2010-03-30

    Hi, I know I've been silent for a while, but I've been working on ironing out my game and I'm almost there! Already made my first release and almost ready for the second which would take it to alpha stage. I was able to find the issue about modified RPObjects
    ( so I'm almost ready to use your jars as they are released from you.

    I already tried using your version of 2.6.3 (yes I'm a lilttle behind since I'm focused on making the game work, upgrading to your latest is in my road map after alpha release as other improvements) but noticed that I have some interfaces defined that I use all around.

    AttributeInterface (extracted from
    RPObjectInterface (extracted from RPObject)

    Nothing new at all but used in Simple-Mararoa project to abstract the way RPObjects are stored into the database as I'm providing means to configure at run time the object used on the client.

    Why I did that? Well, as they are right now its impossible to make a generic server like Simple-Marauroa since you need to bind to an specific implementation of an RPObject. With this I provide the user liberty of defining its client object at run time  but of course it needs to fit a template so the server keeps working properly.

    Would a patch like that be accepted?

    Not sure if I'm making sense here. Feedback is welcomed as always from the gurus… This goes back to this post:

  • Anonymous

    Anonymous - 2010-05-25

    I should have a patch available soon as I'm upgrading to Marauroa 3.6. Still feedback is more than welcomed!



Cancel  Add attachments