51a6467968
Code: All references in the code not related to themes, keybindings, or GConf were changed from 'metacity' to 'mutter'. This includes, among other things, strings, comments, the atoms used in the message protocol, and the envvars used for debugging. The GConf schema file was reduced to the 3 settings new to mutter. The overall version was brought up to 2.27 to match current gnome. Structure: All files named '*metacity*' were renamed '*mutter*' with appropriate changes in the automake system. Files removed are doc/creating_themes, src/themes, doc/metacity-theme.dtd, metacity.doap. These files will eventually end up in an external gnome-wm-data module. Installation location: On the filesystem the mutter-plugindir was change from $(libdir)/metacity/plugins/clutter to just $(libdir)/mutter/plugins. The mutter-plugins.pc.in reflects these changes. Note: mutter.desktop.in and mutter-wm.desktop both continue to have X-GNOME-WMSettingsModule=metacity set. This allows gnome-control-center to continue using libmetacity.so for configuration. This is fine since most the general keybindings and wm settings are being read from /apps/metacity/* in gconf. |
||
|---|---|---|
| .. | ||
| get-tokens.py | ||
| Makefile | ||
| README | ||
| tokentest.c | ||
| tokentest.ini | ||
Tokeniser test ============== This directory contains a set of tools for checking the behaviour of the tokeniser for Metacity theme files. tokentest.ini contains a list of all expressions retrieved from all theme files on art.gnome.org, and mappings to what the tokenising should be, in a separate representation. get-tokens.py produces the template version of this; it will produce a file with no expected values. tokentest.c will either check that a tokeniser behaves according to tokentest.ini, or, if it finds a file, is empty it will print the values that the tokeniser it's using is producing. The makefile is a hacky attempt at letting you compile either against Metacity's existing tokeniser or one which uses GLib's "scanner". This code may or may not eventually end up in the automated test suite.