Do not link libmovit against SDL; only the unit tests need that.

[movit] / README

diff --git a/README b/README
index 702f29a6445e2309b5769277a3ab0b9c94773212..c74e8efbbdab8217dc20f4a24fc62044a2870ad4 100644 (file)
--- a/README
+++ b/README
@@ -39,10 +39,11 @@ for performance estimates.
 Still TL;DR, please give me the list of filters
 ===============================================
 
-Blur, diffusion, glow, lift/gamma/gain (color correction), mirror,
-mix (add two inputs), overlay (the Porter-Duff “over” operation),
-scale (bilinear and Lanczos), sharpen (both by unsharp mask and by
-Wiener filters), saturation (or desaturation), vignette, and white balance.
+Blur, diffusion, FFT-based convolution, glow, lift/gamma/gain (color
+correction), mirror, mix (add two inputs), luma mix (use a map to wipe between
+two inputs), overlay (the Porter-Duff “over” operation), scale (bilinear and
+Lanczos), sharpen (both by unsharp mask and by Wiener filters), saturation
+(or desaturation), vignette, and white balance.
 
 Yes, that's a short list. But they all look great, are fast and don't give
 you any nasty surprises. (I'd love to include denoise, deinterlace and
@@ -56,6 +57,7 @@ TL;DR, but I am interested in a programming example instead
 Assuming you have an OpenGL context already set up:
 
 <code>
+  using namespace movit;
   EffectChain chain(1280, 720);
 
   ImageFormat inout_format;