Don't use LibGDX Image class everywhere

[Plastix]

We are using Images where we shouldn't be. Pretty sure Image is a UI element and PlaneActor shouldn't use it. See https://github.com/libgdx/libgdx/wiki/Spritebatch%2C-Textureregions%2C-and-Sprites

[JEphron]

Using images feels kinda weird to me too. Thing is, image is basically the actor equivalent of a sprite. See here. http://stackoverflow.com/questions/13780742/libgdx-difference-between-sprite-and-actor

On Feb 11, 2015, at 7:06 PM, Plastix notifications@github.com wrote:

We are using Images where we shouldn't be. Pretty sure a PlaneActor shouldn't be an image. https://github.com/libgdx/libgdx/wiki/Spritebatch%2C-Textureregions%2C-and-Sprites

\ Reply to this email directly or view it on GitHub.

[Plastix]

Maybe PlaneActor should be an actor so we can override the draw method. It might be nice to modify the sprite/texture of the plane as the plane turns. It would be nice to rotate the sprite so it looks like the plane is rolling.

[Plastix]

We can override Image's draw method but we may not need all the functionality that Image provides.

[Plastix]

We've addressed this.