Daniel Ribeiro

Each and every component of this framework should have, at the very least, a class comment description, like the following example: ``` /** * What am I? What do I...

Make use of: https://github.com/drgomesp/gogo https://github.com/drgomesp/groxy

Example: ``` go type MyService struct { DepOne SomeInterface DepTwo SomeOtherInterface } func New() *MyService { return &MyService{} } func (s *MyService) setDepOne(depOne *SomeInterface) { s.DepOne = depOne } func...

There must be a way to handle the circular dependency problem.

Add support for registering service definitions through configuration files

4

One should be able to register service definitions through a configuration file, as the example below: ``` go builder := NewBuilder() definition := builder.Load("services.json") ```

Currently, this is a [limitation](https://github.com/GoodBoyDigital/pixi.js/issues/725) that comes from [pixi.js](https://github.com/GoodBoyDigital/pixi.js). We might be able to find a _workaround_ to solve this.

Currently, this is a [limitation](https://github.com/GoodBoyDigital/pixi.js/issues/725) that comes from [pixi.js](https://github.com/GoodBoyDigital/pixi.js). We might be able to find a _workaround_ to solve this.

We should use the [ndarray](https://github.com/mikolalysenko/ndarray) module to work with 2D arrays.

We should be able to support [Tiled](http://www.mapeditor.org/) and parse the following formats: - JSON - XML - TMX

We must expose this library as a [bower](https://github.com/bower/bower) package.