Turning compositing on and off at runtime

On 2/15/06, Soeren Sandmann <sandmannredhat.com> wrote:
> Hi,
>
> Here's a patch that adds a new
/apps/metacity/general/compositing_manager
> preference to turn compositing on and off at runtime.
If noone sees a
> problem with it, I'll commit.

It looks like it breaks feature and string freezes.
_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

It's not really a new feature; it just activates the
currently dormant
metacity compositing.  Maybe it could be committed without
the schema?

And then maybe we can stop a bit of the compiz bickering.

-Rob

On Wed, 2006-02-15 at 17:23 -0700, Elijah Newren wrote:
> On 2/15/06, Soeren Sandmann <sandmannredhat.com> wrote:
> > Hi,
> >
> > Here's a patch that adds a new
/apps/metacity/general/compositing_manager
> > preference to turn compositing on and off at
runtime. If noone sees a
> > problem with it, I'll commit.
> 
> It looks like it breaks feature and string freezes.
> _______________________________________________
> metacity-devel-list mailing list
> metacity-devel-listgnome.org
> http://mail.gnome.org/mailman/listinfo/metacity-devel-
list
> 

_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

On Thu, 2006-02-16 at 00:42, Rob Adams wrote:
> It's not really a new feature; it just activates the
currently dormant
> metacity compositing.  Maybe it could be committed
without the schema?

Err, If turning on a "dormant" feature doesn't
violate feature freeze,
I'd like to know that too.

Thanks in advance

Bill

> And then maybe we can stop a bit of the compiz
bickering.
> 
> -Rob
> 
> On Wed, 2006-02-15 at 17:23 -0700, Elijah Newren wrote:
> > On 2/15/06, Soeren Sandmann <sandmannredhat.com> wrote:
> > > Hi,
> > >
> > > Here's a patch that adds a new
/apps/metacity/general/compositing_manager
> > > preference to turn compositing on and off at
runtime. If noone sees a
> > > problem with it, I'll commit.
> > 
> > It looks like it breaks feature and string
freezes.
> > _______________________________________________
> > metacity-devel-list mailing list
> > metacity-devel-listgnome.org
> > http://mail.gnome.org/mailman/listinfo/metacity-devel-
list
> > 
> 
> _______________________________________________
> metacity-devel-list mailing list
> metacity-devel-listgnome.org
> http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

On 2/15/06, Rob Adams <readamsreadams.net> wrote:
> It's not really a new feature; it just activates the
currently dormant
> metacity compositing.  Maybe it could be committed
without the schema?

Compositing isn't a new feature, but that's kind of beside
the point;
adding the ability to turn something on and off dynamically
is itself
a new feature.  It may be one worth getting approval for,
and since it
is relatively self-contained and has few side-effects or
changes in UI
or anything that might otherwise be scary (with the
exception of the
string freeze break which you suggest a workaround for), it
might not
be too hard to get through the approval process this late.  
 The
question is whether it's worth the trouble or whether we
should just
wait...
_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

On Thu, Feb 16, 2006 at 08:40:20AM -0700, Elijah Newren
wrote:
> On 2/15/06, Rob Adams <readamsreadams.net> wrote:
> > It's not really a new feature; it just activates
the currently dormant
> > metacity compositing.  Maybe it could be committed
without the schema?
> 
> Compositing isn't a new feature, but that's kind of
beside the point;
> adding the ability to turn something on and off
dynamically is itself
> a new feature.  It may be one worth getting approval
for, and since it
> is relatively self-contained and has few side-effects
or changes in UI
> or anything that might otherwise be scary (with the
exception of the
> string freeze break which you suggest a workaround
for), it might not
> be too hard to get through the approval process this
late.    The
> question is whether it's worth the trouble or whether
we should just
> wait...

We still have a month of testing time. Compositing is a
major
feature for the group of motivation-power-users Jdub talks
about. I say we should do it. With compositing off by
default, we're
not taking extensive risks.

