libnm's NMSecretAgentOld is a GInitable and requires explicit
initialization.

Fixes: 3722a190

Fixes: 4d7546e7

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

We only care about TERM/INT, and those are already handled OK by
the event loop.  We don't need custom handling for them.

Dan Winship authored Nov 25, 2014 and Dan Williams committed Feb 25, 2015

Based on a patch by Jiří Klimeš.

Dan Winship authored Nov 25, 2014 and Dan Williams committed Feb 25, 2015

Based on a patch by Jiří Klimeš.

It might get used where NMA_* won't be.

Dan Winship authored Nov 25, 2014 and Dan Williams committed Feb 25, 2015

Add a new libnm-based version of libnm-gtk, called "libnma" (which
matches the naming convention of the functions better anyway). Also,
rename the files from nm-* to nma-*.

Drop nm-wireless-dialog (which was deprecated in favor of
nma-wifi-dialog) and nm-ui-utils.h (whose functionality has been
merged into NMDevice in libnm).

(libnm-glib to libnm porting mostly based on a patch by Jiří Klimeš.)

Dan Winship authored Nov 25, 2014 and Dan Williams committed Feb 24, 2015

Also, drop the "ssid" parameter from wireless_security_validate(),
since it would need to be different between the two versions, but it
turns out it's not actually used anyway.

Dan Winship authored Nov 25, 2014 and Dan Williams committed Feb 24, 2015

Remove "PKG_CHECK_MODULES(GOBJECT, gobject-2.0)", which wasn't being
used, and which was already implied by other checks.

Remove a bunch of unecessary AC_SUBST() calls in configure.ac.
(PKG_CHECK_MODULES automatically substs the variables it sets.)

Remove GNOME_MAINTAINER_MODE_DEFINES, which just sets a bunch of
irrelevant flags like BONOBO_DISABLE_DEPRECATED.

Dan Winship authored Nov 24, 2014 and Dan Williams committed Feb 24, 2015

The current version of gnome-bluetooth does not support plugins, so
there's no reason to keep this around any more.

Dan Winship authored Nov 24, 2014 and Dan Williams committed Feb 24, 2015

Anyone upgrading directly from 0.8 to 1.2 will just lose their old
non-system connections. (Which they probably would have anyway, since
the migration tool only gets run if nm-applet does...)

Dan Winship authored Nov 24, 2014 and Dan Williams committed Feb 24, 2015

Delete the custom-marshaller code and use g_cclosure_marshal_generic()
everywhere.

'pixbuf' isn't used for indicator+icon-name, but is used for
indicator+icon-data and non-indicator cases.

It seems that many implementations don't support pixmaps at all,
instead using only the icon-name.  Unfortunately that means that
these implementations' users loose some valuable information like
encryption status of the AP, but it's better than showing no
icon at all.

There are two solutions to this problem:

1) extend dbusmenu to allow multiple icons, which we would use to
show both the signal bars and a lock icon, much like Mac OS X and
iOS.  This is preferable.

2) add all possible icon combinations (5 signal bars * 2 encryption
states).  This is less easy for theme authors to work with and
means shipping more icons.  Not preferred.  Work on dbusmenu instead.

Remove the separate adhoc icon in the menu, and just replace the signal
bars with the adhoc icon for these networks.  Consolidate some code
paths between normal and indicator modes.

For the moment only pixmaps are passed for WiFi/WWAN menu items
are passed instead of the icon name.  Not all implementations
of appindicator/dbusmenu support pixmap data (Enlightenment is
one that does not) but we'll work on that.

Pavel Šimerda authored Dec 17, 2014 and Dan Williams committed Feb 17, 2015

Add new configure option --with-appindicator which implies a optional
dependency on libappindicator. This is the way systray is done in the
current versions of Unity, KDE and Enlightenment and others. Some of the
systray implementations already dropped support for Xembed, others are
going to, mostly to gain independence on X11 as part of being ported to
Wayland.

Keep the previous functionality intact.

(many cleanups and consolidations by dcbw)

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

Pavel Šimerda authored Feb 17, 2015 and Dan Williams committed Feb 17, 2015

Without this patch the VPN items won't display correctly in appindicator
mode.

Pavel Šimerda authored Feb 17, 2015 and Dan Williams committed Feb 17, 2015

Without this patch, the VPN items would sometimes not show at all
in appindicator mode.

Collapse some of the setters into nm_network_menu_item_new() since
these properties actually never change.  Add some ATK descriptions
too.

Pavel Šimerda authored Jan 15, 2015 and Dan Williams committed Feb 17, 2015

This is especially useful when debugging with G_DEBUG=fatal-warnings
in cases when you don't expect the agent to register successfully,
e.g. due to an already registered nm-applet.

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

Add --keep-above, to tell nm-c-e to mark all of its windows "keep
above". (For use by anaconda, to keep them from getting lost under its
fullscreen window.)

Pavel Šimerda authored Dec 17, 2014 and Dan Williams committed Feb 16, 2015

Add an empty applet_schedule_update_menu() that would later be used
by the appindicator code. Prepare the code for the final appindicator
patch.

Pavel Šimerda authored Feb 08, 2015 and Dan Williams committed Feb 16, 2015

Whenever possible, return icon name from applet_update_icon() and only
load it in foo_set_icon().

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

NetworkManager 1.0 and later don't support the old ModemManager, and
the applet doesn't support old versions of NetworkManager, so remove
the obsolete support and bump the version requirements to NM 1.0+.

Pavel Šimerda authored Jan 15, 2015 and Dan Williams committed Feb 16, 2015

Finalization is reordered in a way that allows seamless implementation
of appindicator mode. Initialization now only includes objects that
actually need some.

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

Pavel Šimerda authored Jan 15, 2015 and Dan Williams committed Feb 16, 2015

With appindicator patches, when built with --enable-indicator,
setup_widgets has to build the whole menu and thus requires access to
NetworkManager data. The patch doesn't cause any harm in non-indicator
mode.

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