Client Object: Difference between revisions

Jump to navigation Jump to search
Content deleted Content added
imported>Javydreamercsw
No edit summary
imported>Javydreamercsw
 
(40 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Navigation for Marauroa Top|Internals}}
{{Navigation for Marauroa Developers}}


{{Future Concept}}


== Proposal ==
== Proposal ==
*Instead of having custom client objects in a per application basis define one that can be enhanced via plugins.
*Instead of having custom client objects in a per application basis define one that can be enhanced via plugins.
Line 7: Line 14:
**Those should be handled via plugins
**Those should be handled via plugins
*Standardize approach
*Standardize approach

== Example Implementation ==
[http://simple-marauroa.svn.sourceforge.net/viewvc/simple-marauroa/trunk/Simple-Server/src/simple/server/core/entity/clientobject/ClientObject.java?revision=101&view=markup Client Object]



== Discussion ==

I am strongly opposing putting such game specific attributes and logic into Marauroa. It might be a good idea to create a set of libraries that can help developing certain types of games by providing functionality that is typically used by a game of the respective type. But Marauroa should focus on client/server communication and database persistence. Marauroa does not even know about x and y as your wrongly claimed although most games have coordinates. So adding even more things such as grumpy, buddies, ignore in your code is out of scope for Marauroa. --[[User:Hendrik Brummermann|Hendrik Brummermann]] 18:07, 14 May 2011 (CEST)

I'm not saying that my example is the way to go, I'm saying it should be extensible enough. I use interfaces and define the client object at runtime loading by reflections like other objects are (i.e. world implementation). The same should be available for the client object.--[[User:Javydreamercsw|Javydreamercsw]] 22:17, 27 September 2011 (CEST)