add WMS GetCapabilities parser for WMS 1.1.0, 1.1.1, 1.1.1 WMS-C profile and WMS 1.3.0
make Travis build pass again
add an example
use namespace URI instead of prefix as suggested by @tschaub and discussed with @ahocevar
Only listen once for tile events

Assuming browser garbage collection cannot happen while we have listeners in the global registry, we need to listenOnce to avoid memory leaks with the tile queue.
Apply transform matrix to text coords

With this commit the transform matrix is applied to each texture coordinate, as opposed to each fragment. This leads to less calculation on the GPU.
Use vec2 for vTexCoord
Merge pull request #193 from elemoine/shaders

Apply transform matrix to text coords
Change view.rotate params: rotation and optional anchor.
Merge pull request #192 from fredj/rotation

Change view.rotate params: rotation and optional anchor.
Merge pull request #180 from bartvde/wmscapsclean

add WMS GetCapabilities parser for WMS 1.1.0, 1.1.1, 1.1.1 WMS-C profile
Don't re-lint files that have already passed after a lint failure
Merge branch 'master' of github.com:openlayers/ol3 into vector
Adding ol.Expression

This simple expression constructor will be used for symbolizer properties and the layer will generate symbolizer literals for rendering by evaluating any expressions with a feature as the this argument and feature attributes as the scope.  This allows generating labels that concatenate multiple attribute values together or displaying point symbols that are sized according to a population attribute divided by an area attribute, for example.

This implementation will not work in environments where the content security policy disallows the use of the Function constructor.  This is the case on browser extensions.  A more content-security-policy-friendly implementation would be to come up with a restricted grammar and write a lex/parser.  This is the road I started down, but this verison is far less code, and I think the security policy limitations are minor at this point.  This version will always be faster/lighter than a parser, so one is written in the future, it should only be pulled in where content security policy mandates it.