According to HIG (section 2.4.1), ctrl+f11 is designated as the full screen key event. It's up to individual apps to follow this, metacity is only responsible for the act of putting the window in fullscreen mode when asked to do so AFAIK.

There isn't a key specified in the HIG for shade/unshade. Should we get it added to HIG if we want it in Metacity, or can Metacity do it anyway? How many people still use shading these days?

Metacity already supports shading/unshading, that's why I asked for the titlebarbutton.

Um, Metacity has a titlebar button for shading and unshading; it has for a while.

really? how is it called? I tried both shade and toggle_shade in "/apps/metacity/general/button_layout" but both didn't work

you're right. I tried with the Schwermetall, Clearlooks and Simple Themes, but it didn't work, now I tried with the Crux Theme and it works. Dump me.

It's "shade", but you need to be using a theme which defines how the shade and unshade buttons should be drawn (i.e. one which ships a metacity-theme-2.xml file, and most of them don't), otherwise there's no reasonable way it could work; bug 96229 was where this was introduced.

Do you still want the fullscreen button?

Yes, that would be nice.

BTW: stick, above, shade, minimize, maximize, close and menu are available, right? or did I miss one?

Um, why would having a fullscreen button make any sense?  Isn't the point of having the buttons in the titlebar to let users toggle states that they don't know they keybindings for?  Users aren't going to be able to unfullscreen their application once it's in fullscreen state because the titlebar won't be shown with the appropriate buttons.  You may then be stuck in a situation where users don't know how to recover from what they just did.

I do agree with this point; I just wanted to make sure I understood what Christopher was asking for (so I knew, say, whether this was wontfix or dependent on the theme v3 tracker bug or whatever).