Complete documentation
Documentation should be completed with meaningful and stringent comments and Javadoc. This includes well chosen method and field names as well as parameters. Don't abbreviate where not necessary. Class names should not be redundant. "TuioConcreteAdapter" has both "Tuio" and "Concrete" in its name. One suffices.
Examples: Why call getObjectId() on TangibleObject? Is there another identifier than that of the object? Don't abbreviate object to obj in some cases.
- TangibleObject
- TangibleObjectBuilder
- TuiAdapter
- TuioConcreteAdapter
- BluetoothClient
- BluetoothServer
- ClientAdapter
- NetworkAdapter
- ServerAdapter
- TcpClient
- TcpServer
- XbeeAdapter
Same holds true for tests.