ae554a5061
Yes, it's not really the proper GL name for a linear-on-every-axis of a texture plus linear-between-mipmap-levels minification filter, but it has three redeeming qualities as a name: - LINEAR_MIPMAP_LINEAR sucks, as it introduces GL concepts like mipmaps in the API naming, while we're trying to avoid that; - people using GL already know what 'trilinear' means in this context without going all Khronos on their asses; - we're using 2D textures anyway, so 'linear on two axes and linear between mipmap levels' can be effectively approximated to 'trilinear'. I mean, if even the OpenGL official wiki says: Unfortunately, what most people think of as "trilinear" is not linear filtering of a 3D texture, but what in OpenGL terms is GL_LINEAR mag filter and GL_LINEAR_MIPMAP_LINEAR in the min filter in a 2D texture. That is, it is bilinear filtering of each appropriate mipmap level, and doing a third linear filter between the adjacent mipmap levels. Hence the term "trilinear". -- http://www.opengl.org/wiki/Texture then the horse has already been flogged to death, and I don't intend to be accused of necrophilia and sadism by flogging it some more. Prior art: every single GL tutorial in the history of ever; CoreAnimation's scaling filter enumerations. If people want to start using 1D or 3D textures they they are probably going to be using Cogl API directly, and that has the GL naming scheme for minification and magnification filters anyway. |
||
---|---|---|
.. | ||
accessibility | ||
conform | ||
data | ||
interactive | ||
micro-bench | ||
performance | ||
Makefile.am | ||
README |
Outline of test categories: The conform/ tests should be non-interactive unit-tests that verify a single feature is behaving as documented. See conform/ADDING_NEW_TESTS for more details. The performance/ tests are performance tests, both focused tests testing single metrics and larger tests. These tests are used to report one or more performance markers for the build of Clutter. Each performance marker is picked up from the standard output of running the tests from strings having the form "\n@ marker-name: 42.23" where 'marker-name' and '42.23' are the key/value pairs of a single metric. Each test can provide multiple key/value pairs. Note that if framerate is the feedback metric the test should forcibly enable FPS debugging itself. The file test-common.h contains utility function helping to do fps reporting. The interactive/ tests are any tests whose status can not be determined without a user looking at some visual output, or providing some manual input etc. This covers most of the original Clutter tests. Ideally some of these tests will be migrated into the conformance/ directory so they can be used in automated nightly tests. The accessibility/ tests are tests created to test the accessibility support of clutter, testing some of the atk interfaces. The data/ directory contains optional data (like images and ClutterScript definitions) that can be referenced by a test. Other notes: • All tests should ideally include a detailed description in the source explaining exactly what the test is for, how the test was designed to work, and possibly a rationale for the approach taken for testing. • When running tests under Valgrind, you should follow the instructions available here: http://live.gnome.org/Valgrind and also use the suppression file available inside the data/ directory.