287ddda5df
workspacesView: Don't zoom into the overview based on a signal
...
Instead, simply have somebody else call us, like we do for hiding
the overview as well.
2013-10-30 13:17:39 -04:00
7747f1c31d
workspacesView: Don't use a drag monitor to get the clone
...
Just use the new variable passed to the signal.
2013-10-30 13:17:39 -04:00
8097cbbbe3
workspacesView: Don't do any special handling for item-dragging
...
The code here really only cares about new windows.
2013-10-30 13:17:39 -04:00
e4c07875a3
overview: Send the clone with the window-drag events
...
This allows clients that care about the actual item we're dragging to
make smarter decisions without adding a drag monitor themselves.
2013-10-30 13:17:38 -04:00
026fd4cf35
workspace: Punt the geometry-fizzling-out logic here
2013-10-30 13:17:38 -04:00
87016f9620
workspacesView: Remove spacing
...
It's not used in the theme and it complicates the layout code a bit
too much; in fact, if set, things start breaking.
2013-10-30 13:17:38 -04:00
88393f0f65
overviewControls: Move translation-x to SlideLayout
...
Not because ClutterActor is bad or wrong, but because I always get
confused on the difference, and having them both in SlideLayout
makes the code a bit easier to read and understand.
2013-10-30 13:16:45 -04:00
f5a9dbb348
overviewControls: Always allocate the actor its full size
...
This is the new Clutter way -- if the actor wants to adjust its
alignment, it will do it itself with its alignment flags.
2013-10-30 13:16:45 -04:00
dbf3bb112c
overviewControls: Make getSlide/updateSlide private
2013-10-30 13:16:45 -04:00
f3186bd501
overviewControls: Make visible and inDrag private
...
These don't need to be accessed from outside SlidingControl,
so don't let them be.
2013-10-30 13:16:44 -04:00
3f1a252b91
overviewControls: Move slideOut on overview hide to the parent as well
2013-10-30 13:16:44 -04:00
1240d6be76
overviewControls: Remove dead code
...
The parent SlidingControl had an onOverviewShowing, but we had
overridden it with the same code in both subclasses. Just move it
back to SlidingControl.
2013-10-30 13:16:44 -04:00
faf7b62f5c
overviewControls: Mark the DashSlider as x_expand
...
Actors need to expand in order for them to their x_aligns to be taken
into account.
2013-10-30 13:16:44 -04:00
445011b1e5
overviewControls: Add the parent's box into the allocation
...
Currently, this is always 0, but this will change when we introduce
a custom layout manager into the story.
2013-10-30 13:16:44 -04:00
e630fec63a
search: Fix adding items to icon grids
2013-10-30 13:06:56 -04:00
17421e8a63
iconGrid: Actually throw programmer errors
...
This way we get a backtrace.
2013-10-30 13:05:20 -04:00
af06b78605
searchDisplay: Cache result display actors
...
When we create a result actor, cache it, so it can be used for
subsearches of the same initial. For now, to keep memory usage
and the stage graph relatively clean, don't persist the actors
across searches, but maybe we should do this in the future.
This also means that we don't query getResultMetas for items
that we've seen in the same initial search.
https://bugzilla.gnome.org/show_bug.cgi?id=704912
2013-10-30 13:01:20 -04:00
3749b09366
searchDisplay: Make the search result actors stateless, by removing terms
...
We want to cache result actors between searches, so we shouldn't
instantiate them with search-specific info.
https://bugzilla.gnome.org/show_bug.cgi?id=704912
2013-10-30 13:01:20 -04:00
27cac10d0c
appDisplay: Use a proper string key for the app search provider
...
Since we're going to be caching results based on the result ID,
we need to return a string-based result ID to cache on.
https://bugzilla.gnome.org/show_bug.cgi?id=704912
2013-10-30 13:00:47 -04:00
0590962d36
viewSelector: Move all of the provider-loading logic to SearchSystem
...
The existing provider system is split between a confusing mess of
RemoteSearch, SearchSystem, SearchDisplay, and ViewSelector, partly
because of the vestigal in-shell search system. Move most of the
logic to search.js so it's easier to read.
2013-10-30 12:59:41 -04:00
c0c20d49a5
search: Always fetch the list of search providers
...
We fetch and store the list of providers from the search system when we
construct SearchResults, but we never update this list when providers are
changed at runtime, causing various bugs making the search not seem as
snappy as it should be. Make sure to always fetch the list of providers
from the search system.
2013-10-30 12:59:31 -04:00
633dd0d9de
notificationDaemon: Save notifications on source destruction
...
While the existing comment is correct in that a source's notifications
will be destroyed first, the code takes a shortcut which prevents the
Source::count-updated signal from being emitted. Given that the purpose
of the signal is to keep notification counters up-to-date which is
pointless when the source is about to be destroyed, the shortcut makes
sense; just save notifications explicitly in that case.
https://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-30 16:40:33 +01:00
b929320d4c
lookingGlass: Remove Memory tab and add a gc Icon to toolbar
...
With js24 it won't be possible to access gjs memory stats from C code.
https://bugzilla.gnome.org/show_bug.cgi?id=711052
2013-10-30 07:44:34 +11:00
dd44219aa5
Merge searchDisplay.js and search.js
...
search.js used to do a lot more, but now that most of the
functionality has been moved to the remote search system,
it doesn't do a lot. Merge searchDisplay.js into it.
2013-10-29 16:02:32 -04:00
8cc1fe007d
search: Actually crash when seeing errors from a native search provider
...
We don't implement many of these, and not catching the error lets us
see stack traces and other such information a lot faster.
https://bugzilla.gnome.org/show_bug.cgi?id=704912
2013-10-29 16:02:32 -04:00
c0b45c9fc4
Remove wanda
...
It's been broken for quite a bit since we removed Panel.Animation,
and hasn't really ever worked with our new search results. It's also
the only non-remote provider left.
Maybe we'll add it back as a remote provider later, but for now, just
ditch it.
2013-10-29 15:46:49 -04:00
41315f45a9
notificationDaemon: Fix custom icons
...
The 'icon' property contains a serialized GIcon, so we need to
deserialize it when setting the icon.
https://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-28 12:28:37 +01:00
04d28a0eea
notificationDaemon: Fix urgency hint
...
We currently mark notifications as urgent which merely contain the
'urgent' property, even when set to false. Look at the actual value
instead.
https://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-28 12:28:37 +01:00
34e75fc595
notificationDaemon: Fix button parameter name
...
Gio ended up using 'target' rather than 'action-target'.
https://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-27 11:38:36 +01:00
dac513e046
notificationDaemon: Unpack button label
...
deep_unpack() doesn't unpack as deeply as one might hope ...
https://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-27 11:38:36 +01:00
2c538d247b
catch more errors on extensions enable() and disable()
...
https://bugzilla.gnome.org/show_bug.cgi?id=688331
2013-10-26 16:35:47 +02:00
f3b7f61e54
AltTabSwitcherPopup: check the number of items after creating the popup child
...
The popup can be empty if the alt-tab switcher is configured
in workspace-only mode, even if there are applications running.
https://bugzilla.gnome.org/show_bug.cgi?id=710745
2013-10-26 16:29:27 +02:00
d47ecf19f5
need space between item in endsession dialog session-list and app-list
...
https://bugzilla.gnome.org/show_bug.cgi?id=710543
2013-10-26 16:24:41 +02:00
da19b344b5
RemoteSearch: don't autostart dbus search providers at login
...
Use the new glib flag that allows us to create the proxy immediately
but only activate the service when making the first call.
https://bugzilla.gnome.org/show_bug.cgi?id=708830
2013-10-26 15:20:52 +02:00
eb66407926
NotificationDaemon: fix more fallout
...
Missing Gtk import for action-icon buttons.
https://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-26 14:56:50 +02:00
61c5b8e7d2
notificationDaemon: Pass the correct id to makeButton()
...
The function expects the action's ID, not the notification's one.
https://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-25 14:15:10 +01:00
4b09d57ec2
Fix fallout from notification changes
...
Commit 5f081b8f8dhttps://bugzilla.gnome.org/show_bug.cgi?id=710596
2013-10-25 14:15:10 +01:00
b908a3d70a
Stringify the xml definitions for E4X removal
...
https://bugzilla.gnome.org/show_bug.cgi?id=691409
2013-10-25 08:57:27 +11:00
d519c7263e
Background: Drop "saturation" related source
...
"saturation" was removed from MetaBackground in mutter with
https://git.gnome.org/browse/mutter/commit/?id=0e589061
2013-10-23 21:37:27 +02:00
3ca1784ff4
notificationDaemon: Fix activating with a target
...
Targets should not be unpacked, and action IDs should.
2013-10-21 16:50:18 -04:00
b54d512f3f
notificationDaemon: Fix loading/saving of notifications
2013-10-21 16:14:14 -04:00
9d8fb19f55
notificationDaemon: Write notifications out to disk
...
This allows notifications to persist even after reboots and
gnome-shell restarts.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 14:13:21 -04:00
e0b87f1e14
notificationDaemon: Implement the new GTK+ notifications API
...
The new API is designed to support features like persistence and uses
the new org.freedesktop.Application specification for activating
actions on notifications. While we won't add support for persistence
yet, implement the new notification spec with parity of the old one.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 14:12:47 -04:00
394743efc8
notificationDaemon: Rename the existing implementation to the FdoNotificationSource
...
We'll add a new, simpler private implementation that's used by the new
GNotification API in gio.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 12:30:25 -04:00
27a86a4756
notificationDaemon: Move nextNotificationId inside the daemon class
...
This won't be used by the new notification daemon.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 12:30:25 -04:00
8ee0ef2cde
messageTray: Don't always open the source when clicking on the notification
...
Some consumers may not always want to open the app, so make clients that
want to do this explicitly connect to the 'clicked' signal.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 12:30:25 -04:00
43f4682ec4
messageTray: Make addButton/addAction take a callback
...
This is a much simpler API for consumers to manage.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 12:30:25 -04:00
5f081b8f8d
messageTray: Remove useActionIcons feature
...
This can be put in the legacy notification daemon with the new
addButtonFull API, to create icon names for actions.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 12:30:25 -04:00
5023542882
messageTray: Split out addButton to allow consumers to pass a pre-made button
...
Some consumers may want to construct their buttons specially, so allow them
to do that by adding a new API that takes a button instead of a label.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 12:30:25 -04:00
88d0731d80
messageTray: Replace setButtonSensitive by simply returning the button
...
We want to remove 'id's from buttons, and simply returning the button actor
is more powerful anyway.
https://bugzilla.gnome.org/show_bug.cgi?id=710137
2013-10-21 12:30:25 -04:00
