mirror of
https://github.com/brl/mutter.git
synced 2024-11-12 17:27:03 -05:00
8a537b6299
* clutter/Makefile.am: * clutter/clutter.h: Add ClutterBindingPool to the build. * clutter/clutter-binding-pool.c: * clutter/clutter-binding-pool.h: Add ClutterBindingPool, a data structure meant to hold (key symbol, modifiers) pairs and associate them to a closure. The ClutterBindingPool can be used to install key bindings for actors and then execute closures inside the key-press-event signal handlers, removing the need for big switch() or if() blocks for each key. * clutter/clutter-event.c: Consistently use "key symbol" instead of "key value". * clutter/clutter-event.h: Add more modifier masks. * clutter/clutter-marshal.list: * tests/conform/Makefile.am: * tests/conform/test-binding-pool.c: * tests/conform/test-conform-main.c: Add ClutterBindingPool conformance test. * tests/interactive/Makefile.am: * tests/interactive/test-binding-pool.c: Add interactive test (and example code) for the ClutterBindingPool usage. |
||
|---|---|---|
| .. | ||
| conform | ||
| data | ||
| interactive | ||
| micro-bench | ||
| tools | ||
| 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 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.