-
Notifications
You must be signed in to change notification settings - Fork 8
Project structure
eAdventure project is organized in several maven projects, each of them with separated and defined functions:
Build tools to generate eAdventure releases. This project contains those tasks necessary to generate eAdventure releases, but are related to more than one project.
For example, this module takes care of generating editor skins, since these are shared by several maven projects.
Schema contains all the JSON Schema (and Java classes generated from them) representing the existing elements in the eAdventure game model.
It contains two main parts: all the JSON schema, placed in src/main/resources, defining the eAdventure game model, and the Java autogenerated classes, placed in src/main/java. These classes are generated with the JsonSchema2Pojo maven plugin.
Engine contains the eAdventure game engine, and includes 4 subprojects,core, a platform independent project with the engine core, and other three projects, desktop, android and html, one for each platform supported by eAdventure. These subprojects contains platform specific implementations for some of the eAdventure games features.
Editor contains the eAdventure game editor, and includes 3 subprojects, core, with the platform independent core of the editor, and another 2, desktop and android, with platform specific implementations of the editor.
Although not a maven project per se, assets contain all the resources used by the different projects, following the libgdx project structure
Internationalization (abbreviated i18n) is also performed via assets
Mockup contains an experimental android editor to quickly generate eAdventure mockup games.
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