WCell:Developer Guide
From WCell
This Guide is supposed to give an overview of the applied coding conventions and all available tools to developers who work with WCell, including developers of Addons.
This article is still in the making...
[edit] Developing
Every developer should want his/her code to have the following feats:
- Working
- Bug-free
- Easily maintainable
- Well readable
- Easily extensible
No developer should except him or herself to be able to write such code at any given time.
Developing code takes a lot of time, and so does mastering the art of writing code. Do not expect too much of yourself and try to set realistic goals.
If you want to learn coding, join a project with a mature approach to development that is in the range of your interest. Learning with others and using their expertise on how to write or handle code would be of greatest advantage to the apprentice.
See the Coding Guide for further reference.
After being so philosophic, lets see what we can use to make our developer-life a little easier when working with WCell:
[edit] The Tools
Here are some tools we have implemented so far:
- Very simple and extensible Command system: Dev:Commands
- The possibility of easily making any global variable in code configurable by Administrators: Configuration
- The Packet Analyzer to analytically work with Packets sent forth and back between client and server or just make them human-readable
- Pluggable Addon System
- Flexible Content System
- WCell's Version Updater
- Dynamic Initialization Routine
- A basis for Unit Tests
Here are some feats, provided by 3rd party tools that we are using:
- NHibernate to easily bind C# Datastructures to a Database
[edit] References
- An overview over WCell Development
