Android Client

This section explains how to start working with the project of the Android client app. It's contents and structure as well as the applied libraries are explained.

Getting started

It is recommended to use Eclipse in combination with the ADT plugin for working with Android projects. For checking out the project from GitHub, the plugin EGit can be used.

Packages

activity

Contains the classes for the particular views shown in the app's UI (read more). They also contain some of the game logic, like subclasses representing the current state of the game, which is important for processing incoming messages.

game

Contains some further classes, like 'game' or 'player'. This packet is also the location of a class responsible for the XMPP connection and communication.

message

Contains the classes representing the particular message types. Usually these classes are created automatically by using the msdl file and the xslt scripts for transformation of msdl to code.

service

In contrast to the package 'activity', which contains the classes representing the UI views, this package contains the classes needed by the background service of the app (read more). Services need less resources than activities, therefore the app keeps running even if the Android System kills the activities which are not on top of the stack.

Used libraries

asmack-android-17-0.8.3.jar

Asmack is an Android port of the XMPP library Smack (read more). It is needed for setting up the connection to the server as well as for sending and receiving of messages.

mobilis_classes.jar

This jar contains some classes borrowed from the MobilisServer and MobilisXMPP projects, like abstract message types or messages for creating new service instances. It would also be possible to use these classes by referencing the mentioned projects, but since they are using the standard Smack XMPP library, conflicts with the Asmack library are to be expected.

---

Up: Home