Just for clarification…
The new “default” theme in GNOME 2.15, called “Clarius”, is exactly the same as Clearlooks, except for the scrollbars.
The Clearlooks theme has glossy blue scrollbars, where as Clarius does not. This was the result of feedback from several members of the community about the new clearlook-cairo additions.
We want your screenshots for the GNOME 2.16 release notes!
Pile them up and we will put them on display. The better looking ones will get put in the release notes.
gtk-engines provides a central location for commonly used GTK+ engines.
It currently supplies several engines and default themes for those which
Many thanks to Andrew Johnson, Benjamin Berg and Benjamin Otte for their contributions to this release.
This will probably be the last release before 2.8.0, and we have now
achieved our goal of converting all the engines distributed in
gtk-engines to use the cairo graphics library, including:
Crux, Clearlooks, HighContrast, Industrial, Mist, ThinIce, Redmond and
Glide (a temporary cairo replacement for Smooth for the Glider theme)
Besides this goal, there have also been numerous improvements to the
engines in this release cycle, including:
- the creation of a shared library of common functions, macros and
- vigorous testing to ensure the stability of all the engines
- and many, many visual improvements
However, there are still likely to be a few bugs left, so please do file
any issues and problems you have in bugzilla.
Overview of Changes in 2.7.8 (since 2.7.7)
Highlights in this release include:
- Add paranoia and deprecated configure flags
- Improve HighContrast (HC) engine inconsistent state check mark
- Use the base/text values for expander arrow in HC (fixes invisible
- Improve visibility/contrast of checks in HC
- Fix broken Clearlooks menu on panel check
- Implement a focus rectangle for GtkEntry
- Many other visual improvements to Industrial
See the ChangeLog for full details of other smaller fixes and enhancements.
Fixed bugs in this release:
- 349575 – C89 Fixes (Last C89 Patch to close bug)
- 350606 – Location of G_GNUC_INTERNAL breaks Solaris build
- 351057 – Leak in clearlooks_style.c
Yes, we’re already getting ready for the next Guadec. In case you’re not up to speed on the details so far, the venue has been booked for the 15th – 21st July 2007.
We know this may clash with another developer conference, but those details have not been confirmed yet. There are several reasons why we are holding it later than other years, one of which was that many students are unsure of their commitments until the end of July, and asked if it could be later.
Paul visited the venue (Conservatiore, Birmingham, UK) yesterday and took some pictures. Discussion is currently taking place on the gnome-uk list, but may move over to the guadec lists soon.
What does it mean to be a foundation member?
My personal response is that it’s a recognition of the time and effort I have put into GNOME related projects, whether it be helping out at LinuxWorld, administrating art.gnome.org, or writing patches for gnome-theme-manager and helping to maintain the gtk-engines, gnome-themes and gnome-backgrounds modules.
I have a feeling my original reason for wanting to become a foundation member wasn’t quite so honourable. I needed a gnome.org mailing address to use for the frequent communication I was doing on behalf of my administration work on art.gnome.org. Since then it has grown to mean more to me, in terms of acceptance and appreciation. I can’t believe it’s been just over two years since then, and I’m still here, even more active and involved than before.
It would be interesting to find out other people’s reasons for becoming foundation members, and even how they got involved in the first place. I spent some time asking people this at Guadec, and it was quite enlightening on the subject of how to encourage people to get involved. One of my conclusions based on the experiences I have had, is that no matter how hard you encourage someone, they will not become committed unless they have enough self motivation. Free and Open Source development is all about doing things to make your own life better. If it’s not for this reason that you get involved, then I doubt you will ever find satisfaction in what you work on in any Free Software project. Maybe we should focus less on trying to encourage developers, but more on trying not to discourage them. If they’re good open source type people, then they won’t need much encouragement, but they certainly don’t need discouragement.