This repository was archived by the owner on Dec 20, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 8
Javadoc
Ángel Serrano edited this page Apr 3, 2014
·
1 revision
We think documentation is important to keep the code maintainable, so we have a few guidelines to follow:
All classes must contain a Javadoc comment on their headers, explaining the general use of the class and those aspects, regarding their methods and attributes, that need to be remarked.
All public methods must contain Javadoc information about how to use it, and parameters should also be commented, remarking special cases (e.g., when a parameter can be null).
Other comments, explaining some tricky part of the code, are always welcomed.
eAdventure - eUCM research group
- Setting up a Development Environment
- Contributing Guidelines
- Build Process
- Project structure
- Schema
-
Engine
- Files paths and FileResolver
- Binding Schema elements with Engine elements
- Managing the game view through Layers
- Game loop and scene management
- IO
- File Resolver
- Assets: Converting schema objects to engine objects
- Engine Objects
- Actors
- Effects
- Testing the engine
- Editor
- Remote communication
- Release Process
- Other documentation