Google Summer of Code 2013 - GNOME - Archive Integration workspace https://lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/atom?h=master 2014-06-09T14:32:25+00:00 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-05T09:47:13+00:00 Milan Crha mcrha@redhat.com 2014-06-05T09:47:13+00:00 urn:sha1:2e71c861438a25ceac5811d9d3aa528691e71410 This is a follow-up for the previous commit, where e_signal_connect_notify*() functions had been added. Due to a different callback and user data being attached to the 'notify' signal, the g_signal_handlers_*() functions do not work properly, thus these e_signal_connect_notify*() functions need a different way for a signal handler disconnect. A side-change was done in e-settings-web-view-gtkhtml.c, checking for a real key change from GSettings. 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-03-25T11:04:58+00:00 Milan Crha mcrha@redhat.com 2014-03-25T11:04:58+00:00 urn:sha1:8692b1cb72654888f0dab31843bdf05d3ac2a888 When enabled, this will compile all libraries/binaries with the necessary gcc and ld flags to enable code coverage support using gcov. 2014-03-03T00:36:01+00:00 Matthew Barnes mbarnes@redhat.com 2014-02-16T14:36:49+00:00 urn:sha1:c53fbc0b8f3b98827d6816a627bdd4d467b84f74 2014-02-13T08:09:21+00:00 Milan Crha mcrha@redhat.com 2014-02-13T08:09:21+00:00 urn:sha1:55557b13d2111c5728078e4866da77140ace960b The "dialog-apply" icon is not from a set of standard icons, thus it cannot be used, which I overlooked yesterday. With its drop are also dropped other button icons in itip-formatter. The missing icon made EStockRequest "panic" which effectively broke page rendering for WebKit - the rendering was never finished. 2014-02-12T19:47:07+00:00 Milan Crha mcrha@redhat.com 2014-02-12T19:45:53+00:00 urn:sha1:b48e21d9aa7eb16e559739b71b9d08f90dfa92be 2014-01-07T21:05:51+00:00 Matthew Barnes mbarnes@redhat.com 2014-01-07T19:19:27+00:00 urn:sha1:b21733d06715597b189c4271a2e9d625f5fc2345 2013-11-15T08:06:57+00:00 Milan Crha mcrha@redhat.com 2013-11-15T08:06:57+00:00 urn:sha1:570c6374806d0f1ec59cf7a72543efe6b5b637be This makes the code free of Coverity scan issues. It is sometimes quite pedantic and expects/suggests some coding habits, thus certain changes may look weird, but for a good thing, I hope. The code is also tagged with Coverity scan suppressions, to keep the code as is and hide the warning too. Also note that Coverity treats g_return_if_fail(), g_assert() and similar macros as unreliable, and it's true these can be disabled during the compile time, thus it brings in other set of 'weird' changes. 2013-10-29T19:22:35+00:00 Bastien Nocera hadess@hadess.net 2013-10-29T18:04:54+00:00 urn:sha1:bc0d5d40ed39c92dcdf62ae891a2e99c25237d74