GitLab

Now, on first start, we will populate GSettings with a layout.

This is the first step for the migration to GSettings for
toplevels/objects.

Some applets might want to hide widgets by default.

This fixes the visibility on startup of lock/logout/shutdown in the
menubar when they are locked down.

This was a small regression introduced with the lockdown change.

We can remove our PanelDBusService helper class now.

We were using gnome-screensaver-command before, but there's no reason to
stay this way.

This means we lose support for xscreensaver; it could be added back,
if some people want it, but this doesn't make a lot of sense since
xscreensaver doesn't completely integrate in GNOME (in the system
settings, for example).

Also, open the system settings on the screen panel for screensaver
properties.

Lock is the default action, so it should be first.

This also means we can get rid of panel-config-global.[ch] since it's
now doing nothing.

I don't think people want to change this as a setting. However, for
themes, it might make sense.

It can be changed with "-ButtonWidget-hover-highlight: false;" set for
ButtonWidget. By default, it's set to true, and ButtonWidgets are
highlighted on hover.

This will be much easier if we have all the defines in one file.

Instead, we simply use the gtk-enable-animations property of
GtkSettings.

Instead, we simply use the gtk-enable-animations property of
GtkSettings.

Also correctly handle change of "enable-program-list" key.

Note: history of the run dialog is still saved in gconf.

This is just the schemas, and no code has been ported. The schemas will
need to be reviewed later on too.

The default panel layout will be defined in a simple keyfile, that the
panel will duplicate inside gsettings if there is no toplevel
configured.

We'll add gsettings schemas there too.

Colin Walters authored Mar 23, 2011 and Vincent Untz committed Mar 29, 2011

A -1 error code will just turn into 255, which is lame.  Fix
it to be just 1 like everything else; we have no error code
standardization or anything.

It's better to put a non-destructive action first.

This was mostly useful because it was too easy to move applets, but with
the new way to edit panels, it's not needed anymore.

Also do the same for internal object (eg: menubar) when clicking with
middle button.

Same rationale as previous commits.

Same rationale as previous commit.

Users migrating from such an old version shouldn't expect the
upgrade to keep their configuration for 3.0, really.

It's finally time to drop drawers:
 - there are always been various issues here and there, and they've
   never got fixed
 - it added complexity to the code
 - number of users using it is small
 - 3.0 is a good time to do this change

This just does not work with GTK+ 3, and was considered bad design for a
long time since it's the only menu in the desktop where a popup menu
exists.

Users can achieve most of it with alacarte / the addto dialog.

The font is now made bold in the theme, which is the right way to handle
this.

This isn't used by gnome-session.