enhance-favori…
Name already in use
Commits on Jun 18, 2015
-
enchaned favorites: use hidden list on runtime installs
Add a new attribute called "_hidden_activities" to BundleRegistry, so it can be used in other scenarios, such as when bundles are installed in runtime to determine whether or not bundle should be favorite looking at this list. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
enhances favorites: use activities.hidden
Add "activities.hidden" file with the bundle ids of Log and Terminal activities, as suggested in [1]. Deployments can later customize it via patching the sugar package or via OOB. Parse "activities.hidden" file and use the bundle ids to determine whether or not thw newly scanned activities should be favorites. [1] http://bugs.sugarlabs.org/ticket/4841
-
enhanced favorites: remove activities.defaults
Remove the "activities.defaults" file because is no longer used with the new approach. Remove "self._last_defaults_mtime" from BundleRegistry because is also no longer used either. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
enhanced favorites: extend favorite_activities file JSON format
Previously, the shell determined if an activity was a favorite by looking into the "favorite_activities" JSON file or by checking the "activities.defaults" file. The "activities.defaults" probed to be confusing and perceptively incosistent [1]. During the discussions it was suggested that we could provide a list of activities that should NOT be favorites as defaults. This patch series remove the use of the "activities.defaults" file and intead introduces the use of a new "activities.hidden" file. With this new approach, all activities are be considered favorites unless their bundle ids are listed in the "activities.hidden" file. This first patch extends the JSON format of the "favorite_activities" file to track activities that have been un-favorite by the users so we can later override the values of the "activities.hidden" file. This is because user preferences should take precendence over default values. [1] http://bugs.sugarlabs.org/ticket/4841 Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
Commits on Jun 17, 2015
-
Fix favorite selection in multiple home views
Use different Gtk.TreeViewColumn for each favorite column, otherwise only the fist one can be clicked and prevents populating the other home views. Slightly cleanup that code. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
Commits on Jun 12, 2015
-
Merge pull request sugarlabs#528 from quozl/2015-06-cp-power
Hide power control panel if powerd missing
-
The extreme power saving mode was removed a long time ago, but the search terms were not updated.
-
Hide power control panel if powerd missing
On commodity hardware the power control panel does nothing useful. Now, if powerd is not present, the CLASS global is not set, causing the panel to be omitted from the control panel. The message about missing CLASS is demoted from error to debug.
Commits on Jun 3, 2015
-
Restore brightness level earlier in startup
Load the brightness module earlier in the shell startup process in order to restore the brightness level before any other screen shows up, ie., the intro screen. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
Commits on Jun 1, 2015
Commits on May 30, 2015
-
Fix brightness monitor flags and file
Watch the specific brightness file instead of watching the whole device directory and drop the use of WATCH_HARD_LINKS because is not necessary. This patch fixes the brightness monitor in Fedora 18. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
Commits on May 29, 2015
-
Merge branch 'overlay-scroll-try3' of https://github.com/samdroid-app…
…s/sugar into samdroid-apps-overlay-scroll-try3
Commits on May 28, 2015
-
Disable overlay scrolling, fixes #4854
This commit disables overlay scrolling in Sugar. Although this should be set in the sugar theme, that is not possible. Setting the environment variable disables the overlay scrolling for both Sugar Shell and all sub processes (eg. activities). By setting an environment variable, this is ignored by Gtk versions less than 3.16. Ticket URL: http://bugs.sugarlabs.org/ticket/4854
Commits on May 24, 2015
-
For consistency with other modal dialogs such as view source and control panel, add a handler to translate escape key into stop button.
Commits on May 20, 2015
-
Merge branch '2015-05-cp-ofw' of https://github.com/quozl/sugar into …
…quozl-2015-05-cp-ofw
-
Fix trailing whitespace on firmware version
On most XO laptops the firmware version doesn't have the engineer's build number appended, and this results in "Q7C05 with 0.5.01" shown. Strip the trailing whitespace before using the version number.
Commits on May 18, 2015
Commits on May 17, 2015
-
Don't change star color on hovering - Fixes #3147
Change the star color on hovering cnfuses to the user, because think the favorite state has changed. This can be seen in the activities list view, in the Journal listview, and in the Journal detail view.
Commits on May 14, 2015
-
Remove signals from activity icon
Now the palette is created by the treeview, we don't need signals in the icon.
-
Adapt to changes in the ScrollingDetector
These changes were introduced with the TreeViewInvoker
-
Connect the signals in the palette
The signals datail-clicked and volume-error, now are triggered in the TreeView class, and need be connected.
-
Use the TreeViewIvoker, need move the creation fo the palettes, from the CellRendererIcons to the TreeViews. This simplify the code, and allow create the palettes only in the moment that is needed. In particular, in the Journal, the palette creation is expensive, and previously was created in the moment the mouse was over the icon, not matter if the palette was used or not. This was the origin of bugs like [1] [1] http://bugs.sugarlabs.org/ticket/4343
-
While the treeviews are scrolling, stop slow operations.
Using the ScrollingDetector, we can avoid expensive drawing operation unneded while scroll in the CellRendererIcons. This patch attach the scrolling detector to the treeviews in the Journal and in the Activities List. Signed-off-by: Manuel Quiñones <manuel.por.aca@gmail.com> Signed-off-by: Gonzalo Odiard <godiard@sugarlabs.org>
-
Merge branch 'brightness-controls-try9' of https://github.com/tchx84/…
…sugar into tchx84-brightness-controls-try9
-
brightness controls: update POTFILES
Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: do not update frame icon if no device
Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: exclude manager widget if no device
Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: update progress bar for external changes
Connect to Brightness.changed_signal to update the progress bar if the brightness values changes externally, ie., because of changes made by power manager or captured control keys. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: delay updates if progress changes
Add a delay to the changes triggered by the progress bar in the display frame palette. This is necessary because calling to external tool is slow and because we do not need to update the screen brightness for every bit of increment, while the bar is still being changed. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: add frame device icon
Add a new device icon to the frame to provive UI options to modify brightness and take screenshots. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: move screenshot code to its own model
Add a new model to provide a general interface for making screenshots and refactor globalkey code to use this model. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: add keyboard controls
Add a new globalkey file to implement brightness controls with the keyboard. This is necessary for detecting XF86MonBrightnessUp and XF86MonBrightnessDown events in standard laptops. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: monitor device for external changes
Use a GFileMonitor to track external changes done to the backlight device. This is required for detecting changes made to the device from external power managers and to workaround missing keyboard events in the XO. Ignore "external" changes triggered internally. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: save and restore user preferences
Add a new gsettings scheme key for saving and restoring brightness values between sugar shell sessions. Store values that are set by the user and do not store changes while is still changing, in order to avoid unnecessary calls to gsettings. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>
-
brightness controls: add brightness model
Add a new model which acts as a general backend for modifying and tracking the brightness of the screen. This model uses sugar-backlight-helper to interact with the backlight device. Signed-off-by: Martin Abente Lahaye <tch@sugarlabs.org>