--d

-- 
Davyd Madeley

http://www.davyd.id.au/
08B0 341A 0B9B 08BB 2118  C060 2EDD BB4F 5191 6CDA
_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

On 2/16/06, Elijah Newren <newrengmail.com> wrote:
> On 2/15/06, Rob Adams <readamsreadams.net> wrote:
> > It's not really a new feature; it just activates
the currently dormant
> > metacity compositing.  Maybe it could be committed
without the schema?
>
> Compositing isn't a new feature, but that's kind of
beside the point;

Okay, so this was kind of beaten to death already but I
think it's
also worthwhile to distinguish between various forms of
'new'.  Since
it's not compiled in by default and requires the
--enable-compositor
configure switch to get it compiled, it has received
extremely little
testing and thus ought to be considered a new feature from
the
standpoint of the Gnome release even if it's not
"new" code.
_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

Em Qui, 2006-02-16 às 08:40 -0700, Elijah Newren escreveu:
> On 2/15/06, Rob Adams <readamsreadams.net> wrote:
> > It's not really a new feature; it just activates
the currently dormant
> > metacity compositing.  Maybe it could be committed
without the schema?
> 
> Compositing isn't a new feature, but that's kind of
beside the point;
> adding the ability to turn something on and off
dynamically is itself
> a new feature.  It may be one worth getting approval
for, and since it
> is relatively self-contained and has few side-effects
or changes in UI
> or anything that might otherwise be scary (with the
exception of the
> string freeze break which you suggest a workaround
for), it might not
> be too hard to get through the approval process this
late.    The
> question is whether it's worth the trouble or whether
we should just
> wait...

Isn't this feature important for a11y? (the ability to run
a different
composite manager is important)

As a translator I wouldn't mind the two extra strings,
though I only
speak for myself and not the i18n team. 

Cheers,
Evandro

_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

On Fri, 2006-02-17 at 00:58, Evandro Fernandes Giovanini
wrote:
> Em Qui, 2006-02-16 às 08:40 -0700, Elijah Newren
escreveu:
> > On 2/15/06, Rob Adams <readamsreadams.net> wrote:
> > > It's not really a new feature; it just
activates the currently dormant
> > > metacity compositing.  Maybe it could be
committed without the schema?
> > 
> > Compositing isn't a new feature, but that's kind
of beside the point;
> > adding the ability to turn something on and off
dynamically is itself
> > a new feature.  It may be one worth getting
approval for, and since it
> > is relatively self-contained and has few
side-effects or changes in UI
> > or anything that might otherwise be scary (with
the exception of the
> > string freeze break which you suggest a workaround
for), it might not
> > be too hard to get through the approval process
this late.    The
> > question is whether it's worth the trouble or
whether we should just
> > wait...
> 
> Isn't this feature important for a11y? (the ability to
run a different
> composite manager is important)

Well, it may have important a11y impact, in that a11y may
need to do the
compositing (for magnification) instead of metacity
(until/unless
metacity takes on the magnification service tasks).  For
that reason,
it's potentially risky to either make it nonconfigurable,
or even to
turn it on by default (and thus develop a 'dependency' on
it).  Of
course we don't want magnifier users to be left behind when
the other
cool compositing features land.

That said, I think the metacity team is aware of the a11y
concerns and I
am optimistic that the end result will be very good for
magnification as
well as everyone else.

Bill

> 
> As a translator I wouldn't mind the two extra strings,
though I only
> speak for myself and not the i18n team. 
> 
> Cheers,
> Evandro
> 
> _______________________________________________
> metacity-devel-list mailing list
> metacity-devel-listgnome.org
> http://mail.gnome.org/mailman/listinfo/metacity-devel-
list

_______________________________________________
metacity-devel-list mailing list
metacity-devel-listgnome.org
http://mail.gnome.org/mailman/listinfo/metacity-devel-
list