Stendhal code design: Difference between revisions

Jump to navigation Jump to search
Content deleted Content added
imported>Chad3f
imported>Hendrik Brummermann
No edit summary
 
(169 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Stendhal code design}}{{Navigation for Stendhal Top|Developing}}__NOTOC__
This page gives a little overview about the Stendhal code.


== Development Environment ==


Stendhal is completely open source. So you can [http://arianne.sourceforge.net/download/stendhal-src.tar.gz download the source code] and have a look. If you plan to modify it and contribute to the project, we suggest that you use the Eclipse IDE and checkout the latest development state from our version control system.
== Client ==


There are good [[Configure a development environment (IDE)|tutorials]] to get you started with Eclipse.
=== Base Client ===


== Finding your way around the Code ==
The base client ([ideally] free of any specific UI) is '''StendhalClient'''. It is responsible for interacting with the server, maintaining private user information/state, and dispatching object events.


The next step is to find your way around the code. The Stendhal code base is roughly divided into the server, client and a little code that is used by both:


* [[Finding your way around the Stendhal Server Code]]
=== Entities ===
* [[Finding your way around the Stendhal Client Code]]
* [[Finding your way around the Stendhal Web Client Code]] (early development)


Entity's are created using '''EntityFactory.createEntity()'''. In this method, the appropriete implementation class is created, and initialize.


'''Example:'''


== Coding Standards ==
RPObject object = ...
Entity entity = EntityFactory.createEntity(object);
// Force the view to be created
entity.getView();
...
// Done with entity - free up resources
entity.release();


We try to follow [http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html SUN Java code convention], in order to create code that feels familiar to many developers.


Despite this:
The design is being transitioned to a Model-View-Controller (MVC) like framework. This will allow different visual implementations (like 2D, 3D, 4D?) to be plugged in with minimal (or no) changes of the model class.


* We use tab for all indentation. (One tab is equivalent to 4 spaces for display purpose.)
* We do not stick too closely to line length.


* We always use blocks in if-statements and loops, even if the block only consists of one single statement:
'''Model/Controller'''
<code>
if (condition) {
method();
}
</code>


Avoid evaluation and assignment in the same line like:
This contains all logical entity data, and is responsible for tracking all entity specific attribute changes in the RPObject that it wraps. Currently this also handles some of the UI controller functions.


* ternary operators, for example in:
The '''initialize()''' method is called with the RPObject that it will represent. This method is called after the constructor returns, but before anything else is [externally] called.
<code>String y = x==null ? "NULL": x.toString();</code>
When the client no longer needs the entity, it should call '''release()''', which should handling any cleanup that garbage collection only is insufficient.


* post-increment/decrement operators as in:
The class gets notified of object changes via the '''RPObjectChangeListener''' interface that it implements. This will be called for all changes to it's object (and immediate slot objects).
if (idx++ == 10) {

...

}

'''View'''

The current view implementation is Entity2DView. This is responsible for rendering an entity in a 2D view.

=== Sound System ===

''TBR''...


=== UI ===

The user interface (UI) is responsible for bringing together the base client and user interaction. The base class is '''StendhalUI''', and is extended by an appropriete implementation (currently j2DClient).


----

== Server ==