<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gsoc2013-evolution/modules/offline-alert/evolution-offline-alert.error.xml, branch archive-integration</title>
<subtitle>Google Summer of Code 2013 - GNOME - Archive Integration workspace
</subtitle>
<id>https://www.lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/atom?h=archive-integration</id>
<link rel='self' href='https://www.lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/atom?h=archive-integration'/>
<link rel='alternate' type='text/html' href='https://www.lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/'/>
<updated>2011-11-22T05:12:36+00:00</updated>
<entry>
<title>EAlertBar: Add a close button to all alerts.</title>
<updated>2011-11-22T05:12:36+00:00</updated>
<author>
<name>Matthew Barnes</name>
<email>mbarnes@redhat.com</email>
</author>
<published>2011-11-21T23:51:00+00:00</published>
<link rel='alternate' type='text/html' href='https://www.lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/commit/?id=451179909849e4e4058180f095e6ae889d97b797'/>
<id>urn:sha1:451179909849e4e4058180f095e6ae889d97b797</id>
<content type='text'>
Replaces the 'Dismiss' button.  All alerts appearing in an alert bar
should be dismissable (i.e. non-modal).  For modal alerts use a dialog.
</content>
</entry>
<entry>
<title>Add an EOfflineAlert module.</title>
<updated>2010-10-18T16:32:36+00:00</updated>
<author>
<name>Matthew Barnes</name>
<email>mbarnes@redhat.com</email>
</author>
<published>2010-10-16T18:42:43+00:00</published>
<link rel='alternate' type='text/html' href='https://www.lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/commit/?id=b674a37a381d0328a7273bafa62d80203c8cdf70'/>
<id>urn:sha1:b674a37a381d0328a7273bafa62d80203c8cdf70</id>
<content type='text'>
This module posts an alert to the first EShellWindow when starting
offline, and also posts an alert when the network connection drops.

We get frequent questions on the mailing list from users not realizing
Evolution is starting in offline mode, so this is meant to help address
that confusion.
</content>
</entry>
<entry>
<title>EAlert: Allow arbitrary actions to be added.</title>
<updated>2010-10-18T16:32:36+00:00</updated>
<author>
<name>Matthew Barnes</name>
<email>mbarnes@redhat.com</email>
</author>
<published>2010-10-15T18:51:13+00:00</published>
<link rel='alternate' type='text/html' href='https://www.lant.com.tw/~lantw44/cgit/cgit.cgi/gsoc2013-evolution/commit/?id=51ebf20237270a785af0aa0e614db42275a05c62'/>
<id>urn:sha1:51ebf20237270a785af0aa0e614db42275a05c62</id>
<content type='text'>
You can now amend the predefined actions in an EAlert by calling
e_alert_add_action().  Useful for adding actions from an existing
GtkUIManager.

Call e_alert_peek_actions() to obtain a combined list of predefined
and custom actions.  These will typically serve as "related" actions
for GtkButtons (cf. gtk_activatable_set_related_action()).

Also, both EShellWindow and EShellView now implement EAlertSink.  Use
EShellWindow for application-wide alerts, EShellView for view-specific
alerts.
</content>
</entry>
</feed>
