I know what you’re thinking: you thought this blog was dead. Well, I have to apologise for the lack of attention to Metacity recently. I’ve been trying to rectify this, and I’ll try to keep it up. There have been things sucking up my time, but they are mostly over now. I’ve closed a few bugs over the last few days; I’m trying to review all the unreviewed patches first. Next to go is GNOME bug 156543.
Posting to the Metacity blog was taking more of my time than actually working on Metacity, so I will try to cut back on the posts. But if someone from the GNOME project who has a basic idea about window managers would like posting rights here, that would be fine with me.
Some actual news: As well as the standard git tree at gnome.org, I have pushed Metacity to github and gitorious, so you can easily clone it if you need to. I will try to keep them up to date. I hope this is useful for people who would like to hack on it.
Photo © Federico, cc-by-nd.
Listen to this.
Welcome back, gentle reader, to the Metacity Journal, which now talks to you over your cornflakes. This may not be a long-term feature, but your chronicler thought it worth trying.
It’s been a quiet few days in the world of Metacity, but here’s the latest news. As ever, feel free to dive in on any of the bugs mentioned.
The recent post about why window matching is currently impossible brings up a chicken-and-egg question. The window manager doesn’t do window matching because it’s nearly impossible, since windows don’t identify themselves, but windows don’t identify themselves because there’s no need, since the window manager doesn’t support it. Perhaps adding window matching as an experimental option would help persuade people to add the GTK call to enable window matching in their programs. Meanwhile, Thomas has suggested making these changes as a new GNOME Goal.
There has been some offlist discussion about reviving Vectacity, the SVG-based branch. This would make theme editing a fair amount simpler.
- GNOME bug 560142: AisleRiot and Metacity arguing over fullscreen mode.
- GNOME bug 533277: session restoration problems
- GNOME bug 524468: problem with the screenshot button reported; Thomas cannot reproduce it
- GNOME bug 487356: there are focus issues if a buried window is fullscreen. This is quite important to fix and is currently at the top of the hitlist.
Around the blogs
And that’s all until next time.
Two of you emailed me out of the blue today to remind me that GNOME bug 504692 has an unreviewed patch on it that you’d like looked at before the next unstable release. Thank you! This is a very good way of reminding me of such things, and I think that holds true for most maintainers: we get dozens of pieces of email a day from Bugzilla, and a personal note is a bit of a stronger push.
(That said, don’t overdo it; I’m drowning in email as it is.)
The patch needs me to set up dual screens to test it. There was a joke earlier that there needed to be a collection to buy me a second screen, since all Metacity development is done on a laptop; I have now been lent a second screen. However, for the next couple of days I’ll be unusually busy in the world of non-GNOME software, and then I need to figure out how to get Xinerama and so on working on the new setup. I shall, of course, keep you up to date with extreme punctiliousness.
Thanks for being such a friendly and helpful bunch of users.
Hooray, hooray, the first of May, Metacity unit and regression testing begins today. Okay, so it doesn’t scan as well as the original, but it’s almost as exciting. Well, perhaps. I (Thomas) am planning the framework at present, have something fairly solid in my head now, and will probably post something up here in the next few days when I have it planned out so everyone else can argue it :)
As well as this, here are the bugs on the front burner for me for this week: if you want something else fixed, talk to us about it (and send us patches!):
* GNOME bug 499996 (possibly aka Debian bug 443933 possibly aka Debian bug 460712)
* Launchpad bug 221144 (possibly aka Debian bug 476386) (may be related to the above, although perhaps not)
* Launchpad bug 216049 – restore to wrong workspace
* GNOME bug 468075 aka Launchpad bug 133541 – vertical maximisation ignores struts, apparent regression
* GNOME bug 528927 — something to do with _net_wm_state_demands_attention, details a little unclear
If you think it should be different, feel free to advocate below.
Are there distributions not using Launchpad which have a systematic way to link to upstream bugs that we could make use of for keeping people installed?
This is the first time we’ve used the new “bug hitlist” tag, which may become partly automated like Metacity Journal is. If you’re working on a bug in Metacity and you have an @gnome.org address, feel free to post bug hitlist entries; if you are and you don’t, feel free to comment to one of them and ask for one to be made or added to.
I shall post Metacity Journal tomorrow, I think, but I just wanted to acknowledge the particular good contributions that Santanu Chatterjee has been making on fixing problems with keyboard grabs during drag-and-drop.