Re: requesting official list of modules and versions for GNOME 2.14
- From: Thomas Wood <thos gnome org>
- To: Matthias Clasen <matthias clasen gmail com>
- Cc: Shaun McCance <shaunm gnome org>, release-team gnome org, desktop-devel-list gnome org
- Subject: Re: requesting official list of modules and versions for GNOME 2.14
- Date: Fri, 10 Feb 2006 21:33:30 +0000
Matthias Clasen wrote:
On 2/9/06, Shaun McCance <shaunm gnome org> wrote:
On Thu, 2006-02-09 at 10:58 +0100, Vincent Untz wrote:
On Thu, February 9, 2006 10:41, Davyd Madeley wrote:
On Thu, Feb 09, 2006 at 09:10:55AM +0100, Vincent Untz wrote:
+ gtk-engines: I quickly looked at the archives and couldn't find a
mail related to it (ie there's no mail with engines in the
subject ;-)). Is the issue a possible slowdown caused by the use of
We have two issues here:
(a) speed issues caused by Cairo; and
(b) changes in the default theme (which while may be popular are
also unpopular with others)
Isn't be an "issue" in the theme (and not the engine)?
Well, the new Clearlooks entails both the Cairo-enabled
Clearlooks engine in gtk-engines and the Clearlooks theme
data in gnome-themes. Both the engine and the theme data
have changed. The theme data is probably setting a few
things that are new to the engine, but most notably, it's
using a brigher and more saturated set of colors.
Both the engine and the theme data are responsible for
point (b). The engine is responsible for point (a).
Until somebody sits down and does measurements to show
that use of cairo in theme engines is responsible for measurable
slowdowns, this is just guesswork.
Is there any way of reliably profiling gtk engines? As far as I am aware
there is no way (short of actually placing hooks in the engine) of
knowing when the engine has finished painting a widget or window. If
anyone can think of a good way of profiling the speed of a theme, I
would be very interested to know.
] [Thread Prev