Google Summer of Code 2013 - GNOME - Archive Integration workspace https://www.lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/atom?h=master 2014-07-17T10:46:38+00:00 2014-07-17T10:46:38+00:00 Milan Crha mcrha@redhat.com 2014-07-17T10:46:38+00:00 urn:sha1:bcc3a1c7e641830622690116907c02b7f89183d7 Plus a little code cleanup for easier grepping. 2014-07-07T10:51:41+00:00 Milan Crha mcrha@redhat.com 2014-07-07T10:51:41+00:00 urn:sha1:50bda1bad222082488d3d9bc9fe1d0fb3867e974 This makes evolution depend on theme-defined named colors, namely: theme_bg_color theme_base_color theme_fg_color theme_text_color theme_selected_bg_color theme_selected_fg_color theme_unfocused_selected_bg_color theme_unfocused_selected_fg_color If it's not defined, then a fallback color is used, in the worse case one of the fallbacks defined in evolution itself. 2014-07-01T16:36:26+00:00 Milan Crha mcrha@redhat.com 2014-07-01T16:36:26+00:00 urn:sha1:2a2201ad44df50c1303eea1e460d47b50a304931 2014-06-25T13:59:50+00:00 Tomas Popela tpopela@redhat.com 2014-06-25T09:33:44+00:00 urn:sha1:93c1357da29c068d1418f8bd07b58b55d05f5c0b 2014-06-11T16:19:10+00:00 Milan Crha mcrha@redhat.com 2014-06-11T16:17:42+00:00 urn:sha1:60d5ff7b7127cbc382139de511fb445322696dca These were new after merging webkit-composer branch changes, but just some leftovers. 2014-06-09T14:32:25+00:00 Tomas Popela tpopela@redhat.com 2014-06-09T14:32:25+00:00 urn:sha1:8650fb139a9143f04615de74ff569bce3e0c4ce3 Merge wip/webkit-composer branch into master. 2014-06-06T10:02:13+00:00 Milan Crha mcrha@redhat.com 2014-06-06T10:02:13+00:00 urn:sha1:d6dcec1b5578cc6a67d3dea97e48b580149cf421 2014-06-06T06:59:53+00:00 Milan Crha mcrha@redhat.com 2014-06-06T06:59:53+00:00 urn:sha1:1205a86888d0d3af669c4c7f97b82ef6987b4beb 2014-06-04T17:46:25+00:00 Milan Crha mcrha@redhat.com 2014-06-04T17:46:25+00:00 urn:sha1:2f3fbdd6c6ff42a6c71ebe1d1d78108affe59d0f This is related to bug 698275, which did not cover all cases. The problem here is that the dconf can in certain situation claim that everything changed (path "/" changed), which GSettingsBinding propagates to a GObject property unconditionally and GObject's property setter (g_object_set_property()) also notifies about the property change unconditionally, despite the real descendant property setter properly checks for the value change. After all these false notifications a callback on "notify" signal is called and possibly an expensive operation is run. Checking whether the value really changed helps in performance, for which were added new e-util functions: e_signal_connect_notify() e_signal_connect_notify_after() e_signal_connect_notify_swapped() e_signal_connect_notify_object() which have the same prototype as their GLib counterparts, but they allow only "notify::..." signals and they test whether the value really changed before they call the registered callback. 2014-06-03T08:44:19+00:00 Milan Crha mcrha@redhat.com 2014-06-03T08:44:19+00:00 urn:sha1:70f58975e34348e4b698bb80e0078f93858bbc48