A more visually simple look for the roomList
as designed by Lapo Calamandrei.

Instead of displaying notifications when connecting to
a server, use less attention grabbing status indicators in
the roomlist for displaying status of the servers
individually.

If a room is created as the result of user action, it feels more
responsive if we switch to it immediately rather than waiting
for the actual channel request to come in.

If we receive a disconnect error and the network is
unavailable, then the error is not specific to Polari.

It's obvious that a connection attempt will fail if we don't have
network, so don't bother trying ...

Account names are user configurable strings, and thus can be of
arbitrary length. While this shouldn't be a common issue, we still
shouldn't grow the UI indefinitely, so ellipsize the names.

When the user joins a room it makes sense to
also join it next time polari is started, even
if the room was never successfully connected to.

When a error requires the user to edit the details of the
connection, guide the user to the errornous entry using a
higlight and display a detailed description of the network error
in the bottom.

We currently update the indication for unread or highlighted messages
as the number of pending messages changes. However this obviously
does not work while offline, while at the same time keeping the
highlight around is obviously unobvious to users. The best thing
we can do while offline is clearing out the indication when a room
is selected, so do that.

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

Regular popup context menus can be brought up with the MENU key
or Shift-F10, so it makes sense to allow the same for the context
popover.

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

Update NEWS.

It's dead[0] Jim, it's dead ...

[0] https://mail.gnome.org/archives/desktop-devel-list/2015-May/msg00040.html

The plain line currently used to indicate the start of unread messages
in the chat log is not immediately obvious. Update its visuals to clarify
the purpose by including a "New Messages" label.

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

GtkContainer's default focus chain is based on its children's allocated
y position and height[0]. This is problematic when the user list has just
been created and doesn't have a proper allocation yet, as it will wrongly
sort before the search entry in that case.
Work around this by adding the user list to a dedicated bin (that is kept
around on room changes) instead of directly to the main box.

[0] https://git.gnome.org/browse/gtk+/tree/gtk/gtkcontainer.c#n2737

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

We currently set a width-request in the .ui file that used to be
consistent with the width of icon buttons, but the (default) theme
changed at one point, so this is no longer the case.
Fix this by setting the width-request to the actually allocated width
of an actual icon button (the join-menu).

Commit c96929c7 introduced different styling for active and inactive
nicks. However simply desaturating the theme's link color will not
result in a different color if the original color was already a shade
of gray (for instance when using the High Contrast theme).
To address this, dim the inactive-nick color via its alpha channel in
that case.

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

Cairo contexts don't play well with SpiderMonkey's GC, and thus need to
be disposed explicitly. However we are currently not doing that when
returning early from ::draw, piling up resources in turn.

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

Nothing connects to the ::draw signal, so this doesn't make any
difference in practice and is purely for correctness.

It is not necessary to mark Polari as busy since in-app indication
take care of indicating the status for each individual
connection already.

Since commit 1c6b4091 the chat log's border is always 0, and the
text offset is achieved using appropriate margins.

Check whether the line is actually visible (or covered/scrolled away)
before drawing it.

When a telepathy client appears on the bus, mission-control will only use the
interface information exposed on the bus for the proxy object if it cannot
locate a .client file matching the client's bus name[0]. As we do not set
TpBaseClient:uniquify-name, our bus name does match the .client file added
in commit 21df75d2 and the interface information from the file will be used
instead.
However our .client file currently only announces the Handler interface, so
mission-control doesn't consider us an observer anymore - add appropriate
information for the Observer interface to fix that regression.

[0] http://cgit.freedesktop.org/telepathy/telepathy-mission-control/tree/src/mcd-client.c#n899

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

Since commit 0b27b134 removed the first handler filter, we no longer
start counting from 0 as the hacker gods demand - rectify this.

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

As part of the effort to improve the initial setup experience
in Polari, a message is now shown telling the user how to
add a new connection as a convenience. The message is only
visible should when no connections have been added.

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

Currently there is a lot of empty grey space when Polari's
main window is started with no rooms in it. The patch adds a
recognizeable Polari logo to the background and a helping text
for adding connections, enabling accounts or joining a chatroom.

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

Update NEWS.

Commit fe51ac273c8 changed the fallback behavior when the looked up
state mismatches the actual state; as a result, the lookup may now
trigger the GtkStyleContext::changed signal - and as we happen to do
the lookup from a ::changed handler, we set off infinite recursion
with the expected fatal consequences.
Prevent this by guarding the lookup with a save()/restore() pair.

Commit c96929c7 uses an API which is only available in group
chat rooms, resulting in errors in private message rooms.
We currently don't have a way to check the actual online
status of a PM message, so always mark it as available.

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