gsoc2013-evolution - Google Summer of Code 2013 - GNOME

	Commit message (Collapse)	Author	Age	Files	Lines
*	Composer: Show cancellable operations and errors inline.	Matthew Barnes	2010-10-13	1	-31/+50
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	'Send' and 'Save Draft' are now asynchronous and run outside of Evolution's MailMsg infrastructure. Add an EActivityBar to the composer window so these asynchronous operations can be tracked and cancelled even in the absense of a main window. Also add an EAlertBar to the composer window so error messages can be shown directly in the window. Instead of calling e_alert_dialog_run_for_args(), call e_alert_submit() and pass the EMsgComposer as the widget argument. The EMsgComposer will decide whether to show an EAlertDialog or use the EAlertBar, depending on the GtkMessageType of the alert.
*	Adapt to Camel API changes.	Matthew Barnes	2010-09-28	1	-6/+7
\|
*	Add missing linker flag to composer-autosave module.	Matthew Barnes	2010-09-11	1	-0/+1
\|
*	Convert composer autosave to an EExtension.	Matthew Barnes	2010-09-03	6	-0/+1078
	Given the way the autosave feature was awkwardly bolted on to the composer, an EExtension seemed like a natural fit. And it helped clean up some object lifecycle hacks (and bugs). What we have now is a new module consisting of two EExtensions: EComposerAutosave extends EMsgComposer and determines when to kick off an asynchronous autosave operation. EComposerRegistry extends EShell and offers to restore orphaned autosave files on startup (which is also asynchronous now). e-autosave-utils.c holds the actual asynchronous functions and a few other miscellaneous utility functions. Source code for the new module lives in /modules/composer-autosave.