aboutsummaryrefslogtreecommitdiffstats
path: root/help/devel/calendar/evolution-calendar.sgml
blob: 019fef9ea4ff5ea3b87ed39161192a49af49e86f (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
  <part id="evolution-calendar">
    <docinfo>
      <authorgroup>
    <author>
      <firstname>Federico</firstname>
      <surname>Mena Quintero</surname>
      <affiliation>
        <address>
          <email>federico@helixcode.com</email>
        </address>
      </affiliation>
    </author>
      </authorgroup>
    </docinfo>

    <title>Developing Applications with the &Evolution; Calendar</title>

    <partintro>
      <para>
    This part of the &Evolution; Developer's Guide describes how
    to write applications for the &Evolution; Calendar by using
    its public interfaces.  The &Evolution; Calendar exports its
    functionality through a number of interfaces, including CORBA,
    GTK+ wrappers for Bonobo objects, and other utility libraries.
    This part also describes the internals of the calendar so that
    it will be easy for you to make changes to &Evolution;'s core
    code.
      </para>

      <para>
    You should read this part of the &Evolution; Developer's guide
    if you intend to write client applications that use the
    functionality of the &Evolution; Calendar, such as its storage
    interfaces and generic recurrence engine.  If you intend to
    make changes to the calendar's core code, it will be useful to
    read the sections on the calendar internals as well.  Even if
    you do not intend to modify the core code of the calendar, it
    may be useful to know a few things about the way it works so
    that you can make better use of the public interfaces.
      </para>
    </partintro>

    &calendar-architecture;
    &calendar-alarm-generation;
  </part>

<!--
Local variables:
mode: sgml
sgml-parent-document: ("../evolution-devel-guide.sgml" "book" "book" "")
End:
-->