Texture binding + creation

Closes #49
Oh ok :)

> On Jul 19, 2014, at 15:24, Corey Richardson <notifications@github.com> wrote:
> 
> In src/device/tex.rs:
> 
> > +//! "Texture" is an overloaded term. In gfx-rs, a texture consists of two
> > +//! separate pieces of information: image storage description (which is
> > +//! immutable for a single texture object), and image data. To actually use a
> > +//! texture, a "sampler" is needed, which provides a way of accessing the
> > +//! texture data.
> > +
> > +use std::default::Default;
> > +
> > +/// How to [filter](https://en.wikipedia.org/wiki/Texture_filtering) the
> > +/// texture when sampling. They correspond to increasing levels of quality,
> > +/// but also cost. They "layer" on top of each other: it is not possible to
> > +/// have bilinear filtering without mipmapping, for example.
> > +///
> > +/// These names are somewhat poor, in that "bilinear" is really just doing
> > +/// linear filtering on each axis, and it is only bilinear in the case of 2D
> > +/// textures. Similarly for trilinear, it is really Quadralinear(?) for 3D
> No, I mean for the case of 3D textures. Each axis of the texture, plus all the mipmaps.
> 
> —
> Reply to this email directly or view it on GitHub.