X-Git-Url: https://git.sesse.net/?p=movit;a=blobdiff_plain;f=README;h=05ba9f3cd89f292cf9a10e1d8fd93a71b9f5fb00;hp=b6b2b9d9a946561639d33079a6f54187026aff13;hb=236a0ad8b604d5b3bff53f40b600991168f76800;hpb=144496bf79000c3971090195fbfedcb2cb22a0be diff --git a/README b/README index b6b2b9d..05ba9f3 100644 --- a/README +++ b/README @@ -25,8 +25,9 @@ OK, you need part of OpenGL 3.0 or newer, although most OpenGL 2.0 cards also have what's needed through extensions). If your machine is less than five years old _and you have the appropriate drivers_, 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.) + GLES3 (for mobile devices) will also work. +* The [Eigen 3], [FFTW3] and [Google Test] libraries. (The library itself + does not depend on the latter, but you probably want to run the unit tests.) * The [epoxy] library, for dealing with OpenGL extensions on various platforms. @@ -55,8 +56,8 @@ all research-grade problems, and Movit is currently not there.) TL;DR, but I am interested in a programming example instead =========================================================== -Assuming you have an OpenGL context already set up (currently you need -a classic OpenGL context; a GL 3.2+ core context won't do): +Assuming you have an OpenGL context already set up (either a classic OpenGL +context, a GL 3.x forward-compatible or core context, or a GLES3 context): using namespace movit; @@ -92,12 +93,12 @@ OK, I can read a bit. What do you mean by “modern”? Backwards compatibility is fine and all, but sometimes we can do better by observing that the world has moved on. In particular: -* It's 2014, so people want to edit HD video. -* It's 2014, so everybody has a GPU. -* It's 2014, so everybody has a working C++ compiler. +* It's 2015, so people want to edit HD video. +* It's 2015, so everybody has a GPU. +* It's 2015, so everybody has a working C++ compiler. (Even Microsoft fixed theirs around 2003!) -While from a programming standpoint I'd love to say that it's 2014 +While from a programming standpoint I'd love to say that it's 2015 and interlacing does no longer exist, but that's not true (and interlacing, hated as it might be, is actually a useful and underrated technique for bandwidth reduction in broadcast video). Movit will eventually provide