It needs implement the client-part of the tracker spec

This is basic support for gameplay

The node-to-tracker protocol is a WIP, but there isn't any work being done on 
the node-to-node protocol.

This needs change.

The game needs a theme music.

The masternode should publish itself to some tracker

Someone wish to type:

    void method(CustomClass customObject);

But someone need to write:

    void method(QHash<QString, QVariant> customObject);

...and add custom checks and code in the implementation.

FIX THIS BULLSHIT in the libbta-level.

The tracker must:
*  List rooms
*  (un)publish rooms

Use openslp to implement LAN services discovery and publishing.
http://en.wikipedia.org/wiki/Service_Location_Protocol
http://www.openslp.org/

r7e03dee77828:
[http://qt-project.org/forums/viewthread/18732]
[http://stackoverflow.com/questions/11473168/fails-to-load-qml-extension-using-q
ts-svg-module]

The drafts are done, but the source code isn't moving on.

MUST:
* Handle keyboard events
* List rooms (tracker communication)
* Enter on a room
* Menus
* Render graphics

The basic master node code should handle explosions and movement.

Study how to add gamepads event handling in Qt event loop.

http://qjoypad.svn.sourceforge.net/viewvc/qjoypad/trunk/src/joypad.cpp?revision=
127&view=markup

Implements some GraphicsItem class that implements this spec:
https://docs.google.com/document/d/1JhRTnlEwwqwHwHJJq6OITXrpn8-iK-dZYu1yns96-E4/
edit?hl=en_US

Qual a convenção de código usar?

Ei pessoal, ai a gente tem que fazer uns rascunhos da interface que a gente vai 
implementar.


Alguem tem que ir fazendo e ir subindo para o svn.

The distributed nature of the game leaves some secutiry problems. We need to 
investigate solutions.

Must handle simple logic:
* Explosions (bombs, bricks and players)
* Movement (players)

Must publish itself in the tracker.