X-Git-Url: https://git.sesse.net/?a=blobdiff_plain;f=README;h=8a85fb4af61fa0daf5f00caaea89b3b86fc6fab9;hb=7f1c8bb8b3ce08b94054f0a8990e5b8225d36036;hp=90345948f3749317c3ca084fd21e4b6c2ded58e3;hpb=0059fbc390f8a50b5848cc9de52d4208450c7d71;p=movit

diff --git a/README b/README
index 9034594..8a85fb4 100644
--- a/README
+++ b/README
@@ -26,7 +26,7 @@ OK, you need
   you're home free.
 * The [Eigen 3] and [Google Test] libraries. (The library itself
   depends only on the former, but you probably want to run the unit tests.)
-* The [GLEW] library, for dealing with OpenGL extensions on various
+* The [epoxy] library, for dealing with OpenGL extensions on various
   platforms.
 
 Movit has been tested with Intel GPUs with the Mesa drivers
@@ -56,6 +56,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;
@@ -153,9 +154,10 @@ instead of on input? And I can promise you that once we move to more
 wide-gamut color spaces, like the one in Rec. 2020 (used for UHDTV), the
 difference will be anything but subtle. As of [why working in linear
 light matters](http://www.4p8.com/eric.brasseur/gamma.html),
-others have explained it better than I can; note also
-that this makes Movit future-proof when the world moves towards 10-
-and 12-bit color precision. The extra power from the GPU makes all of this
+others have explained it better than I can; note also that this makes Movit
+future-proof when the world moves towards 10- and 12-bit color precision
+(although the latter requires Movit to change from 16-bit to 32-bit floating
+point, it is a simple switch). The extra power from the GPU makes all of this
 simple, so do we not need to make too many concessions for the sake of speed.
 
 Movit does not currently do ICC profiles or advanced gamut mapping;