aboutsummaryrefslogtreecommitdiffstats
path: root/e-util/e-activity.c
Commit message (Collapse)AuthorAgeFilesLines
* Add e_activity_cancel().Matthew Barnes2013-04-251-0/+27
| | | | Convenience function cancels the activity's GCancellable.
* Document EActivity.Matthew Barnes2013-04-251-3/+183
|
* Consolidate base utility libraries into libeutil.Matthew Barnes2012-12-131-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Evolution consists of entirely too many small utility libraries, which increases linking and loading time, places a burden on higher layers of the application (e.g. modules) which has to remember to link to all the small in-tree utility libraries, and makes it difficult to generate API documentation for these utility libraries in one Gtk-Doc module. Merge the following utility libraries under the umbrella of libeutil, and enforce a single-include policy on libeutil so we can reorganize the files as desired without disrupting its pseudo-public API. libemail-utils/libemail-utils.la libevolution-utils/libevolution-utils.la filter/libfilter.la widgets/e-timezone-dialog/libetimezonedialog.la widgets/menus/libmenus.la widgets/misc/libemiscwidgets.la widgets/table/libetable.la widgets/text/libetext.la This also merges libedataserverui from the Evolution-Data-Server module, since Evolution is its only consumer nowadays, and I'd like to make some improvements to those APIs without concern for backward-compatibility. And finally, start a Gtk-Doc module for libeutil. It's going to be a project just getting all the symbols _listed_ much less _documented_. But the skeletal structure is in place and I'm off to a good start.
* Do not call g_object_notify() when property didn't changeMilan Crha2012-06-181-0/+18
|
* EActivity cleanups.Matthew Barnes2012-01-251-5/+7
|
* Bug 668595 - Suppress bogus percentage in status messagesMatthew Barnes2012-01-251-0/+19
|
* Bug #646109 - Fix use of include <config.h> to make sure translations workMilan Crha2011-05-271-0/+4
|
* Add e_activity_handle_cancellation().Matthew Barnes2011-05-121-0/+15
| | | | | | | | Convenience function for use in GAsyncReadyCallback functions. This acknowledges the cancellation, so that the activity's description changes from "(cancelling)" to "(cancelled)" and the description appears crossed out in the UI for a moment before disappearing.
* Coding style and whitespace cleanup.Matthew Barnes2011-03-061-1/+2
|
* Bug #614480 - Avoid using G_TYPE_INSTANCE_GET_PRIVATE repeatedlyMilan Crha2011-02-251-7/+3
|
* Fix few memory leaksMilan Crha2011-02-151-4/+5
|
* EActivity: Add an "alert-sink" property.Matthew Barnes2010-11-011-18/+57
| | | | | | | This is just for convenience, EActivity does not use this property. Especially useful in async function callbacks when the operation failed and now you have to do something useful with the GError.
* Simplify EActivity.Matthew Barnes2010-10-231-217/+60
| | | | | | | | | | | | | | | | | | | | | | With unintrusive error dialogs gone, we can cut some unnecessary bits out of EActivity. I'm also adding a new enum property called "state", which is one of: E_ACTIVITY_RUNNING E_ACTIVITY_WAITING E_ACTIVITY_CANCELLED E_ACTIVITY_COMPLETED The state of an activity must be explicitly changed. In particular, when the user cancels an activity the state should be set only after confirming the operation has been cancelled and not when cancellation is requested (e.g. after receiving a G_IO_ERROR_CANCELLED, not when the GCancellable emits "cancelled"). EActivityBar and EActivityProxy widgets have been updated to make this distinction clearer in the UI. E_ACTIVITY_WAITING will be used when activities have to be queued and dispatched in sequence, which I haven't written yet.
* Adapt to Camel API changes.Matthew Barnes2010-09-281-4/+2
|
* Add a GCancellable to EActivity.Matthew Barnes2010-09-191-65/+105
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | EActivity now uses a GCancellable to manage cancellations, instead of having its own redundant cancellation API. API changes are as follows: + e_activity_get_cancellable() + e_activity_set_cancellable() - e_activity_cancel() - e_activity_is_cancelled() - e_activity_get_allow_cancel() - e_activity_set_allow_cancel() EActivity's "cancelled" signal remains, but only as a repeater for GCancellable::cancelled signals. It should not be emitted directly. The presence of a GCancellable implies that cancellation is allowed. EActivity does not create its own default GCancellable, it has to be given one. If a CamelOperation (cast as a GCancellable) is given, EActivity will configure itself to listen for status updates from the CamelOperation and propagate the information to its own "primary-text" and "percent" properties. These changes allowed me to start cleaning up some of the incredibly convoluted logic in mail-mt.c -- in particular, mail_operation_status() is completely gone now. mail-mt.c is still in a transitional state -- much more significant changes coming soon.
* GObject boilerplate cleanup.Matthew Barnes2010-08-251-31/+8
| | | | | | | Prefer thread-safe G_DEFINE_TYPE and G_DEFINE_INTERFACE macros over manual GType registration. This is just a start... lots more to do.
* Bug #610229 - Status bar progress goes beyond 100 percentagepunit2010-04-131-1/+1
|
* Move EActivity and subclasses to e-util.Matthew Barnes2009-11-081-0/+605
Planning to write some asynchronous utility functions in e-util that return EActivity objects.