Re: gtk-engines 2.6.x for GNOME 2.14

Thomas Wood <[email protected]>
Newsgroups gmane.comp.gnome.desktop,gmane.comp.gnome.themes
Message-ID <[email protected]>
Evandro Fernandes Giovanini wrote:
> Em Sáb, 2006-02-11 às 17:09 +0000, Thomas Wood escreveu:
>> This is to confirm that the gtk-engines team have decided that, in light 
>> of the recent issues raised on various mailing lists, and our own 
>> assessment of the progress we have made towards the goals for 
>> gtk-engines 2.8, we would like to suggest that GNOME 2.14 uses the 2.6.x 
>> series of gtk-engines.
>>
>> We have had some excellent feedback and testing from our 2.7.x 
>> development series by it being in the current GNOME 2.13 releases, and 
>> we'd like to thank everyone for their help and comments. However we feel 
>> that because of a number of unresolved issues, including the speed, 
>> appearance, and general completeness, we cannot recommend it be included 
>> in the GNOME 2.14 releases.
>>
>> I will be reverting jhbuild to use the gnome-engines-2-6 branch for the 
>> 2.14 module set. The HEAD branch of gtk-engines should be used when the 
>> 2.16 module set is created.
>>
> 
> Any chance of adding the clearlooks engine from 2.7 with a name like
> libclearlookscairo.so or libclearlooks2.so? 
> (the default theme, "Clearlooks", would still be based on the 2.6
> version). 
> 

Sorry, but no. The whole reason for not releasing gtk-engines 2.8 yet is 
because the engines are not ready for general consumption. You will, of 
course, be free to use the unstable 2.7.x series if you wish instead, 
and we will continue making 2.7.x releases until the cairo versions of 
the engines are ready. In fact, I hope the 2.8 stable release of 
gtk-engines will in ready before GNOME 2.16, so there will be plenty of 
time to finish testing and fixing before 2.16.

-Thomas
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.