aboutsummaryrefslogtreecommitdiffstats
path: root/doc/devel/calendar
diff options
context:
space:
mode:
authorFederico Mena Quintero <federico@ximian.com>2001-01-19 02:00:31 +0800
committerFederico Mena Quintero <federico@src.gnome.org>2001-01-19 02:00:31 +0800
commite3297a5f71f408b9ed93c81a25af54c13b93f848 (patch)
treed6630334b849cacae0a5ea50468b08582b728a97 /doc/devel/calendar
parent52f1578c8176b6bf91ee832c6f68e1423210b911 (diff)
downloadgsoc2013-evolution-e3297a5f71f408b9ed93c81a25af54c13b93f848.tar
gsoc2013-evolution-e3297a5f71f408b9ed93c81a25af54c13b93f848.tar.gz
gsoc2013-evolution-e3297a5f71f408b9ed93c81a25af54c13b93f848.tar.bz2
gsoc2013-evolution-e3297a5f71f408b9ed93c81a25af54c13b93f848.tar.lz
gsoc2013-evolution-e3297a5f71f408b9ed93c81a25af54c13b93f848.tar.xz
gsoc2013-evolution-e3297a5f71f408b9ed93c81a25af54c13b93f848.tar.zst
gsoc2013-evolution-e3297a5f71f408b9ed93c81a25af54c13b93f848.zip
Um, why was the doc directory removed from SUBDIRS?
2001-01-18 Federico Mena Quintero <federico@ximian.com> * Makefile.am: Um, why was the doc directory removed from SUBDIRS? svn path=/trunk/; revision=7626
Diffstat (limited to 'doc/devel/calendar')
-rw-r--r--doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml36
1 files changed, 18 insertions, 18 deletions
diff --git a/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml b/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml
index ccfb33de4d..56bcf3aff5 100644
--- a/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml
+++ b/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml
@@ -8,23 +8,36 @@
@pilot_id:
@pilot_status:
-<!-- ##### FUNCTION cal_client_get_events_in_range ##### -->
+<!-- ##### FUNCTION cal_client_load_calendar ##### -->
<para>
</para>
@client:
-@start:
-@end:
+@str_uri:
@Returns:
-<!-- ##### FUNCTION cal_client_load_calendar ##### -->
+<!-- ##### ENUM CalClientLoadStatus ##### -->
+ <para>
+ These values describe the status of a calendar load or create
+ request. After asking a calendar factory to load or create a
+ calendar, the provided listener will get notification about the
+ result in asynchronous fashion. Such notification is represented
+ by one of these enumeration values. For values other than
+ #CAL_CLIENT_LOAD_SUCCESS, the #CalClient object will not accept
+ any other operations on the calendar and it should just be
+ destroyed.
+ </para>
+
+
+<!-- ##### FUNCTION cal_client_get_events_in_range ##### -->
<para>
</para>
@client:
-@str_uri:
+@start:
+@end:
@Returns:
<!-- ##### SIGNAL CalClient::cal-loaded ##### -->
@@ -50,19 +63,6 @@
@client:
@Returns:
-<!-- ##### ENUM CalClientLoadStatus ##### -->
- <para>
- These values describe the status of a calendar load or create
- request. After asking a calendar factory to load or create a
- calendar, the provided listener will get notification about the
- result in asynchronous fashion. Such notification is represented
- by one of these enumeration values. For values other than
- #CAL_CLIENT_LOAD_SUCCESS, the #CalClient object will not accept
- any other operations on the calendar and it should just be
- destroyed.
- </para>
-
-
<!-- ##### FUNCTION cal_client_create_calendar ##### -->
<para>