gnome-shell:wip/fullscreen

Last commit made on 2015-10-12
Get this branch:
git clone -b wip/fullscreen https://git.launchpad.net/gnome-shell

Branch merges

Branch information

Name:
wip/fullscreen
Repository:
lp:gnome-shell

Recent commits

672ca88... by Cosimo Cecchi

windowManager: add animations for fullscreen and unfullscreen

We use the newly introduced feature from Mutter to hook up our own
fullscreen and unfullscreen animations.
To give the illusion of a transition as smooth as possible, we create a
snapshot of the current contents of the actor before its state is
changed, and crossfade between the two states while the size changes.

https://bugzilla.gnome.org/show_bug.cgi?id=707248

674ae26... by Cosimo Cecchi

Change incorrect parameter names

These were renamed a while ago.

db297e7... by Owen Taylor

Don't crash on accesses to stale window-backed apps

The JS code could still be holding on to a reference to a window-backed app
after all windows have vanished. (For example, the dash queues an idle to
refetch apps and display them.) Avoid dying with an error message if we
attempt to activate or otherwise manipulate such a window.

https://bugzilla.gnome.org/show_bug.cgi?id=674799

d57c146... by Ask Hjorth Larsen

Updated Danish translation by scootergrisen

ec5a432... by Ask Hjorth Larsen

Updated Danish translation

e4ee72c... by Khaled Hosny

Update Arabic translation

31f1e9f... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

autorunManager: Do not mark the notification CRITICAL

There is nothing particularly critical about this notification, it
was only marked as such to get certain behavior like auto-expanding
and sticking-around to be acknowledged by the user (as it offers
more actions than the summary notification, so it is frustrating
when it goes away because it was missed).
As all notifications will now stay visible until we are sure the
users has seen them, the latter reasoning no longer applies.
Auto-expansion doesn't appear too important and may even be considered
annoying by users, so remove the CRITICAL hint now.

https://bugzilla.gnome.org/show_bug.cgi?id=657923

d6c049a... by Rui Matos

altTab: Don't error out if we don't have windows for an app

We are currently erroring out when the tab chain doesn't contain at
least one window for an app which might happen for windows that don't
take focus like xeyes. This leaves us in a state where we can't show
the switcher at all. Let's just ignore these apps instead of looking
broken.

44047ac... by Rui Matos

shell-glsl-quad: Set the pipeline blend string explicitly

The default pipeline color is opaque white and blending is turned
off. If we only draw with that color (e.g. because animations are
disabled and we're always drawn with opacity == 255), blending is kept
disabled since cogl_pipeline_set_color() returns early if the color
doesn't change from what was there before.

In our case we always want blending to be enabled which we can achieve
by setting the blending string ourselves.

https://bugzilla.gnome.org/show_bug.cgi?id=755827

464d5d8... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

st-button: Don't rely on hover to accept clicks

Since commit 4f1f226828 we only consider buttons clicked when the
release event had a corresponding press event. However as we use
the hover state to check whether a release event actually occurred
on the button, we dismiss any clicks in cases where we missed the
enter event - most likely due to some other actor holding a grab.
Instead, check whether the button contains the event's source, which
should be less error-prone.

https://bugzilla.gnome.org/show_bug.cgi?id=748919