mutter

brl/mutter

History

Robert Bragg 33994caa71 [cogl-material] Support string based blending and layer combine descriptions Setting up layer combine functions and blend modes is very awkward to do programatically. This adds a parser for string based descriptions which are more consise and readable. E.g. a material layer combine function could now be given as: "RGBA = ADD (TEXTURE[A], PREVIOUS[RGB])" or "RGB = REPLACE (PREVIOUS)" "A = MODULATE (PREVIOUS, TEXTURE)" The simple syntax and grammar are only designed to expose standard fixed function hardware, more advanced combining must be done with shaders. This includes standalone documentation of blend strings covering the aspects that are common to blending and texture combining, and adds documentation with examples specific to the new cogl_material_set_blend() and cogl_material_layer_set_combine() functions. Note: The hope is to remove the now redundant bits of the material API before 1.0		2009-05-28 02:43:28 +01:00
..
conform	[cogl-material] Support string based blending and layer combine descriptions	2009-05-28 02:43:28 +01:00
data	Adds a CoglMaterial abstraction, which includes support for multi-texturing	2008-12-22 16:35:52 +00:00
interactive	[cogl] Remove max_waste argument from Texture ctors	2009-05-23 19:35:19 +01:00
micro-bench	[test-text-perf] Small fix-ups	2009-05-21 17:43:41 +01:00
tools	[tests/tools] Don't install libdisable-npots.so	2009-02-24 17:04:05 +00:00
.gitignore	[gitignore] Ignore two newly introduced tests	2009-03-25 20:58:22 +00:00
Makefile.am
README

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 micro-bench/ tests should be focused perfomance test, ideally testing a single metric. Please never forget that these tests are synthetec and if you are using them then you understand what metric is being tested. They probably don't reflect any real world application loads and the intention is that you use these tests once you have already determined the crux of your problem and need focused feedback that your changes are indeed improving matters. There is no exit status requirements for these tests, but they should give clear feedback as to their performance. If the framerate is the feedback metric, then the test should forcibly enable FPS debugging.

The interactive/ tests are any tests whos 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.

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 aproach taken for testing.