I agree about animations, apparently the setting doesn't affect
gnome-shell... I'll consider a feature request of something like a
setting 'bells-and-whistles', so, when disabled, Gnome accepts that
user is serious about disabling all this stuff :) It shouldn't be
accessible with dconf-editor thoug
- Mensaje original -
> Thanks for the answer, Marc-André!
>
> Few comments inline.
>
>
> On Tue, Jul 23, 2013 at 4:27 PM, Marc-André Lureau
> wrote:
> >
> > Hi
> >
> > On Mon, Jul 22, 2013 at 10:28 PM, Fedor Lyakhov
> > wrote:
> > > Hi everyone,
> > >
> > > I've made a bit of progres
Thanks for the answer, Marc-André!
Few comments inline.
On Tue, Jul 23, 2013 at 4:27 PM, Marc-André Lureau
wrote:
>
> Hi
>
> On Mon, Jul 22, 2013 at 10:28 PM, Fedor Lyakhov
> wrote:
> > Hi everyone,
> >
> > I've made a bit of progress on this issue - "disable wallpaper" and "disable
> > anima
Hi
On Mon, Jul 22, 2013 at 10:28 PM, Fedor Lyakhov wrote:
> Hi everyone,
>
> I've made a bit of progress on this issue - "disable wallpaper" and "disable
> animations" somewhat work with Gnome3. The code is very simple:
>
> static void disable_animation()
> {
> GSettings *desktop_settings =
>
Hi everyone,
I've made a bit of progress on this issue - "disable wallpaper" and
"disable animations" somewhat work with Gnome3. The code is very simple:
static void disable_animation()
{
GSettings *desktop_settings =
g_settings_new("org.gnome.desktop.interface");
g_settings_set_boolean(d
Hi,
On 07/05/2013 06:07 PM, Fedor Lyakhov wrote:
Thanks for your answers!
Looks like the issue is more complicated than I originally thought. But I'm
still excited to continue working on it.
Ok, I'm going to follow Hans' view now.
Good.
One thing I don't understand: why would we want to ap
Thanks for your answers!
Looks like the issue is more complicated than I originally thought. But I'm
still excited to continue working on it.
Ok, I'm going to follow Hans' view now.
One thing I don't understand: why would we want to apply these 'effects'
settings via vdagentd (system level)? For
Hi,
On 07/05/2013 03:08 PM, Marc-André Lureau wrote:
hi
On Fri, Jul 5, 2013 at 2:40 PM, Fedor Lyakhov wrote:
Hello everyone,
I continue working on this "bug62033 means to detect local only" issue, and
want to confirm whether I'm going in the right direction so the result can
be committed int
hi
On Fri, Jul 5, 2013 at 2:40 PM, Fedor Lyakhov wrote:
> Hello everyone,
>
> I continue working on this "bug62033 means to detect local only" issue, and
> want to confirm whether I'm going in the right direction so the result can
> be committed into Spice.
> My plan is:
> 1. Announce capability
Hello everyone,
I continue working on this "bug62033 means to detect local only" issue, and
want to confirm whether I'm going in the right direction so the result can
be committed into Spice.
My plan is:
1. Announce capability of DisplayConfig by vdagentd, then receive
VDAgentDisplayConfig message
Hi,
1. Yes, exactly, I meant to use this option.
2. And yes, that's my point - why vdagent should tweak settings for all
desktops (it is impossible to support all desktops) - but we need to
provide some means for desktop developers to take in account the DE is
viewed via Spice (local or remote cl
Hi
- Mensaje original -
> OK, so first implementation will work via --spice-disable-effects option. As
> far as I understand, this user-provided option flags should already be
> available at the agent, need to handle appropriate message as in Windows
> vdagent, correct?
There is already:
Hi,
OK, so first implementation will work via --spice-disable-effects option.
As far as I understand, this user-provided option flags should already be
available at the agent, need to handle appropriate message as in Windows
vdagent, correct?
Anyway, I still don't understand how we can control th
Hi,
On 06/24/2013 05:32 PM, Yonit Halperin wrote:
Hi,
For the purpose of disabling guest desktop effects, we already have a spice-gtk
option which we use for Windows guests, and can be used for Linux guests as
well. The Linux agent should support VD_AGENT_DISPLAY_CONFIG for this.
However, fo
Hi,
For the purpose of disabling guest desktop effects, we already have a
spice-gtk option which we use for Windows guests, and can be used for
Linux guests as well. The Linux agent should support
VD_AGENT_DISPLAY_CONFIG for this.
However, for local usage, we would also like to disable bitma
Hans,
Thanks for the comments and clarifications! OK, I'll start with more simple
solution of 'local/remote' detection first.
As for gsettings - I see your point, this will solve the issue for Gnome3
as requested. But I think this is too limited - e.g. what if KDE5 wants
this in future?
On Mon
Hi,
On 06/24/2013 02:44 PM, Fedor Lyakhov wrote:
Hi David,
Thanks for your answer. Please see my comments below.
On Mon, Jun 24, 2013 at 3:47 PM, David Jaša mailto:dj...@redhat.com>> wrote:
Hi Fedor,
I'd personally prefer to:
1) monitor bandwidth and latency continuously - ther
Hi David,
Thanks for your answer. Please see my comments below.
On Mon, Jun 24, 2013 at 3:47 PM, David Jaša wrote:
> Hi Fedor,
>
> I'd personally prefer to:
> 1) monitor bandwidth and latency continuously - there's a long-standing
> RFE for it and IIRC Yonit has posted some proof-of-concept pa
Hi Fedor,
I'd personally prefer to:
1) monitor bandwidth and latency continuously - there's a long-standing RFE for
it and IIRC Yonit has posted some proof-of-concept patches in recent months (as
a part of her streamlining of video streams)
2) set the options on-the fly as the conditions allow t
Hello Zeeshan, Marc-André and other Spice developers,
I think about implementing a solution for this bug 62033 (
https://bugs.freedesktop.org/show_bug.cgi?id=62033).
First of all, need to clarify what is requested and what is really needed
in this request. Zeeshan suggests as a simple yet accepta
20 matches
Mail list logo
