| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Metacity reads the default theme from gsettings and we were trying
to override it at lower level, causing race conditions. Now we are
just setting the cursor-theme gsetting, so that metacity setup the
Sugar theme for us.
Distributions which are shipping both GNOME and Sugar should make
sure to set XDG_CONFIG_HOME for either of the desktops to point
to a non default location, so that the settings are not conflicting.
It's necessary in this case if you don't want to get the Sugar
cursors in GNOME, but it seems like a sane approach in general. We
are sharing several components with GNOME which are (or might in
the future) use GNOME gsettings.
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
|
|
|
| |
So that the sugar script only setup environment variables
and all the rest is in main.py. This avoids the confusion about
putting stuff in the one or the other script. Ideally we would
get rid of the bash script completely, but it would not be
possible to source the debug and i18n files from python.
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
|
|
| |
They seems to have been added for sugar-emulator, which is not
using them anymore. It seems unlikely anyone will run the
sugar script directly from the command line, and anyway it's
just about setting environment variables.
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
| |
On fedora 17, where wpa_passphrase is installed in /usr/sbin, the
directory is now also on the path.
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
|
|
| |
It's quite unexpected to find a large amount of code outside the
package. Also it's not really much of a "session", it starts a
couple of other processes maybe, but it mostly setups stuff and
initialize the UI.
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
|
|
|
|
| |
These are necessary for unit tests because we cannot assume
they are installed in the system. Also config.py is not
generated inside the jarabe package directory when building
out-of-source, so trying to import it fails
They might be used for customization too.
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
| |
Signed-off-by: Daniel Narvaez <dwnarvaez@gmail.com>
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
|
|
|
| |
Creating multiple non-nested mainloops in gtk 3.6 breaks
at least accessibility.
See https://bugzilla.gnome.org/show_bug.cgi?id=685453
Signed-off-by: Daniel Narvaez <dwnarvaez@gmail.com>
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
|
|
|
|
| |
It avoids the unexpected side effect (showing the intro UI
implicityly when we are just checking the profile existence).
It also prepares for listening to an IntroWindow done signal
instead of blocking in a mainloop.
Signed-off-by: Daniel Narvaez <dwnarvaez@gmail.com>
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
| |
We just have to move it earlier in the startup phase.
Signed-off-by: Simon Schampijer <simon@laptop.org>
Acked-by: Manuel Quiñones <manuq@laptop.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sugar extensions that use threads such as OLPC's software updater
require that threads have been properly initialised before the
main loop is ran.
For pygobject3, GLib.threads_init() must be called before doing
the same for Gdk, otherwise the threads hang in random places
for long periods of time. See e.g.
http://stackoverflow.com/questions/11070263/webkit-threads-with-pygobject-on-gtk3
Signed-off-by: Daniel Drake <dsd@laptop.org>
Acked-by: Simon Schampijer <simon@laptop.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
We only display the cursor in mouse/trackpad mode, hence when
a mouse motion is detected or a button press event. When a
touch begin event is received the cursor will be hidden.
We only track the incoming events when a touchscreen device
is available.
Signed-off-by: Simon Schampijer <simon@laptop.org>
Acked-by: Manuel Quiñones <manuq@laptop.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As spoted by Daniel Narvaez in [1], pygi does not set the default encoding
anymore as the old GTK+ did. This change does break activities ported
to GTK+3.
The change in GTK+ has been discussed upstream here [2].
A better solution will be implemented when we port to Python 3,
when we will be able to use real unicode strings.
The toolkit-gtk3 has already been fixed in
5fdad9481ba7079a6a718159ebe7eb8e5367c46e.
Signed-off-by: Simon Schampijer <simon@laptop.org>
Reviewed-by: Gonzalo Odiard <gonzalo@laptop.org>
[1] http://lists.sugarlabs.org/archive/sugar-devel/2012-August/038993.html
[2] https://bugzilla.gnome.org/show_bug.cgi?id=681915
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We use SugarExt.GestureGrabber to listen for gestures
on the root window. Swiping from the frame area
towards the center does reveal the Frame.
Swiping towards one of the edges does hide the Frame.
This patch does depend on fe0022cd8f6a8fb94d379be287761cc3a6206086
in the toolkit-gtk3.
Signed-off-by: Simon Schampijer <simon@laptop.org>
Acked-by: Manuel Quiñones <manuq@laptop.org>
|
|
|
|
|
| |
Signed-off-by: Daniel Narvaez <dwnarvaez@gmail.com>
Acked-by: Manuel Quiñones <manuq@laptop.org>
|
|
|
|
|
|
|
|
| |
- use intrspected API for getting the default display
- adopt to new API
Signed-off-by: Manuel Quiñones <manuq@laptop.org>
Acked-by: Simon Schampijer <simon@laptop.org>
|