From 18a0bcfe566ca78f0b9304666e0aa300c66310c2 Mon Sep 17 00:00:00 2001 From: nobody Date: Tue, 22 Aug 2000 12:05:30 +0000 Subject: This commit was manufactured by cvs2svn to create tag 'BUG_BUDDY_1_1'. svn path=/tags/BUG_BUDDY_1_1/; revision=4927 --- doc/.cvsignore | 2 - doc/C/.cvsignore | 4 - doc/C/Makefile.am | 51 - doc/C/apx-authors.sgml | 74 -- doc/C/apx-bugs.sgml | 19 - doc/C/apx-fdl.sgml | 678 ------------ doc/C/apx-gloss.sgml | 284 ----- doc/C/apx-gpl.sgml | 414 ------- doc/C/config-prefs.sgml | 570 ---------- doc/C/config-setupassist.sgml | 159 --- doc/C/config-sync.sgml | 67 -- doc/C/evolution-guide.sgml | 132 --- doc/C/fig/calendar.png | Bin 33576 -> 0 bytes doc/C/fig/config-cal.png | Bin 13077 -> 0 bytes doc/C/fig/config-mail.png | Bin 9729 -> 0 bytes doc/C/fig/contact.png | Bin 28369 -> 0 bytes doc/C/fig/filter-new-fig.png | Bin 11861 -> 0 bytes doc/C/fig/mail-druid-pic.png | Bin 35959 -> 0 bytes doc/C/fig/mainwindow-pic.png | Bin 108277 -> 0 bytes doc/C/fig/vfolder-createrule-fig.png | Bin 12084 -> 0 bytes doc/C/preface.sgml | 174 --- doc/C/usage-calendar.sgml | 356 ------ doc/C/usage-contact.sgml | 504 --------- doc/C/usage-mail.sgml | 1132 -------------------- doc/C/usage-mainwindow.sgml | 420 -------- doc/C/usage-notes.sgml | 41 - doc/C/usage-sync.sgml | 22 - doc/Camel-Classes | 35 - doc/ChangeLog | 329 ------ doc/Design | 201 ---- doc/Makefile.am | 1 - doc/devel/.cvsignore | 4 - doc/devel/ChangeLog | 35 - doc/devel/Makefile.am | 64 -- doc/devel/calendar/.cvsignore | 2 - doc/devel/calendar/Makefile.am | 6 - doc/devel/calendar/architecture.sgml | 94 -- doc/devel/calendar/cal-client/.cvsignore | 3 - doc/devel/calendar/cal-client/Makefile.am | 76 -- .../cal-client/evolution-cal-client-decl.txt | 132 --- .../cal-client/evolution-cal-client-sections.txt | 37 - .../calendar/cal-client/evolution-cal-client.args | 0 .../cal-client/evolution-cal-client.hierarchy | 2 - .../cal-client/evolution-cal-client.signals | 21 - .../calendar/cal-client/evolution-cal-client.types | 4 - doc/devel/calendar/cal-client/tmpl/cal-client.sgml | 291 ----- .../tmpl/evolution-cal-client-unused.sgml | 10 - doc/devel/calendar/cal-util/.cvsignore | 3 - doc/devel/calendar/cal-util/Makefile.am | 75 -- .../calendar/cal-util/evolution-cal-util-decl.txt | 852 --------------- .../cal-util/evolution-cal-util-sections.txt | 166 --- .../calendar/cal-util/evolution-cal-util.args | 0 .../calendar/cal-util/evolution-cal-util.hierarchy | 2 - .../calendar/cal-util/evolution-cal-util.signals | 0 .../calendar/cal-util/evolution-cal-util.types | 4 - .../calendar/cal-util/tmpl/cal-component.sgml | 934 ---------------- doc/devel/calendar/cal-util/tmpl/cal-recur.sgml | 88 -- doc/devel/calendar/cal-util/tmpl/cal-util.sgml | 62 -- .../cal-util/tmpl/evolution-cal-util-unused.sgml | 0 doc/devel/calendar/cal-util/tmpl/timeutil.sgml | 260 ----- doc/devel/calendar/evolution-calendar.sgml | 51 - doc/devel/calendar/public-reference.sgml | 24 - doc/devel/calendar/reference.sgml | 24 - doc/devel/evolution-devel-guide.sgml | 50 - doc/white-papers/calendar/calendar.sgml | 209 ---- doc/white-papers/mail/camel.sgml | 339 ------ doc/white-papers/mail/ibex.sgml | 158 --- doc/white-papers/widgets/e-table.sgml | 279 ----- 68 files changed, 10030 deletions(-) delete mode 100644 doc/.cvsignore delete mode 100644 doc/C/.cvsignore delete mode 100644 doc/C/Makefile.am delete mode 100644 doc/C/apx-authors.sgml delete mode 100644 doc/C/apx-bugs.sgml delete mode 100644 doc/C/apx-fdl.sgml delete mode 100644 doc/C/apx-gloss.sgml delete mode 100644 doc/C/apx-gpl.sgml delete mode 100644 doc/C/config-prefs.sgml delete mode 100644 doc/C/config-setupassist.sgml delete mode 100644 doc/C/config-sync.sgml delete mode 100644 doc/C/evolution-guide.sgml delete mode 100644 doc/C/fig/calendar.png delete mode 100644 doc/C/fig/config-cal.png delete mode 100644 doc/C/fig/config-mail.png delete mode 100644 doc/C/fig/contact.png delete mode 100644 doc/C/fig/filter-new-fig.png delete mode 100644 doc/C/fig/mail-druid-pic.png delete mode 100644 doc/C/fig/mainwindow-pic.png delete mode 100644 doc/C/fig/vfolder-createrule-fig.png delete mode 100644 doc/C/preface.sgml delete mode 100644 doc/C/usage-calendar.sgml delete mode 100644 doc/C/usage-contact.sgml delete mode 100644 doc/C/usage-mail.sgml delete mode 100644 doc/C/usage-mainwindow.sgml delete mode 100644 doc/C/usage-notes.sgml delete mode 100644 doc/C/usage-sync.sgml delete mode 100644 doc/Camel-Classes delete mode 100644 doc/ChangeLog delete mode 100644 doc/Design delete mode 100644 doc/Makefile.am delete mode 100644 doc/devel/.cvsignore delete mode 100644 doc/devel/ChangeLog delete mode 100644 doc/devel/Makefile.am delete mode 100644 doc/devel/calendar/.cvsignore delete mode 100644 doc/devel/calendar/Makefile.am delete mode 100644 doc/devel/calendar/architecture.sgml delete mode 100644 doc/devel/calendar/cal-client/.cvsignore delete mode 100644 doc/devel/calendar/cal-client/Makefile.am delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client-decl.txt delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client-sections.txt delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.args delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.hierarchy delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.signals delete mode 100644 doc/devel/calendar/cal-client/evolution-cal-client.types delete mode 100644 doc/devel/calendar/cal-client/tmpl/cal-client.sgml delete mode 100644 doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml delete mode 100644 doc/devel/calendar/cal-util/.cvsignore delete mode 100644 doc/devel/calendar/cal-util/Makefile.am delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util-decl.txt delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util-sections.txt delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.args delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.hierarchy delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.signals delete mode 100644 doc/devel/calendar/cal-util/evolution-cal-util.types delete mode 100644 doc/devel/calendar/cal-util/tmpl/cal-component.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/cal-recur.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/cal-util.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml delete mode 100644 doc/devel/calendar/cal-util/tmpl/timeutil.sgml delete mode 100644 doc/devel/calendar/evolution-calendar.sgml delete mode 100644 doc/devel/calendar/public-reference.sgml delete mode 100644 doc/devel/calendar/reference.sgml delete mode 100644 doc/devel/evolution-devel-guide.sgml delete mode 100644 doc/white-papers/calendar/calendar.sgml delete mode 100644 doc/white-papers/mail/camel.sgml delete mode 100644 doc/white-papers/mail/ibex.sgml delete mode 100644 doc/white-papers/widgets/e-table.sgml (limited to 'doc') diff --git a/doc/.cvsignore b/doc/.cvsignore deleted file mode 100644 index 282522db03..0000000000 --- a/doc/.cvsignore +++ /dev/null @@ -1,2 +0,0 @@ -Makefile -Makefile.in diff --git a/doc/C/.cvsignore b/doc/C/.cvsignore deleted file mode 100644 index cba1534920..0000000000 --- a/doc/C/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -evolution-guide -evolution-guide.junk diff --git a/doc/C/Makefile.am b/doc/C/Makefile.am deleted file mode 100644 index 0d02ac056f..0000000000 --- a/doc/C/Makefile.am +++ /dev/null @@ -1,51 +0,0 @@ -evolution_helpdir = $(datadir)/gnome/help/evolution/C - -SGML_FILES = \ - apx-authors.sgml \ - apx-bugs.sgml \ - apx-fdl.sgml \ - apx-gloss.sgml \ - config-prefs.sgml \ - config-setupassist.sgml \ - config-sync.sgml \ - evolution-guide.sgml \ - preface.sgml \ - usage-calendar.sgml \ - usage-contact.sgml \ - usage-mail.sgml \ - usage-mainwindow.sgml \ - usage-sync.sgml - - -EXTRA_DIST = \ - $(SGML_FILES) - -all: evolution-guide - -evolution-guide: $(SGML_FILES) - -db2html evolution-guide.sgml - -dist-hook: - mkdir $(distdir)/evolution-guide - -cp evolution-guide/*.html evolution-guide/*.css \ - $(distdir)/evolution-guide - mkdir $(distdir)/fig - -cp fig/*.png $(distdir)/fig - -install-data-local: evolution-guide - $(top_srcdir)/mkinstalldirs $(DESTDIR)$(evolution_helpdir)/fig - -for file in $(srcdir)/evolution-guide/*.html $(srcdir)/evolution-guide/*.css; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/$$basefile; \ - done - -for file in $(srcdir)/fig/*.png; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/fig/$$basefile; \ - done - -evolution.ps: evolution.sgml - -db2ps $< - -evolution.rtf: evolution.sgml - -db2rtf $< - diff --git a/doc/C/apx-authors.sgml b/doc/C/apx-authors.sgml deleted file mode 100644 index e064276be3..0000000000 --- a/doc/C/apx-authors.sgml +++ /dev/null @@ -1,74 +0,0 @@ - - - Authors - - Evolution was written by: - - Seth Alves: alves@helixcode.com - Anders Carlssonandersca@gnu.org - Damon Chaplin:damon@helixcode.com - Clifford R. Conover rusty@zootweb.com - Miguel De Icaza: miguel@helixcode.com - Arturo Espinoza arturo@nucleu.unam.mx - Larry Ewing: lewing@helixcode.com - Bertrand Guiheneuf: bertrand@helixcode.com - Tuomas Kuosmanen: tigert@gimp.org - Christopher J. Lahey: clahey@helixcode.com - Matthew Loper: matt@helixcode.com - Federico Mena: federico@helixcode.com - Eskil Heyn Olsendeity@eski.dk - Nat Friedman: nat@helixcode.com - Ettore Perazzoli:ettore@helixcode.com - Russell Steinthal: rms39@columbia.edu - Peter Teichman: peter@helixcode.com - Chris Toshok: toshok@helixcode.com - Radek Doulik: rodo@helixcode.com - Dan Winship: danw@helixcode.com - Michael Zucchi: notzed@helixcode.com - -and other dedicated GNOME programmers. - - - The Evolution code owes a great debt - to the GNOME-pim and - GNOME-Calendar applications, and to - KHTMLW. The developers of - Evolution acknowledge the efforts - and contributions of all who worked on those projects. - - - - For more information please visit the - Evolution Web page. Please send all comments, - suggestions, and bug reports to the GNOME bug tracking - database. Instructions for submitting bug reports can be - found on-line at - http://bugs.gnome.org/Reporting.html. You can also use - command bug-buddy for submitting bug reports. - - - This manual was written by Aaron Weber - (aaron@helixcode.com) and Kevin Breit - (battery841@mypad.com) with the help of the - application programmers and the GNOME Documentation Project. - Please send all comments and suggestions regarding the manual to - the GNOME Documentation Project at - docs@gnome.org. You can also add your comments - online by using GNOME Documentation - Status Table. - - - - - - - - diff --git a/doc/C/apx-bugs.sgml b/doc/C/apx-bugs.sgml deleted file mode 100644 index e7a501acba..0000000000 --- a/doc/C/apx-bugs.sgml +++ /dev/null @@ -1,19 +0,0 @@ - - - Known bugs and limitations - - - This appendix describes known bugs and limitations of - Evolution. Please use the GNOME - Bug Report Tool (known as - bug-buddy at the command line) if you find one - we have not listed. - - - - - The bugs are many, but the application is young, and this is to - be expected. - - - diff --git a/doc/C/apx-fdl.sgml b/doc/C/apx-fdl.sgml deleted file mode 100644 index 8b49729cfc..0000000000 --- a/doc/C/apx-fdl.sgml +++ /dev/null @@ -1,678 +0,0 @@ - - GNU Free Documentation License - - Version 1.1, March 2000 - - - - Copyright © 2000 -
- Free Software Foundation, Inc. - 59 Temple Place, Suite 330, - Boston, - MA - 02111-1307 - USA -
- Everyone is permitted to copy and distribute verbatim copies of this license - document, but changing it is not allowed. - - - - - 0. PREAMBLE - - - The purpose of this License is to make a manual, textbook, or other - written document "free" in the sense of freedom: to assure everyone - the effective freedom to copy and redistribute it, with or without - modifying it, either commercially or noncommercially. Secondarily, - this License preserves for the author and publisher a way to get - credit for their work, while not being considered responsible for - modifications made by others. - - - - This License is a kind of "copyleft", which means that derivative - works of the document must themselves be free in the same sense. It - complements the GNU General Public License, which is a copyleft - license designed for free software. - - - - We have designed this License in order to use it for manuals for free - software, because free software needs free documentation: a free - program should come with manuals providing the same freedoms that the - software does. But this License is not limited to software manuals; it - can be used for any textual work, regardless of subject matter or - whether it is published as a printed book. We recommend this License - principally for works whose purpose is instruction or reference. - - - - - 1. APPLICABILITY AND DEFINITIONS - - - This License applies to any manual or other work that contains a - notice placed by the copyright holder saying it can be distributed - under the terms of this License. The "Document" , below, refers to any such - manual or work. Any member of the public is a licensee, and is - addressed as "you". - - - - A "Modified Version" of the - Document means any work containing the Document or a portion of it, - either copied verbatim, or with modifications and/or translated into - another language. - - - - A "Secondary Section" is a named - appendix or a front-matter section of the Document that deals exclusively with the - relationship of the publishers or authors of the Document to the Document's overall subject (or to - related matters) and contains nothing that could fall directly within - that overall subject. (For example, if the Document is in part a textbook of - mathematics, a Secondary Section - may not explain any mathematics.) The relationship could be a matter - of historical connection with the subject or with related matters, or - of legal, commercial, philosophical, ethical or political position - regarding them. - - - - The "Invariant Sections" are - certain Secondary Sections whose - titles are designated, as being those of Invariant Sections, in the notice that - says that the Document is released - under this License. - - - - The "Cover Texts" are certain - short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that - says that the Document is released - under this License. - - - - A "Transparent" copy of the - Document means a machine-readable - copy, represented in a format whose specification is available to the - general public, whose contents can be viewed and edited directly and - straightforwardly with generic text editors or (for images composed of - pixels) generic paint programs or (for drawings) some widely available - drawing editor, and that is suitable for input to text formatters or - for automatic translation to a variety of formats suitable for input - to text formatters. A copy made in an otherwise Transparent file format whose markup - has been designed to thwart or discourage subsequent modification by - readers is not Transparent. A - copy that is not "Transparent" - is called "Opaque". - - - - Examples of suitable formats for Transparent copies include plain - ASCII without markup, Texinfo input format, LaTeX input format, SGML - or XML using a publicly available DTD, and standard-conforming simple - HTML designed for human modification. Opaque formats include - PostScript, PDF, proprietary formats that can be read and edited only - by proprietary word processors, SGML or XML for which the DTD and/or - processing tools are not generally available, and the - machine-generated HTML produced by some word processors for output - purposes only. - - - - The "Title Page" means, for a - printed book, the title page itself, plus such following pages as are - needed to hold, legibly, the material this License requires to appear - in the title page. For works in formats which do not have any title - page as such, "Title Page" - means the text near the most prominent appearance of the work's title, - preceding the beginning of the body of the text. - - - - - - 2. VERBATIM COPYING - - - You may copy and distribute the Document in any medium, either - commercially or noncommercially, provided that this License, the - copyright notices, and the license notice saying this License applies - to the Document are reproduced in - all copies, and that you add no other conditions whatsoever to those - of this License. You may not use technical measures to obstruct or - control the reading or further copying of the copies you make or - distribute. However, you may accept compensation in exchange for - copies. If you distribute a large enough number of copies you must - also follow the conditions in section - 3. - - - - You may also lend copies, under the same conditions stated above, and - you may publicly display copies. - - - - - - 3. COPYING IN QUANTITY - - - If you publish printed copies of the Document numbering more than 100, and - the Document's license notice - requires Cover Texts, you must - enclose the copies in covers that carry, clearly and legibly, all - these Cover Texts: Front-Cover - Texts on the front cover, and Back-Cover Texts on the back cover. Both - covers must also clearly and legibly identify you as the publisher of - these copies. The front cover must present the full title with all - words of the title equally prominent and visible. You may add other - material on the covers in addition. Copying with changes limited to - the covers, as long as they preserve the title of the Document and satisfy these conditions, - can be treated as verbatim copying in other respects. - - - - If the required texts for either cover are too voluminous to fit - legibly, you should put the first ones listed (as many as fit - reasonably) on the actual cover, and continue the rest onto adjacent - pages. - - - - If you publish or distribute Opaque copies of the Document numbering more than 100, you - must either include a machine-readable Transparent copy along with each - Opaque copy, or state in or - with each Opaque copy a - publicly-accessible computer-network location containing a complete - Transparent copy of the Document, free of added material, which - the general network-using public has access to download anonymously at - no charge using public-standard network protocols. If you use the - latter option, you must take reasonably prudent steps, when you begin - distribution of Opaque copies - in quantity, to ensure that this Transparent copy will remain thus - accessible at the stated location until at least one year after the - last time you distribute an Opaque copy (directly or through your - agents or retailers) of that edition to the public. - - - - It is requested, but not required, that you contact the authors of the - Document well before - redistributing any large number of copies, to give them a chance to - provide you with an updated version of the Document. - - - - - - 4. MODIFICATIONS - - - You may copy and distribute a Modified - Version of the Document - under the conditions of sections 2 - and 3 above, provided that you - release the Modified Version under - precisely this License, with the Modified - Version filling the role of the Document, thus licensing distribution - and modification of the Modified - Version to whoever possesses a copy of it. In addition, you - must do these things in the Modified - Version: - - - - - - A - - Use in the Title Page (and - on the covers, if any) a title distinct from that of the Document, and from those of - previous versions (which should, if there were any, be listed in - the History section of the Document). You may use the same - title as a previous version if the original publisher of that - version gives permission. - - - - - - - B - - List on the Title Page, as - authors, one or more persons or entities responsible for - authorship of the modifications in the Modified Version, together with at - least five of the principal authors of the Document (all of its principal - authors, if it has less than five). - - - - - - - C - - State on the Title Page - the name of the publisher of the Modified Version, as the - publisher. - - - - - - - D - - Preserve all the copyright notices of the Document. - - - - - - - E - - Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices. - - - - - - - F - - Include, immediately after the copyright notices, a license - notice giving the public permission to use the Modified Version under the terms - of this License, in the form shown in the Addendum below. - - - - - - - G - - Preserve in that license notice the full lists of Invariant Sections and required - Cover Texts given in the - Document's license notice. - - - - - - - H - - Include an unaltered copy of this License. - - - - - - - I - - Preserve the section entitled "History", and its title, and add - to it an item stating at least the title, year, new authors, and - publisher of the Modified Version - as given on the Title - Page. If there is no section entitled "History" in the - Document, create one stating - the title, year, authors, and publisher of the Document as given on its Title Page, then add an item - describing the Modified - Version as stated in the previous sentence. - - - - - - - J - - Preserve the network location, if any, given in the Document for public access to a - Transparent copy of the - Document, and likewise the - network locations given in the Document for previous versions it - was based on. These may be placed in the "History" section. You - may omit a network location for a work that was published at - least four years before the Document itself, or if the - original publisher of the version it refers to gives permission. - - - - - - - K - - In any section entitled "Acknowledgements" or "Dedications", - preserve the section's title, and preserve in the section all - the substance and tone of each of the contributor - acknowledgements and/or dedications given therein. - - - - - - - L - - Preserve all the Invariant - Sections of the Document, unaltered in their text - and in their titles. Section numbers or the equivalent are not - considered part of the section titles. - - - - - - - M - - Delete any section entitled "Endorsements". Such a section may - not be included in the Modified - Version. - - - - - - - N - - Do not retitle any existing section as "Endorsements" or to - conflict in title with any Invariant Section. - - - - - - - If the Modified Version includes - new front-matter sections or appendices that qualify as Secondary Sections and contain no - material copied from the Document, you may at your option designate - some or all of these sections as invariant. To do this, add their - titles to the list of Invariant - Sections in the Modified - Version's license notice. These titles must be distinct from - any other section titles. - - - - You may add a section entitled "Endorsements", provided it contains - nothing but endorsements of your Modified - Version by various parties--for example, statements of peer - review or that the text has been approved by an organization as the - authoritative definition of a standard. - - - - You may add a passage of up to five words as a Front-Cover Text, and a passage of up - to 25 words as a Back-Cover - Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of - Front-Cover Text and one of - Back-Cover Text may be added by - (or through arrangements made by) any one entity. If the Document already includes a cover text - for the same cover, previously added by you or by arrangement made by - the same entity you are acting on behalf of, you may not add another; - but you may replace the old one, on explicit permission from the - previous publisher that added the old one. - - - - The author(s) and publisher(s) of the Document do not by this License give - permission to use their names for publicity for or to assert or imply - endorsement of any Modified Version - . - - - - - - 5. COMBINING DOCUMENTS - - - You may combine the Document with - other documents released under this License, under the terms defined - in section 4 above for modified - versions, provided that you include in the combination all of the - Invariant Sections of all of the - original documents, unmodified, and list them all as Invariant Sections of your combined - work in its license notice. - - - - The combined work need only contain one copy of this License, and - multiple identical Invariant - Sections may be replaced with a single copy. If there are - multiple Invariant Sections with - the same name but different contents, make the title of each such - section unique by adding at the end of it, in parentheses, the name of - the original author or publisher of that section if known, or else a - unique number. Make the same adjustment to the section titles in the - list of Invariant Sections in the - license notice of the combined work. - - - - In the combination, you must combine any sections entitled "History" - in the various original documents, forming one section entitled - "History"; likewise combine any sections entitled "Acknowledgements", - and any sections entitled "Dedications". You must delete all sections - entitled "Endorsements." - - - - - - 6. COLLECTIONS OF DOCUMENTS - - - You may make a collection consisting of the Document and other documents released - under this License, and replace the individual copies of this License - in the various documents with a single copy that is included in the - collection, provided that you follow the rules of this License for - verbatim copying of each of the documents in all other respects. - - - - You may extract a single document from such a collection, and - distribute it individually under this License, provided you insert a - copy of this License into the extracted document, and follow this - License in all other respects regarding verbatim copying of that - document. - - - - - - 7. AGGREGATION WITH INDEPENDENT WORKS - - - A compilation of the Document or - its derivatives with other separate and independent documents or - works, in or on a volume of a storage or distribution medium, does not - as a whole count as a Modified - Version of the Document, - provided no compilation copyright is claimed for the compilation. - Such a compilation is called an "aggregate", and this License does not - apply to the other self-contained works thus compiled with the Document , on account of their being - thus compiled, if they are not themselves derivative works of the - Document. If the Cover Text requirement of section 3 is applicable to these copies - of the Document, then if the Document is less than one quarter of the - entire aggregate, the Document's - Cover Texts may be placed on - covers that surround only the Document within the aggregate. Otherwise - they must appear on covers around the whole aggregate. - - - - - - 8. TRANSLATION - - - Translation is considered a kind of modification, so you may - distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations - requires special permission from their copyright holders, but you may - include translations of some or all Invariant Sections in addition to the - original versions of these Invariant - Sections. You may include a translation of this License - provided that you also include the original English version of this - License. In case of a disagreement between the translation and the - original English version of this License, the original English version - will prevail. - - - - - - 9. TERMINATION - - - You may not copy, modify, sublicense, or distribute the Document except as expressly provided - for under this License. Any other attempt to copy, modify, sublicense - or distribute the Document is - void, and will automatically terminate your rights under this - License. However, parties who have received copies, or rights, from - you under this License will not have their licenses terminated so long - as such parties remain in full compliance. - - - - - - 10. FUTURE REVISIONS OF THIS LICENSE - - - The Free - Software Foundation may publish new, revised versions of the - GNU Free Documentation License from time to time. Such new versions - will be similar in spirit to the present version, but may differ in - detail to address new problems or concerns. See http://www.gnu.org/copyleft/. - - - - Each version of the License is given a distinguishing version - number. If the Document specifies - that a particular numbered version of this License "or any later - version" applies to it, you have the option of following the terms and - conditions either of that specified version or of any later version - that has been published (not as a draft) by the Free Software - Foundation. If the Document does - not specify a version number of this License, you may choose any - version ever published (not as a draft) by the Free Software - Foundation. - - - - - - Addendum - - - To use this License in a document you have written, include a copy of - the License in the document and put the following copyright and - license notices just after the title page: - - - - Copyright © YEAR YOUR NAME. - - - - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.1 or - any later version published by the Free Software Foundation; with the - Invariant Sections being LIST - THEIR TITLES, with the Front-Cover - Texts being LIST, and with the Back-Cover Texts being LIST. A copy - of the license is included in the section entitled GNU Free - Documentation License. - - - - If you have no Invariant - Sections, write "with no Invariant Sections" instead of saying - which ones are invariant. If you have no Front-Cover Texts, write "no - Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise - for Back-Cover Texts. - - - - If your document contains nontrivial examples of program code, we - recommend releasing these examples in parallel under your choice of - free software license, such as the GNU General Public - License, to permit their use in free software. - - - - - \ No newline at end of file diff --git a/doc/C/apx-gloss.sgml b/doc/C/apx-gloss.sgml deleted file mode 100644 index 55ab3ed8a1..0000000000 --- a/doc/C/apx-gloss.sgml +++ /dev/null @@ -1,284 +0,0 @@ - - - Glossary - - - Attachment - - - Any file sent along with an email. Attachments may be embedded in - a message or appended to it. - - - - - - Automatic Indexing - - - Pre-sorting procedure that allows - Evolution to refer to data quickly. - It enables faster searches and decreases memory usage for - data displays. - - - - - - Bcc (Blind Carbon Copy) - - - A way of addressing a message. Bcc is used to send a group of - people an e-mail, while hiding their names and addresses from each - other. - - - - - - Cc (Carbon Copy) - - - Carbon-copies are used to send a 3rd party a copy of the e-mail, - so they an keep up to date on a conversation, without being in the - To: list. - - - - - - - Emoticon - - - Also called smileys, emoticons are the little sideways faces made - of colons and parentheses which people use to convey emotion in email. - Examples: :-) or ;( . - - - - - - Evolution - - - Evolution is the GNOME - groupware application. - - - - - - Execute - - - To run a program. Any file that can be run is called an - executable. Evolution can download - executable attachments, but before they can be run, the files must - be marked as executable with a shell or file manager. This - security precaution prevents the automatic or accidental execution - of malicious programs. - - - - - - Filter - - - Within Evolution, a filter is a method - of sorting mail automatically. You can create filters to perform - one or more actions on a message that meets any (or all) of a wide - range of criteria. - - - - - - Forward - - - the user can send a third party a message - which was sent to the user originally. - - - - - - Groupware - - - Groupware is a term describing an application which helps groups - of people work together. Typically, a groupware application will - have several productivity features built into one program. - - - - - - Haiku - - - A Japanese form of poetry. Haiku are unrhymed, and - three lines long. The first and last lines should have five - syllables, and the second line seven syllables. The subject - matter is traditionally related to the seasons. - - - - - - HTML - - - Hyper-text Markup Language(HTML) is the layout - language which all webpages are written in. HTML can be used - inside of e-mails to insert images, justfiy text different ways, - and even include webpages inside the e-mail itself. - - - - - - Hot Key - - - Hot-keys are keyboard combinations used to do actions on a - computer instead of using the mouse to do the same action. - Hot-keys can speed up computer usage. - - - - - - iCal - - - iCal is the program which - Evolution uses to manage the calendar - section. - - - - - - - LDAP - - - LDAP is a protocol which allows a client to search through a large database - of addresses, phone numbers, and people, as an alternative to a physical - phone book. - - - - - - Mail Client - - - A mail client is the application with which a person reads and - sends e-mail. Its counterparts are the various types of mail - servers, which handle user authentication and direct messages from - sender to recipient. - - - - - - - Minicard - - - A format for the display of contact data. Similar in appearance - to a small business card. - - - - - - Nautilus - - - Nautilus is the next generation file - manager for GNOME being written by Eazel. - - - - - - Nickname - - - An alias for an e-mail address. - - - - - - Script - - - A program which is written in an interpreted language, which can - be executed. - - - - - - Shortcut Bar - - - The Shortcut Bar is where the user accesses - all the components of Evolution from. - - - - - - Signature - - - Signatures allow a user to specify a message to place at the bottom of - every email sent. A signature can be anything from a favorite quote to - a link to a webpage. - - - - - - - Spam - - - Spam: useless, unwanted e-mail. Spam normally comes in forms of - chain-letters and advertisements for unscrupulous websites or - services. Messages that are merely useless are called - "opt-in newsletters." - - - - - - vFolder - - - vFolders allow an e-mail to be shared among multiple folders, so - it appears that theres a copy of the e-mail in each folder. - - - - - diff --git a/doc/C/apx-gpl.sgml b/doc/C/apx-gpl.sgml deleted file mode 100644 index 7c7e4cd0f7..0000000000 --- a/doc/C/apx-gpl.sgml +++ /dev/null @@ -1,414 +0,0 @@ - - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - - - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - -Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - - The precise terms and conditions for copying, distribution and -modification follow. - - - - - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - - - -NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - - END OF TERMS AND CONDITIONS - - - - How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - - <one line to give the program's name and a brief idea of what it does.> -Copyright (C) < year> <name of author> - - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - - - -Also add information on how to contact you by electronic and paper mail. - - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - - Gnomovision version 69, Copyright (C) year name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - - <signature of Ty Coon>, 1 April 1989 - Ty Coon, President of Vice - - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. - - - - - - - - - - - - diff --git a/doc/C/config-prefs.sgml b/doc/C/config-prefs.sgml deleted file mode 100644 index e0f6dd0297..0000000000 --- a/doc/C/config-prefs.sgml +++ /dev/null @@ -1,570 +0,0 @@ - - - - - Advanced Configuration - - Perhaps your mail server has changed names. Perhaps you've - grown tired of a certain layout for your appointments. - Whatever the reason, you want to change your - Evolution settings. This chapter - will tell you how to do just that. - - - - Mail Settings - - To change your mail settings, first go to your - Inbox. Then select Mail - Settings from the Tools menu. - This will open the mail preferences - window, illustrated in . Mail Preferences are - separated into several categories: - - - Identity - - - This allows you to set - your name, email address, and other information. The - default values are the ones found on your system account. - - - - - Sources - - - Set your mail-checking protocols and servers here. - - - - - - Sources - - - Set your mail-checking protocols and servers here. - - - - - - News Servers - - - Specify your News Server preferences here. - - - - - - - - - - - -
- Preferences Dialog - - Setting mail preferences - - - -
- - - - - Identity Settings - - If you have only one email address, or use automatic - forwarding to funnel multiple addresses to one account, then - you will only need to configure one identity. You may, - however, want more that one. To alter an identity, click on - it in the Identity tab of the - Preferences window, and then click - Edit. To add a new identity, simply - click Add. - - - - In either case, you'll be presented with a dialog box with - four fields: - - - - Full Name: by default, this is the - same name as the full name described in your user - account on your computer. You can select another if you - wish. - - - - - Email address: Enter your email - address in this space. - - - - - Organization: If you send email as - a representative of a company or other organization, - enter its name here. - - - - - Signature file: You may choose a - small text file to be appended to every message that you - send. Typically, signature files include address or - other contact information, or a favorite quotation. - They should not be more than three lines long. - - - - - - - - - Network Settings - - In order to send mail with - Evolution, you need to connect to - your network. To do that, you'll need to know your user name - and password, what sort of mail sending and receiving - protocols your network uses, and the names of the servers - you'll be using. If you're switching from another groupware - or email program, you can almost certainly use the same - settings as you did with that program. Select the - Sources tab in the - Preferences window to tell - Evolution where you want to get - your mail, and click Transports to - determine how you want to send your mail. - - - - Mail Sources - - The Mail Sources tab allows you to - edit, add, or delete methods of retrieving mail from - servers. Clicking on Add or - Edit will bring up a dialog box to - offer you the following options: - - - Mail source type: - - - Select from IMAP, POP or Unix-style - mbox files. - - - - - Server: - - - Enter the name of your mail server in this field. - For example: - mail.mycompany.com - - - - - Username: - - - Enter your user name here. Eva Lucianne Tester's - user name is eltester. - - - - - Authentication: - - - Your system administrator will know which type of - authentication your system requires. - Evolution can also detect - what sorts of authentication are available once it - knows where to find the server. - - - - - Test values before continuing - - - If this box is checked, - Evolution will attempt to - make sure that all the other entries in the dialog - window are correct. - - - - - - - - Transports - - The Transports tab lets you set how - you will send mail. Evolution currently supports two mail - transport options: SMTP, which uses a - remote mail server, and sendmail, - which uses the sendmail program - on your local system. Sendmail - is more difficult to configure, but offers more flexibility - than plain SMTP. - - - To use SMTP, you'll need to enter the - name of your SMTP server, which should look like: - smtp.isp.net. - - - Evolution can - attempt to determine if you have entered the right server - name. To have it do so, check the box labelled - Test these values before continuing - before you click OK. - - - - - - - - News Servers - - When you first select the News - Servers tab, you will see a blank box with - three familiar buttons on the right: - Add, Edit, - and Delete. - - - Click Add to add a news server; you - will be prompted for its name. Enter the name, click - OK, and you're done. (FIXME, this needs work). - - - - - Other Mail Preferences - - Not everything fits neatly into categories. This tab - contains some miscellaneous configurations that don't have - too much to do with each other. - - - - Send messages in HTML format - - - If you check this box, you will send - messages as HTML by default. If you leave it unchecked, your - messages will be sent without HTML formatting unless you select - Format HTML - in the message composer. - See - for more information about HTML mail. - - - - - Folder Format - - By default, - Evolution saves its mail - in the - mbox - format. You can switch to the - mh - format if you like. Note that this is an advanced - feature and may cause you to lose some messages, so - you should probably make a backup of your - evolution - directory first. In addition, it will take quite - some time if you have a large mailbox. - - - - - - - - - Managing the Contact Manager - - To set the behavior of your Contact Manager, click on the - Contact Manager tab in the - Preferences window. - - - You can set the following options: - - - - - Configuring the Calendar - - This section discusses calendar-specific preferences. While - looking at your calendar, select - Preferences from the - Edit menu. This will open up the - Preferences window. It contains four - tabs: Time display, - Colors, To Do List - and Alarms. The calendar - preferences window is illustrated in . - - -
- Calendar Preferences Dialog - - If this worked on my job as well as my calendar... - - - -
- - - - - Time Display Settings - - The Time display tab lets you set the - following: - - - Time format - - You may choose between twelve-hour (AM/PM) and - twenty-four hour time formats here by clicking the - appropriate radio button. - - - - - Weeks start on - - You can set weeks to start on Sunday or on Monday. - - - - Day range - - - When does your work day start, and when does it end? - In the day and week views, - Evolution displays all the - hours in the range you select here, even if there are - no appointments for those times. Of course, you can - still schedule an appointment outside of these hours, - and if you do, the display will be extended to show - it. - - - - - - - - Calendar Colors - - The colors tab allows you to decide - what color your calendar will be. The tab consists of a - sample calendar on the right and a list of ten items that can - be colored in different ways. If you click on the color - button to the right of each item, you will bring up a - color-selector window where you can choose to alter that - color. By clicking OK in the color - selection dialog, you can see the results of the color on the - sample calendar. - - The display elements whose color you can set are: - - - - - Outline: The lines between days - and at the top of the display. - - - - - Headings: Text color for day - and month names and other headings. - - - - - Empty days: This is the - background color for any time slots in which you have no appointments. - - - - - - Appointments: This is the - background color for any time slots in which you have appointments. - - - - - Highlighted day: The - background color for a selected time slot. - - - - - - - Day numbers: Text color for date numbers. - - - - - - - Current day's number: Text color for today's date. - - - - - To-Do item that is not yet - due: Text color for To-Do list items that are - not yet due. (Or maybe background color? find out!) - - - - - - To-Do item that is due today: - Text color for today's tasks. - - - - - To-Do item that is overdue: - Text color for overdue tasks. - - - - - - - - - To Do List Settings - - You can choose what information the To Do list displays and the - way it is displayed. The two areas of the To Do - List tab offer several options each: - - - Show on To Do List - - - This box contains three items. If you select the - check boxes next to them, that information will appear - in the To Do list for each task it contains: - - - Due Date - - - Time Until Due - - - Priority - - - - - - - Style Options - - - Select among the following checkboxes to determine - how your To Do list will look: - - - Highlight overdue items - - - Highlight items due today - - - Highlight not yet due items - - - - - - - - - - - Alarms Settings - - The alarms tab enables you to select from three boxes: - - - Beep on display alarms: select - this box to have Evolution beep - at you for any alarms you have set. If you leave this box - unchecked, Evolution will only - alert you to events by opening a dialog box. - - - - Audio alarms timeout after: - Select this button to have the beeping stop automatically - after a certain number of seconds. - - - Enable snoozing for: If you - would like to have the option to tell - Evolution to repeat an alarm in - a few minutes, select this button and decide how long - you'd like it to wait. - - - - - - - - - - - General Preferences - - Additional configuration options will be covered here, as - they become available. - - - - - - - - - diff --git a/doc/C/config-setupassist.sgml b/doc/C/config-setupassist.sgml deleted file mode 100644 index 52ca546b9a..0000000000 --- a/doc/C/config-setupassist.sgml +++ /dev/null @@ -1,159 +0,0 @@ - - Easy Setup with the Setup Assistant - - The setup assistant can gather most of the information - necessary for Evolution's daily - operation. If you prefer more detailed or advanced - configuration, see . - - - - Mail Setup - - The first time you try to send or receive mail with - Evolution, the mail - setup assistant will pop up to help you with your - email preferences. If you don't plan to use email, or if - you'd rather deal with your email preferences later, click - Cancel. - - - The setup assistant (sometimes called a - Druid) will guide you through the - network configuration process. It will ask you for some - basic information; your system administrator or ISP should - have the answers you'll need. The mail setup assistant is - pictured in . - - - - -
- Mail Setup Assistant - - Evolution Main Window - - - -
- - - - - The assistant will ask you for the following information: - - - - Name: - Your - full name: eg. Eva Lucianne Tester - - - - Email address: - - Your email address: eg. eltester@helixcode.com - - - - - Organization: - - - Organization: Any organization you - represent. Leave this blank if you wish. - - - - - - Signature File: - - - A text file appended to any email you send. A signature - file typically consists of your name and email address, - or a quotation you like. It should be fewer than four - lines of text. - - - - - - Mail source type: - - - Evolution supports three mail - sources: POP servers, the most common email server type; - IMAP, which stores mail remotely and allows access from - multiple locations, and UNIX-style - mbox files. Ask your system - administrator which one you use. - - - - - - Server: - - - This should be the name of your mail server: it should - look something like: - mailserver.organization.org. - - - - - - Username: - - - Normally, this is the part of your email address before - the @ character, and - Evolution has selected that - value as the default. If you have a different username, - you can enter it here. - - - - - - Authentication: - - - Select the type of authentication you will use. You can - click Detect supported types to - find out which authentication protocols your network - allows. - - - - - - Mail Transport: - - - This is the mail sending protocol you will want to use. - Evolution supports both SMTP - and sendmail. - - - - - - - To learn how to configure Evolution - in greater detail, or to change preferences once you have set - them, see . - - - - - - - - - - - - - diff --git a/doc/C/config-sync.sgml b/doc/C/config-sync.sgml deleted file mode 100644 index ae78a6daaf..0000000000 --- a/doc/C/config-sync.sgml +++ /dev/null @@ -1,67 +0,0 @@ - - - - - Setting up your synchronization system - - Synchronization presents you with two issues you'll need to - deal with. The first one is pretty simple: you'll need to get - the data to move among the various devices you're using. If - you've already got Gnome-Pilot - working, then all you have to do is tell it to use Evolution - as a conduit. If you haven't used - Gnome-Pilot before, you'll need to - run the GNOME Control Center and go - through the hand-held device setup assistant. Then you can - create the Evolution conduit and press the hotsync button. - - - If that doesn't work, jump up and down several times and swear - loudly. Then make sure you've got - Gnome-Pilot going to the right - device (for my serial port, it's /dev/ttys0, not the default - /dev/pilot) and that you have read and write permission on - that device. If you don't you'll need to be added to whatever - group has those permissions (for my system, it's tty). - Alternately, if you're the only user of your computer and - don't care too much about security, just use - su to become root, and then use - chmod a+rw /dev/[DEVICENAME] to set - universal read and write permissions on that port— just - don't tell your sysadmin I said you could. (Sysadmins, of - course, would never do such a thing.) - - - Once Evolution knows where to get - the mail, address, and calendar data, it needs to know what to - do with it. When you synchronize your local data with the data on - a server or handheld device, you may run into conflicts: - perhaps you have ended up with two cards with the same name - and different addresses, or old mail that has been deleted - from one device but not the other. What if you want to keep - only the most recent mail on your hand-held or your laptop, - but all the mail on the LDAP server or your desktop machine? - Select the Synchronization tab from the - Preferences window to set up the - conflict resolution preferences. - - - You can set Evolution's - synchronization behavior in the following ways: - - - - - Data Loss Prevention - - It's always a good idea to make a backup. If you set your - synchronization behaviors wrong, you could end up deleting - the messages and cards you want to keep, and keeping the - ones you want to delete. Before you change these - preferences, make a backup of your - Evolution files. You can do - this by... - - - - diff --git a/doc/C/evolution-guide.sgml b/doc/C/evolution-guide.sgml deleted file mode 100644 index 59b50120b9..0000000000 --- a/doc/C/evolution-guide.sgml +++ /dev/null @@ -1,132 +0,0 @@ - - - - - - - - - - - - - - - - -]> - - - - - - A User's Guide to Evolution - - AaronWeber - KevinBreit - - - 2000 - Helix Code, Inc., - Kevin Breit - - - - - Permission is granted to copy, distribute and/or modify this - document under the terms of the GNU Free - Documentation License, (FDL) Version 1.1 or any later - version published by the Free Software Foundation with no - Invariant Sections, no Front-Cover Texts, and no Back-Cover - Texts. - - - The software described by this document falls under the - GNU General Public License, or GPL. - - - The licenses are included with this document in , and ; you may also obtain - a copy from the Free Software Foundation by visiting their Web site or - by writing to: Free Software Foundation, Inc., 59 Temple Place - - Suite 330, Boston, MA 02111-1307, USA. - - - Many of the names used by companies to distinguish their - products and services are claimed as trademarks. Where those - names appear in any GNOME documentation, and those trademarks - are made aware to the members of the GNOME Documentation - Project, the names have been printed in caps or initial caps. - - - - - - This is version 0.4 of the Evolution manual, describing version - 0.3.1 of Evolution. - - - - - &PREFACE; - - - Using Evolution - - - Part one of the Evolution manual - describes how to use Evolution - for email, contact management, and appointment and task - scheduling. You'll find as you go along that, as with most of - Linux, there's more than one way to do things, and you can - pick whichever method you like best. - - - - &USAGE-MAINWINDOW; - &USAGE-MAIL; - &USAGE-CONTACT; - &USAGE-CALENDAR; - &USAGE-NOTES; - &USAGE-SYNC; - - - - Configuring and Managing Evolution - - - Evolution is highly configurable. - Usually, when developers say that, they mean that they didn't - test it out thoroughly and have left it to other hackers to - "configure" themselves a working system. When we say - configurable, we mean that although - Evolution will work perfectly well - with minimal setup hassle, you can alter its behavior to fit - your needs with just a little more work. - - - - &CONFIG-SETUPASSIST; - &CONFIG-PREFS; - &CONFIG-SYNC; - - &APX-GLOSS; - &APX-BUGS; - &APX-AUTHORS; - &APX-FDL; - &APX-GPL; - - - - - - - - - - - - - diff --git a/doc/C/fig/calendar.png b/doc/C/fig/calendar.png deleted file mode 100644 index 47354813a2..0000000000 Binary files a/doc/C/fig/calendar.png and /dev/null differ diff --git a/doc/C/fig/config-cal.png b/doc/C/fig/config-cal.png deleted file mode 100644 index e124196279..0000000000 Binary files a/doc/C/fig/config-cal.png and /dev/null differ diff --git a/doc/C/fig/config-mail.png b/doc/C/fig/config-mail.png deleted file mode 100644 index ef270858f7..0000000000 Binary files a/doc/C/fig/config-mail.png and /dev/null differ diff --git a/doc/C/fig/contact.png b/doc/C/fig/contact.png deleted file mode 100644 index 1610e278a4..0000000000 Binary files a/doc/C/fig/contact.png and /dev/null differ diff --git a/doc/C/fig/filter-new-fig.png b/doc/C/fig/filter-new-fig.png deleted file mode 100644 index 4c612ce5fc..0000000000 Binary files a/doc/C/fig/filter-new-fig.png and /dev/null differ diff --git a/doc/C/fig/mail-druid-pic.png b/doc/C/fig/mail-druid-pic.png deleted file mode 100644 index f29f3e77be..0000000000 Binary files a/doc/C/fig/mail-druid-pic.png and /dev/null differ diff --git a/doc/C/fig/mainwindow-pic.png b/doc/C/fig/mainwindow-pic.png deleted file mode 100644 index 0ff712efa5..0000000000 Binary files a/doc/C/fig/mainwindow-pic.png and /dev/null differ diff --git a/doc/C/fig/vfolder-createrule-fig.png b/doc/C/fig/vfolder-createrule-fig.png deleted file mode 100644 index 571a487ba4..0000000000 Binary files a/doc/C/fig/vfolder-createrule-fig.png and /dev/null differ diff --git a/doc/C/preface.sgml b/doc/C/preface.sgml deleted file mode 100644 index bb6cb4d948..0000000000 --- a/doc/C/preface.sgml +++ /dev/null @@ -1,174 +0,0 @@ - - - - Introduction - -
- What is Evolution, and What Can It Do for Me? - - The word "evolution" means "a process of improvement and - development." The GNOME application - Evolution is meant to be a more - evolved groupware program, and an - integral part of the Internet-connected desktop. - - - As part of the GNOME project, - Evolution is free software. The - program and its source code are released under the terms of - the GNU Public License (GPL), and the documentation falls - under the Free Documentation License (FDL), which is included - with this document (). For more - information about the GPL and the FDL, visit the Free Software - Foundation's website at http://www.fsf.org. - - - - This is a preview release - - Please help develop Evolution - by submitting bug reports when you find bugs. You can do - so by using the Bug Report - Tool (known as bug-buddy - at the command line). - - - - - - Evolution is a suite of tools to - help you work in a group. You can use it to send, receive, - and organize email, manage address and other contact - information, and maintain a calendar. It enables you to do - those things on one or several computers, connected directly - or over a network, for one person or for large groups. - Evolution can handle almost all - your communications tasks with the power and flexibility of - the GNOME desktop environment. - - - The developers of Evolution had - four major goals for their project: - - - - - The application must be both powerful and easy - to use. That means a familiar and intuitive - interface that users could customize to their liking, and - the development of shortcuts for complex tasks. - - - - - Evolution must meet and - exceed the standards set by other groupware products. - It must include support for most major network protocols - so that it can integrate seamlessly with existing - hardware and network environments. - - - - - The project must support open standards and protocols - to turn Evolution into an - advanced development platform. From the simplest - scripting to the most complex network and component - programming, Evolution - needed to offer developers an environment for - cutting-edge application development. - - - - - Data must be safe: Evolution - must not lose mail or corrupt mailbox files. It will - not execute scripts, automatically forward a virus to - your entire contacts list, or delete files from your - hard disk. - - - - - - Evolution is designed to make most - daily tasks faster. For example, it takes only one or two - clicks to enter an appointment or an address card sent to you - by email, or to send email to a contact or appointment. - Evolution makes displays faster and - more efficient, so searches are faster and memory usage is - lower. People who get lots of mail will appreciate advanced - features like vFolders, which - let you save searches as though they were ordinary mail - folders. - - -
- -
- About This Book - - - This version of the Evolution - User's Guide is a draft. It is missing - huge chunks of information, and many of the features it - describes are unimplemented. All the content is subject to - change, especially if you help. Please send comments on the - guide to aaron@helixcode.com. If you would like - to work on the guide please contact me or see the GNOME - Documentation project web site. This - paragraph will be removed in later versions of the manual. - - - - - This book is divided into two sections. The first section is a - guided tour— it will - explain how to use Evolution. If - you are new to Evolution or to - groupware in general, this is the section for you. The second - section, covering configuration, - is targeted at more advanced users, but anyone who wants to - change the way Evolution looks or - acts can benefit from reading it. - - - Typographical conventions - - Some kinds of words are marked off with special typography: - - Applications - Commands typed at the command line - Labels for interface items - - Menu selections look like this: - - Menu - Submenu - Menu Item - - - Buttons you can click - Anything you type in - Text output from a computer - - - - -
- - - - - - - - - - - - - diff --git a/doc/C/usage-calendar.sgml b/doc/C/usage-calendar.sgml deleted file mode 100644 index 9ec3b0f60e..0000000000 --- a/doc/C/usage-calendar.sgml +++ /dev/null @@ -1,356 +0,0 @@ - - - - The Evolution Calendar - - To begin using the calendar, select - Calendar from the shortcut - bar. By default, the calendar starts showing today's - schedule on a grey and white ruled background. At the upper - right, there's a monthly calendar you can use to switch days. - Below that, there's a TaskPad, where you can - keep a sort of glorified to-do list that's not linked to your - calendar. The calendar's daily view is shown in . - - -
- Evolution Calendar View - - Evolution Contact Manager Window - - - -
- - - - - Ways of Looking at your Calendar - - - You can view your calendar by the day, by the week, by the - month, or by the year; press the calendar-shaped buttons on the - right side of the toolbar to switch between views. - - - To view yesterday's appointments, (last week's, if you're in - the weekly view, and last month's for the monthly view), click - the Pref button. For tomorrow, next week, - or next month, click Next, and of course, - click Today for today. - - - To visit a specific date's calendar entries, click - Go To and select the date in the dialog - box that appears. - - - - - - - - Scheduling With the Evolution Calendar - - The Evolution calendar allows you to - schedule events for yourself or a group of people. It can - handle events that repeat, event lengths from ten minutes to - multiple days, and events that have a date but no specific - time. Of course, you can also set event reminders and alarms - so that you don't forget about everything you've just put into - your calendar. Basically, it can handle almost any schedule you - throw at it. - - - Creating events - - To create a new calendar event, select - - File - New - Appointment - - or click the New button on the left end - of the toolbar. The New Appointment - dialog will pop up with the usual menu bar, tool bar, and - window full of choices for you. - - - Your event must have a starting and ending date — by - default, today — but you can choose whether to give it - starting and ending times or to mark it as an All - day event. For the purposes of the calendar, an - All day event begins at ten in the - morning, runs until eleven at night, and is displayed at the - top of a day's event list rather than inside it. That makes - it easy to have events that overlap and fit inside each other. - For example, a conference might be an all day event, and the - meetings at the conference would be timed events. Events with - starting and ending times can also overlap, however, and when - they do they're displayed as multiple columns in the day view - of the calendar. - - - Doing Two Things At Once - - If you create two calendar events that overlap, - Evolution will display them as - multiple columns in the calendar window. If you manage to - do both things at once, I'd like to meet you. - - - - You can have as many as four different - Alarms, any time prior to the event - you've scheduled. You can have one alarm of each type: - - - Display - - - A window will pop up on your screen to remind you of - your event. - - - - - Audio - - - Choose this to have your deliver a sound alarm. - - - - - Program - - - Select this if you would like some additional application - to run as a reminder. You can enter its name in the - text field, or find it with the - Browse button. - - - - - Mail - - - Evolution will send an - email reminder to the address you enter into the text - field. - - - - - - - - Classification is a little more - complicated, and only applies to calendars on a - network. Public is the default category, - and a public event can be viewed by anyone on the calendar - sharing network. Private denotes one - level of security, and Confidential a - higer level. Exact determinations and implementations of - this feature have yet to be determined. - - - The Recurrence tab lets you describe - repetition in events ranging from once every day up to once - every 100 years. You can then choose a time when repetition - will stop, and, under Exceptions, pick - individual days when the event will not - recur. - - - - Once you're done with all those settings, click on the disk - icon in the toolbar. That will save the event and close the - event editor window. If you want, you can alter an event - summary in the calendar view by clicking on it and typing. You - can change other settings by right-clicking on the event in - the and then choosing Edit this Appointment. - - - - - - - - - The Task Pad - - The Task Pad, located in the lower right corner of the - calendar, lets you keep a list of tasks separate from your - calendar events. Tasks are colored and sorted by priority and - due-date (see for more - information), and are included with calendar data during - synchronization with a hand-held device. - - - To record a new task, click the Add - button below the list. Evolution - will pop up a small window with five items in it: - - - - Summary: - - - The description you enter here will appear in the To Do - list itself. - - - - - - Due Date: - - - Decide when this item is - due. You can either type in a date and time, or select one from - the Calendar and time drop-down menus. - - - - - Priority: - - - Select a level of importance from 1 (most important) to 9 - (least important). - - - - - Item Comments: - - - If you wish, you can keep a more detailed description of - the item here. - - - - - - - Once you've added a task to your to-do list, its summary - appears in the Summary section of the - calendar window. To view or edit a detailed description of an - item, double-click on it, or select it and click - Edit. You can delete items by selecting - them and clicking on the Delete button. - - - - - Multiple Calendars - - Evolution permits you to have and - maintain multiple calendars. This is useful if you maintain - schedules for other people, if you are responsible for resource - or room allocation, or if you have multiple personalities. - - - - Keeping Multiple Calendars - - Keelyn has one calendar for her own schedule. Next to that - she maintains one for the conference room, so people know when - they can schedule meetings. On the local network, she - maintains a calendar that reflects when consultants are going - to be on site, and another that keeps track of when the Red - Sox are playing. - - - - To create a new calendar, select - - File New - Calendar - . - - You can place the calendar in any calendar folder and access it - from the folder view. Alarms, configuration, and display for - each calendar are seperate from each other. - - - - - - - - - - - - - - diff --git a/doc/C/usage-contact.sgml b/doc/C/usage-contact.sgml deleted file mode 100644 index 4f9b9fd058..0000000000 --- a/doc/C/usage-contact.sgml +++ /dev/null @@ -1,504 +0,0 @@ - - - - The Evolution Contact Manager - - - The Evolution contact manager can - handle all of the functions of an address book, phone book, or - Rolodex. Of course, it's a lot easier to update - Evolution than it is to change an - actual paper book. Evolution also - allows easy synchronization with hand-held and remote devices. - Since Evolution supports most major - network protocols, including LDAP, it can - fit into almost any existing network. - - - Another advantage of the Evolution - address book is its integration with the rest of the - application. That means that when you look for someone's - address, you can also see a history of appointments with that - person. Or, you can get an e-mail with contact information in - it and create a new address card on the spot. In addition, - searches and folders and all work in the same way they do in the - other components, so you don't have to learn another system for - similar tasks. - - - This chapter will cover using the - Evolution contact manager to organize - any amount of contact information, share addresses over a - network, and several ways to save time with everyday tasks. To - learn about configuring the contact manager, see . - - - - Getting Started With the Contact Manager - - - To open up your address book, click on - Contacts in the shortcut bar. The - contact manager is illustrated in . By default, the contact manager - shows all your cards in alphabetical order, in a - minicard format. You can select other - views from the View menu, and adjust the - width of the colums by clicking and dragging the grey column - dividers. - - - -
- Evolution Contact Manager - - Evolution Contact Manager Window - - - -
- - - The toolbar for the address book is quite simple: - - - Press New for a new contact. - - - - Find brings up an in-depth search window. - - - - Press Print to print one or more cards. - - - Delete deletes a selected card. - - - - - The last feature is Quick Search; to use - it, just type in the name of the person you're looking for and - hit Enter. - Evolution will search through all - the cards to find one that matches. - - - If there are no matches, the card display will be blank. To - display all of your contacts, you can - leave the Quick Search field blank, and - press enter. - - - The rest of the contact manager is taken up by the display of - your cards. You can view it as a table or as a list of - cards— switch between them in the View - menu — and move through them alphabetically alphanumeric - buttons and the scrollbar at the right of the window. - - - - Destroy, Create, or Change Cards - - - To delete a card, click on it once to select it, then press the - Delete Card button. If you have - multiple cards selected, you'll delete mutliple cards. - - - Adding or changing cards is slightly more complicated. Any - time you add information to the contact manager, whether it's - an old card you're editing or a new card you're just adding to - your address book, you'll use the contact editor. To change a - card that already exists, just double click it to open the - contact editor window with all the current information already - filled in. If you want to create a new one, clicking the - New Card button will open up that same - window, but with empty fields instead of full ones. Either - way, it's the same tool for quite similar tasks, and you'll - find that it's pretty flexible and can store quite a lot more - than you'd think would fit onto a file card. - - - - The contact editor window has two tabs, - General, for basic contact information, - and Details, for a more specific - description of the person. In addition, it contains a full - menu bar, which is still evolving rapidly. - - -
- Evolution Contact Editor - - Evolution Contact Editor - - - -
- - The General tab contains no less - than seven sections, each with an icon: a face, for name and - company; a telephone for phone numbers; an envelope for email - address; a house for postal address; a file folder for - contacts, and a briefcase for categories. You can guess what - sort of information belongs in fields like Job - Title and Web page address, - but there are several parts of the window that are a little - more interesting. - - - The Categories feature is discussed in - , but the remaining - features are described here: - - - Full Name - - - The Full Name field has two - major features: - - - - You can enter a name into the Full - Name field, but you can also click the - Full Name button to bring - up a small dialog box with a few text boxes - - - Title: - - Enter an honorific or select one from the menu. - - - - First: - - The person's first, or given, name. - - - - Middle: - - The middle name or initial, if any, goes here. - - - - Last: - - The last name (surname) belongs here. - - - - Suffix: - - Suffixes such as "Jr." or "III" can go here. - - - - - - - - The Full Name field also - interacts with the File As - box to help you organize your contacts. - - - To see how it works, type a name in the - Full Name field: - Eva Lucianne Tester. - You'll notice that the File - As field also fills up, but in reverse: - Tester, Lucianne. - You can pick Eva - Tester from the drop-down, or - type in your own, such as Lucianne - Tester, Eva. - - - Filing Suggestion - - Don't enter something entirely different from - the actual name, since you might forget that - you've filed Eva's information under "F" for - "Fictitious Helix Code Employees" - - - - - - - - - Multiple Values for Fields - - - If you click on the small arrow buttons next to the - Primary Email field, you can also - choose Email 2 and - Email 3. Although the contact - editor will only display one of those at any given - time, Evolution will - remember them all. The arrow buttons next to the - telephone and postal address fields work in the same - way. - - - - - - - - - - - Organizing your Contact Manager - - Organizing your contact manager is a lot like organizing your - mail. You can have folders and searches the same way you can - with mail, but the contact manager does not allow vFolders. It - does, however, allow each card to fall under several - categories, and allow you to create your own categories. - Categories are discussed . - - - - - - Groups of contacts - - Evolution offers two ways for you - to organize your cards. The first way is to use folders; - this works the same way that mail folders do. For more - flexibility, you can also mark contacts as members of - different categories. - - - - Grouping with Folders - - The simplest way to group address cards is to use folders. - By default, cards start in the - Contacts folder. If you've read then you already know that you - can create a new folder by selecting - - File - New - Folder - - and that you can put new folders anywhere you like. Note - that each card must be in one and only one folder, unless - you want to have duplicate cards. - - - To put a card into a folder, just drag it there from the - folder view. Remember that contact cards can only go in - contact folders, just like mail can only go in mail folders, - and calendars in calendar folders. - - - - - Grouping with Categories - - The other way to group cards is to mark them as belonging - to different categories. The difference between folders - and categories is that folders contain cards, but category - membership is a property of each card. That means that you - can mark a card as being in several categories or no - category at all. For example, I put my friend Matthew's - card in the "Business" category, because he works with me, - the "Friends" category, because he's also my friend, and - the "Frequent" category, because I call him all the time - and can never remember his phone number. - - - To mark a card as belonging to a category, click the - Categories button at the lower - right. From the dialog box that appears, you can check as - many or as few categories as you like. - - - Then, you can refer to all the cards in that category by: - FEATURE NOT IMPLEMENTED... FIXME - - - If the master list of categories doesn't suit you, you can - add your own. Just enter the new category's name in the - text box, then click Categories and - choose Add to Master List in the - window that appears. - - - - Another way to use Categories - - You can categorize contacts by typing the category - names into the Categories - field. You can also create new categories that way: - just type in a category name, and it counts as a - category. - - - - - - - - Sharing your Cards (and keeping them to yourself) - - Cards can be shared over a network. This is the sort of - feature you'll want to use if your company has a list of - vendors and clients that needs constant updating. If you - also share your calendars, people can avoid duplicating - work and keep up to date on developments within their - workgroup or across the entire company. - - - - Sharing Address Cards and Calendar Data - - Ray wants to schedule a meeting with Company X, so he - checks the network for the Company X address card so he - knows whom to call there. Since his company also shares - calendars, he then learns that his co-worker Deanna has - already scheduled a meeting with Company X next Thursday. - He can either go to the meeting himself or ask Deanna to - discuss his concerns for him. Either way, he avoids - scheduling an extra meeting with Company X. - - - - Of course, you don't want to share all of your cards— why - overload the network with a list of babysitters, or tell - everyone in the office you're talking to new job prospects? - Evolution lets you decide which - folders you want to make accessible to others. - - - To begin sharing a folder of address cards, wait until - Evolution supports this - feature. - - - - - Contact Manager Tools - - The contact manager works with - Evolution mail and the calendar to - help you add new address cards quickly. However, it can also - manage mailing lists. There are more tools planned, and when - they arrive, they will be described in this - section. - - - - Send me a Card: Adding New Cards Quickly - - As noted before, when you get information about a person in - the mail or in a calendar entry, you can add it to an address - card. To do so, right click on any email address or email - message, and select Add Address - Card from the menu that appears. Of course, - Evolution also adds cards from a - hand-held device during HotSync operation. For more - information about that, see . - - - - - Managing a Mailing list - - You already know that when you are writing an email, you can - address it to one or more people, and that - Evolution will fill in addresses - from your contact manager's address cards if you let it. In - addition to that, you can send email to everyone in a - particular group. - - - - Future versions of Evolution will - allow you to you export a group of cards to a spreadsheet, - database, or word processor so you can print address labels - or prepare large postal mailings. - - - - - - - Contact Manager Menubar Reference - - - - - - - - - - - - - - - - - - diff --git a/doc/C/usage-mail.sgml b/doc/C/usage-mail.sgml deleted file mode 100644 index de2f3b0a23..0000000000 --- a/doc/C/usage-mail.sgml +++ /dev/null @@ -1,1132 +0,0 @@ - - - - Evolution Mail - - An Overview of the Evolution Mailer - - Evolution email is like other email - programs in all the ways you would hope: - - - - It can sort and organize your mail in a wide variety of ways with - folders, searches, and filters. - - - - - It can send and receive mail in HTML or as plain text, and - supports file attachments. - - - - - It supports multiple mail sources, including IMAP, POP3, - and local mbox files. - - - - - - However, Evolution has some important - differences. First, it's built to handle very large amounts of - mail without slowing down or crashing. Both the filtering and searching functions - were built for speed and efficiency on gargantuan mail - volumes. There's also the Evolution - vFolder, an - advanced organizational feature not found in other mail clients. - If you get a lot of mail, or if you keep every message you get - in case you need to refer to it later, you'll find that feature - especially useful. - - - - You can start reading email by clicking - Inbox in the shortcut bar. By - default, the Inbox is open when you - start Evolution, and the first - time you see your inbox, there's a message in it from Helix - Code welcoming you to the application. - - - - - Reading, Getting and Sending Mail - - Reading a Message - - The first time you open your - Evolution - Inbox, you will see a window like the one - in , with a message from - Helix Code in the message list. The - message is displayed below that, in the view - pane. If you find the view - pane too small, you can double-click on the - message in the message list to have it - open in a new window. As is the case with folders, you can - right-click on messages in the message list and get a menu of - possible actions: - - - - View Message - - Select this item to view the message in - the view pane of the Evolution - window. - - - - - Edit Message - - This item is available only for messages and drafts - that you have written. Select it to open the message - composer and make changes to the message. - - - - - Print Message - - Select this item to print a message. - - - - - Reply to Sender - - Use this item to reply only to the author of the message. - - - - - Reply to All - - Send a reply to the author of the message - and to all others on the recipient list. See for more information. - - - - - Forward Message - - Send the message on to another person. - See for - information about how to use the Forward feature. - - - - - Delete Message - - Mark the message for deletion. Choose - ActionsExpunge - to delete marked messages permanently. - - - - - Move Message - - Select this item to move the message to another folder. - This will open a dialog to let you choose the destination - from a folder tree. - - - - - - - You can also select the order in which messages appear in - that list. To sort by sender, subject, or date, click on the - bars with those labels at the top of the message list. If - you click twice, you'll sort them in reverse order. - - - Aside from sorting the messages, you can opt to have the - messages threaded. Select - View Threaded Message - List to turn the threaded view on - or off. If the option selected, - Evolution will attempt to - associate related messages by using the - References, - In-Reply-To, and - Subject message headers. Messages - which are related are then placed next to each other, so that - it's easier to follow the thread of a conversation from - message to message. - - - Go ahead and click on the message in the message - list. That selects the message. Then click on - the Delete button in the tool bar. The - message now has a line through it, because you've marked it - for deletion. If you really want to get rid of it, choose - Expunge from the - Tools menu. That will delete it - permanently. If you want to keep it, click - Delete again, and it will no longer be - marked as deleted. At some point in the future, this feature - will change to something a little less counter-intuitive. - - - -
- Evolution Mail - - Inbox - - - -
- - - - - - Checking Mail - - To check your email, just click Get - mail in the toolbar. If this is the first time - you've done so, the mail setup - assistant will ask you for the information it - needs to check your mail (see for more information). If - you're checking mail over a network (instead of from local - mbox files), you'll need to enter your - email password. Type it in, click OK and - Evolution will download your mail. - New mail will appear in your Inbox. - - - - Once you've entered your password, - Evolution will hold it in memory so - that you don't have to retype it every time you want to check - mail. It will only remember the password until you quit the - application; each time you run - Evolution, you need to re-enter - your password. If you'd like - Evolution to forget your password - sooner, select - ActionsForget - Passwords, and it will do so - immediately. - - - If you get an error message instead of mail, you probably - need to change your network settings. To learn how to - do that, have a look at , or ask your system - administrator. - - - - Attachments, HTML Mail, and Live Documents - - If someone sends you a file attached to an email (an - "attachment"), Evolution will - display the file at the bottom of the message to which it's - attached. Text, HTML, and most images will be displayed in - the message itself. For other files, - Evolution will provide a link and - icon at the end of the message. Click on that, and - Evolution will ask you where you - want to put the file. Once you've chosen a location and - saved the file, you can open, move, copy, or execute it just - like any other, using Nautilus or - your favorite shell or file manager. - - - - Evolution can also display - HTML-formatted mail, complete with graphics. HTML - formatting will display automatically, although you can - turn it off if you prefer. - - - - - - - - - Writing and Sending Mail - - You can start writing a new email message by selecting - File - New - Mail, or by pressing the - Compose button in the Inbox toolbar. - When you do so, the New Message window - will open, as shown in . - - - -
- New Message Window - - Evolution Main Window - - - -
- - - - - Enter an address in the To: field, a - subject in the Subject: and a message in - the big empty box at the bottom of the window, and press - Send. That's easy. It may even be - too easy, which is why I like to queue my messages up to be - sent a few minutes later. - - - Send Now, Send Later - - Evolution will send mail immediately unless you tell it to - do otherwise by selecting Send - Later from the MENU in - the message composition window. Then, when you press - Send, all your unsent messages will - go out at once. I like to use "Send Later" because it - gives me a chance to change my mind about a message before - it goes out. That way, I don't send anything I'll regret - the next day. - - - To learn more about how you can specify message queue - and filter behavior, see . - - - - - - You can probably guess the purpose of the buttons labelled - Cut, Copy, - Paste and Undo, but - there's a bit more to sending mail that's less obvious. In - the next few sections, you'll see how - Evolution handles additional - features, including mailing lists, attachments, and - forwarding. - - - - - Choosing Recipients - - If you have created address cards in the contact manager, - you can also enter nicknames or other portions of address - data, and Evolution will complete - the address for you. If you enter a name or - nickname that can go with more than one card, Evolution will - open a dialog box to ask you which person you meant. - - - Alternately, you can click on the - To:, Cc:, or - Bcc: buttons to get a list of email - addresses. Click the check-boxes next to the addresses, then - click OK, and the address will be - added to the appropriate form field. - - - For more information about using email together with the - contact manager and the calendar, see and . - - - - Multiple Recipients - - In addition, you can mark recipients in three different - ways. The To: field is for the - primary recipients of the message you are going to send. - However, it is considered bad form to have more than a few - email addresses in this section. - - - If you're writing to one person, but want to keep a third - party up to date, you can use Cc:. - Hearkening back to the dark ages when people used - typewriters and there were no copy machines, "Cc" stands - for "Carbon Copy." Use it whenever you want to share a - message you've written to someone else. - - Using the Cc: field - - When Susan sends an email to a client, she puts her - co-worker, Tim, in the in the - Cc: field, so that he know - what's going on. The client can see that Tim also - received the message, and knows that he can talk to - Tim about the message as well. - - - - - If you have a large number of recipients, or if you want - to send mail to several people without sharing the - recipient list, you should use - Bcc:. "Bcc" stands for "Blind Carbon - Copy", and means that people you put in the - Bcc: field get the message, but - nobody else sees their email address. They will still see - the list of addresses from the To: - and Cc: fields, though. - - - Using the Bcc: field - - Tim is sending an email announcement to all of his - company's clients, some of whom are in competition - with each other, and all of whom value their - privacy. He needs to use the - Bcc: field here. If he puts - every address from his address book's "Clients" - category into the To: or - Cc: fields, he'll make the - company's entire client list - public. Don't assume it won't happen to you! - - - - - - - - Replying to Messages - - In order to reply to a message, click on it once in the - message list to select it. Then press the - Reply button. A window like the - New Message window will appear, but - the subject will already be present— the same subject - as the message to which you are replying, but with Re: - before it, to mark it as a reply. In addition, the full - text of the previous message is inserted into the new - message, either in italics (for HTML display) or with the - > character (in plain text mode) before each line. This - indicates quoting. You can intersperse your message with - the quoted material as shown in - - - -
- Reply Message Window - - Evolution Main Window - - - -
- - - - - If a message has several recipients, as in the case of - mailing lists or messages that have been carbon copied, you - may wish to click Reply to All - instead of Reply. If there are large - numbers of people in the Cc: or - To: fields, this can save substantial - amounts of time. But be careful, and always make sure you - know who is getting a message: it could be a mailing list - with thousands of subscribers. - - Using the Reply to All feature - - Susan sends an email to a client, and sends copies to - Tim and to an internal company mailing list of - co-workers. If Tim wants to make a comment to all of - them, he uses Reply to All, but - if he just wants to tell Susan that he agrees with her, - he uses Reply. - - - - - - - Embellish your email with HTML - - You can't normally use text treatments or pictures in - emails, which is why you've probably seen people use - asterisks for emphasis or use - emoticons to convey their - feelings. However, most of the newer email programs can - include and display images and text treatments as well as - basic alignment and paragraph formatting. - - - HTML Mail is not a Default Setting - - Some people do not have HTML-capable mail clients, or - prefer not to receive HTML-enhanced mail because it is - slower to download and display. Some - people refer to HTML mail as "the root of all evil" and - get very angry if you send them HTML mail, which is why - Evolution sends plain text - unless you explicitly ask for HTML. To send HTML mail, - you will need to select - HTML in the mail settings dialog box. See - for more information. - - - If you format a message with HTML, but do not have - Send Messages as HTML enabled in your - mail settings, the composer will remove your text styles. - It will, however, preserve indentation and lists. The - same is true for individuals in your address book whom you - have not marked as wanting to receive HTML mail. - - - - HTML formatting tools are located just above the - composition frame, and in the Insert and - Format menus. Your message text will - appear formatted in the composer window, and the message - will be sent as HTML. - - - The icons in the toolbar are explained in tool-tips, which - appear when you hold your mouse over the buttons. The - buttons fall into four categories: - - - Headers and lists - - - Choose Normal for a default - text style, or Header 1 through - Header 6 for varying sizes of - header. You can also select - pre for preformatted text - blocks, and three types of List - Item. - - - - - Text style - - - - B is for bold text - I for italics - U to underline - S for a strikethrough. - - - - - - Alignment - - - Located next to the text style buttons, - these three paragraph icons should be familiar to - users of most word processing software. The - leftmost button will make your text left-justified, - the center button, centered, and the right hand - button, right-justified. - - - - - - Indentation rules - - - The button with the arrow pointing left will reduce - a paragraph's indentation, and the right arrow will - increase its indentation. - - - - - - - There are three tools that you can find only in the - Insert menu. - - - Insert Link: - - - Use this tool to - put hyperlinks in your HTML messages. When you - select it, Evolution will - prompt you for the Text that - will appear, and the Link, where - you should enter the actual web address (URL). - - - - - Insert Image: - - - Insert Image: Select this item to - embed an image into your email, as was done in the welcome - message. Images will appear at the location of the - cursor. - - - - - Insert Rule: - - This will insert a horizontal line, or rule, into your document. - You'll be presented with a dialog box which gives you - the choice of size, percentage of screen, shading, and - alignment; if you leave everything at the default - values you'll get a thin black rule all the way across - the screen. - - - - - - A Technical note on HTML Tags - - The composer is a WYSIWYG (What You See Is What You Get) - editor for HTML. That means that if you enter HTML - directly into the composer— say, <B>Bold Text</B>, the - the composer will assume you meant exactly that string - of characters, and not "make this text bold," as an HTML - composition tool or text editor would. - - - - - Attachments - - If you want to attach a file to your email message, you - can drag it from your desktop into the message window, or - click the button in the toolbar with a paper clip on it, - labelled Attach. If you click the - Attach button, - Evolution will open a file - selection dialog box, to ask you which file you want to - send. Select the file and click OK. - - - When you send the message, a copy of the file will - go with it. Be aware that big attachments can take a long - time to download. - - - - - - - - Forwarding Mail - - The post office forwards your mail for you when you change - addresses, and you can forward mail when you get a letter by - mistake. The email Forward button - works in much the same way. It's particularly useful if you - have received a message and you think someone else would - like to see it. You can forward a message as an attachment - to a new message (this is the default) or - you can send it inline as a quoted - portion of the message you are sending. Attachment - forwarding is best if you want to send the full, unaltered - message on to someone else. Inline forwarding is best if - you want to send portions of a message, or if you have a - large number of comments on different sections of the - message you are forwarding. Remember to note from whom the - message came, and where, if at all, you have removed or - altered content. - - - To forward a message you are reading, press - Forward on the toolbar, or select - Message - Forward . If you - prefer to forward the message inline - instead of attached, select - Message Forward - Inline from the menu. Choose an - addressee as you would when sending a new message; the - subject will already be entered, but you can alter it. - Enter your comments on the message in the - composition frame, and press - Send. - - - - Seven Tips for Email Usage - - I started with ten, but four were "Don't send - spam." - - - - - Don't send spam or forward chain mail. If you must, - watch out for hoaxes and urban legends, and make sure - the message doesn't have multiple layers of email - quotation symbols (>) indicating multiple layers - of careless inline forwarding. - - - - - - Always begin and close with a salutation. Say - "please" and "thank you", just like you do in real - life. You can keep your pleasantries short, but be pleasant! - - - - - - ALL CAPS MEANS YOU'RE SHOUTING! - - - - - - Never write anything in email you wouldn't say in - public. Old messages have a nasty habit of - resurfacing when you least expect. - - - - - - Check your spelling and use complete sentences. - - - - - - Don't send nasty emails (flames). If you get one, - don't write back. - - - - - - When you reply or forward, include just enough of - the previous message to provide context: not too - much, not too little. - - - - - Happy mailing! - - - - - - Organizing Your Mail - - Even if you only get a few email messages a day, you probably - want to sort and organize them. When you get a hundred a day - and you want to refer to a message you received six weeks ago, - you need to sort and organize them. - Fortunately, Evolution has the tools - to help you do it. - - - - Getting Organized with Folders - - Evolution keeps mail, as well as - address cards and calendars, in folders. You start out with a - few, like Inbox, - Outbox, and Drafts, - but you can create as many as you like. Create new folders by - selecting New and then - Folder from the - File menu. - Evolution will as you for the name - and the type of the folder, and will provide you with a folder - tree so you can pick where it goes. - - - When you click OK, your new folder will - appear in the folder view. You can - then put messages in it by dragging and dropping them, or by - using the Move button in the toolbar. - If you create a filter with the filter - assistant, you can have mail moved to your folder - automatically. - - - - - Searching for Messages - - Most mail clients can search through your messages for you, - but Evolution does it faster. You - can search through just the message subjects, just the message - body, or both body and subject. - - - To start searching, enter a word or phrase in the text area - right below the toolbar, and choose a search type: - - - Body or subject contains: - - - This will search message subjects and the messages - themselves for the word or phrase you've entered in - the search field. - - - - - Body contains: - - - This will search only in message text, not the subject - lines. - - - - - Subject contains: - - - This will show you messages where the search text is - in the subject line. It will not search in the - message body. - - - - - Body does not contain: - - - This finds every email message that does not have the - search text in the message body. It will still show - messages that have the search text in the subject - line, if it is not also in the body. - - - - - Subject does not contain: - - - This finds every mail whose subject does not contain - the search text. - - - - - - Then, press Enter. - Evolution will show your search - results in the message list. - - - - - - Staying organized: Mail Filters in Evolution - - Filters sort your email for you as it arrives. Most often, - you'll want to have Evolution put - mail into different folders, but you can have it do anything - you like. People who subscribe to multiple mailing lists, or - who often need to refer to messages they have sent, find - filters especially helpful to separate personal from - list-related mail, but they're good for anybody who gets more - than a few messages a day. To create a filter, select - - Tools Filter - Assistant . This will bring up a - window which will guide you through filter creation. The - filter assistant is shown in - -
- Creating a new Filter - - Creating a new Filter - - - -
- - - - The filter assistant window - contains a window listing rules, and an option to create a - new rule. To start filtering your mail, click - Add to add a filtering rule. - You'll decide when it should take place: - - - - When mail arrives: Select - this option to have messages filtered as they - arrive. - - - - - When mail is sent: Select - this option to filter your outgoing mail. You - can use this feature to keep your - Outbox as organized as - your Inbox. - - - - - - - Then, the filter assistant will ask you which emails it should - act upon. You can set criteria based on message size, the - sender, primary addressee or Cc: list, words in the subject or - body of the message, or any combination of criteria. Check the - boxes next to each criterion you would like to use. - - - Once you've decided which messages to filter, the assistant - will ask you the sort of action you wish to take. You can - file, delete, or forward the message, and you can also have it - be exempted from other filters which would otherwise have - acted upon it. - - - - Two Notable Filter Features - - - Any incoming email that does not meet - filter action criteria remains in the Inbox. - - - If you move a folder, your filters - will follow it. - - - - - - - - - Getting Really Organized with Virtual Folders - - If filters aren't flexible enough for you, or you find - yourself performing the same search again and again, consider - a virtual folder. Virtual folders, or vFolders, are an - advanced way of viewing your email messages within - Evolution. If you get a lot of - mail or often forget where you put messages, vFolders can help - you stay on top of things. - - - A vFolder is really a hybrid of all the other organizational - tools: it looks like a folder, it acts like a search, and you - set it up like a filter. Once you've set it up, you'll be - able to open it and read the messages in it as though it were - a normal mail folder. It's not a folder, though, because when - you open a vFolder, Evolution - performs a search for you. It's not a regular search, though, - because you can build a vFolder with a very complicated set of - criteria with multiple inclusions and exclusions, as though - you were setting up a filter. - - - - - - As messages that meet the vFolder criteria arrive or are - deleted, Evolution will - automatically place them in and and remove them from the - vFolder contents list. When you delete a message, it gets - erased from the folder in which it actually exists, as well as - any vFolders which include it. - - - That's pretty complicated, but it can be useful. For example, - if I have a folder for all the email from one person, and - another folder for all the email on a given topic, I - feel organized. But when the person - sends me mail about the topic, my whole email filing universe - becomes chaotic, and I need vFolders to save the day for me. - - - That sounds silly, but imagine a business trying to keep track - of mail from hundreds of vendors and clients, or a university - with overlapping and changing groups of faculty, staff, - administrators and students. The more mail you need to organize, the less - you can afford the sort of confusion that stems from an - organizational system that's not flexible enough. vFolders - make for better organization because they can accept - overlapping groups in a way that regular folders and filing - systems can't. - - - - Using Folders, Searches, and vFolders - - To organize my mail box, I can set up a vFolder for emails - from my friend Vince. Then, whenever I want to see the - messages Vince has sent me, I open the vFolder, and every - message he's sent me shows up, no matter where I've - actually filed it. If I want, I can also create a vFolder - containing any message from my list of co-workers which - also has the name of the project in it. That way, when - Vince sends me mail about the project, I can see that - message both in the "Vince" vFolder and in the "Project" - vFolder. That's because when I open up the "Vince" folder, - I'm really performing a search for all the mail from Vince, - and when I open the "Project" folder I'm really performing - a search for all the mail about the project. - - - - - - - To create a vFolder, select VFolder - Assistant from the Tools - menu in the main window. This - will bring up a dialog box that looks suspiciously like - the Filter Assistant (for more information on filters, see - ), and which - presents you with a list of vFolders you have previously - created. If you have already created vFolders, you can - click on them in the frame labelled Select Rule - Type, and edit or remove them. If you have - not created any, there will be only one available option: - click Add to add a new vFolder. - - - You'll be prompted to create a filtering rule. You can build - your own from the ground up, or select one of several base - rules to customize. Your options are: - - - For matching messages: - - - Choose this to create your own set of rules for the - vFolder. You may select one or more search criteria; - the vFolder you create will contain messages that - match all of them. - - - - - Messages from a certain person: - - - The remaining three rules are simpler. Select this - one to create a vFolder that will contain only - messages from an address you enter. - - - - - Messages to a certain address: - - - Any messages sent directly to this address will be in - the vFolder you create. This vFolder is an absolute - must for people with multiple email addresses. - - - - - Messages with a given subject: - - - Enter a subject, and the vFolder will contain messages - with that subject. - - - - - - The selection window is shown in - -
- Selecting a vFolder Rule - - Selecting a vFolder Rule - - - -
- - - - Once you click Next, you'll customize - the vFolder rule. The rules for the vFolder you're creating - will appear as phrases in the bottom pane of the window. You - can click on the blue underlined text in the phrase to alter - it to your liking. For example, when I create a vFolder to - contain all messages from rupert@helixcode.com - that have the word "evolution" in the message body, the bottom - frame says: The From address matches - rupert@helixcode.com and the body contains - "evolution".. - - - - - diff --git a/doc/C/usage-mainwindow.sgml b/doc/C/usage-mainwindow.sgml deleted file mode 100644 index 8a71f2d4f2..0000000000 --- a/doc/C/usage-mainwindow.sgml +++ /dev/null @@ -1,420 +0,0 @@ - - - - The Main Window: Evolution Basics - - Start Evolution by selecting - Evolution from the - Applications of the Main Panel - Menu, or by typing evolution at the - command-line. The first time you run the program, it will create - a directory called evolution in your home - directory, where it will keep all your - Evolution-related files. - - - After Evolution starts - up, you will see the main window, with the - Inbox open. It should look a lot like the - picture in . On the left of - the main window is the shortcut - bar, with several buttons in it. Just underneath the - title bar is a series of menus in the menu - bar, and below that, the tool - bar with buttons for different functions. The largest - part of the main window is taken up by the - actual Inbox, where messages are listed - and displayed. If you're running the program for the first time, - you'll have just one message: a welcome from Helix Code. - - - -
- Evolution Main Window and Inbox - - Evolution Main Window - - - -
- - - - - - The Way Evolution Looks - - The appearance of both Evolution - and GNOME is very easy to - customize, so your screen might not look like this picture. - You might configure Evolution to - start with a different view, without the shortcut - bar, or with the folder bar - instead. - - - - - - The Shortcut Bar - - Evolution's most important job is - to give you access to your information and help you use it - quickly. One way it does that is through the - shortcut bar, the column on the left - hand side of the main window. The large buttons with names - like Inbox and - Contacts are the shortcuts, and you can - select different groups of shortcuts by clicking the - rectangular category buttons. - - - The category buttons are Evolution - Shortcuts and Internet - Directories. When you click on them, they'll slide - up and down to give you access to different sorts of shortcuts. - When you first start Evolution, you - are looking at the Evolution Shortcuts - category. If you click Internet - Directories, it will slide up and you'll see buttons - for the Bigfoot and - Netcenter directories, as well as any - others you or your system administrator might have added. - Internet directories behave a lot like the local contact - manager, which is covered in . - - - Take a look at the Evolution Shortcuts - again. They are: - - - - - - - Inbox: - - - The Inbox will show you all of your email. Your Inbox - is also where you can access Evolution's tools to - filter, sort, organize, and search your mail. - - - - - - Calendar: - - - The Calendar can store your appointments and To do lists - for you. Connected to a network, you can use it to keep - a group of people on schedule and up to date. - - - - - - Contacts: - - - The Contact Manager holds your addresses, phone numbers, - and contact information. Like calendar information, - contact data can be synchronized with hand-held devices - and shared over a network. - - - - - - - Notes: - - The note pad is your catch-all tool: use it to take - messages from phone conversations, keep small things - organized, write haiku, or whatever - you like. This feature is not yet implemented, but will be - soon. See for more - information. - - - - - - - If you prefer to use a keyboard shortcut, or hot - key, you can use those instead. They're shown next - to their equivalent menu items in the menu bar. You can also set - your own hot keys for functions that don't have any; this is - covered in . If you're using the - keyboard shortcuts you may also want to hide the - shortcut bar by selecting - View Show Shortcut - Bar . - - - - Two Shortcut Bar Tricks - - To remove a shortcut from the shortcut bar, right-click on it - and select Remove. - - To change the way the shortcut bar looks, right-click in an - empoy space on the shortcut bar. From the menu that appears, - you can select icon sizes. - - - - - - The Folder Bar - - The folder bar is a more comprehensive - way to view the information you've stored with - Evolution. It displays all your - appointments, address cards, and email in a tree that's a lot - like a file tree— it starts small - at the top, and branches downwards. On most computers, there - will be three folders at the base. The first one is - VFolders, for virtual folders (discussed in - . The next one is - External Directories, for contact - directories stored on a network. The most important one is - probably Local, which you can use to access - all the data that's stored on your computer. If you click on - the plus sign plus sign next to the Local - folder, you'll see the contents: - - - - Calendar, for appointments and - event listings. - - - - - Contacts, for address cards. - - - - - Directories, for Internet contact directories. - - - - - Inbox, for incoming mail. - - - - - Outbox, which is for drafts of - messages and mail that's already been sent. - - - - - - - - To create a new folder, select - File New - Folder. You'll be asked where you want to - put it, and what kind of folder it should be. You can choose - from three types: Mail, for storing mail, - Calendar for storing calendars, and - Contacts for storing contacts. - - - - Folders Have Limits - - You can always place a folder inside other folders, - regardless of folder type. However, calendars, - contacts, and mail can't go into the same - folder. Calendars have to go in calendar folders, mail - in mail folders, and contacts in contact folders. - - - - - Right-clicking will bring up a menu for just about anything - in GNOME, and Evolution is no - exception. If you right-click on a folder, you'll have a - menu with the following options: - - View, to view a message. - Something else, for another purpose. - Something else, for another purpose. - . - - - - Context-Sensitive Help - - GNOME 2.0 supports context-sensitive help, which means you can - almost always get help on an item by right-clicking it. If - you're not sure what something is, or don't know what you can - do with it, choosing Help from the - right-click menu is a good way to find out. - - - - - Any time new information arrives in a folder, that folder label - is displayed as bold text. - - - To delete a folder, right-click it and select - Delete from the menu that pops up. - To change the order of folders, or put one inside another, use - drag-and-drop. To move individual - messages, appointments, and address cards between folders, you - can do the same thing: drag them where you want them, and - they'll go. - - - - The Menu Bar - - The menu bar's contents will always - provide all the possible actions for any given view of your - data. That means that, depending on the context, menu bar items - will change. If you're looking at your Inbox, most of the menu - items will relate to mail; some will relate to other components - of Evolution and some, especially - those in the File Menu will relate to the - application as a whole. This section describes those items that - cover the application as a whole; items specific to mailer are - discussed in the mail chapter, calendar items in the calendar - chapter, and so forth. - - - - - File Menu - - - Anything related to a file falls under this - menu: - - - New... — If you - want to create a new folder, calendar, - appointment, address card, or message, this is - where you should look. - - - - Go to Folder — - Select this item, then choose which folder you'd - like to view. - - - Exit — Quits the application. - - - - Print... — Opens the printing - dialog box so you can print items from the view pane of - Evolution. - - - - - - - Edit Menu - - Although it doesn't contain anything at first, - the Edit menu fills up with - useful editing tools when you're... editing. - - - - - Tools Menu - All of your assistants and configuration - tools go here. For the Inbox, that - means things like Mail - Configuration and the vFolder - Editor. For the - Calendar and the Contact - Manager - - - - Actions Menu - - This menu contains a list of actions you can perform on - the information you've stored with - Evolution. The contents vary - depending on the view, but for the - Inbox, it contains items like - Mark All Messages Read and - Expunge, to erase all the - messages you've marked for deletion. - - - - - Help Menu - - Select among these items to open the - Help Browser to the appropriate section. - - - - - - Once you've familiarized yourself with the main - window you can start doing things with it. We'lql - start with your email inbox: you've got a letter waiting for you - already. - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/doc/C/usage-notes.sgml b/doc/C/usage-notes.sgml deleted file mode 100644 index a4161da810..0000000000 --- a/doc/C/usage-notes.sgml +++ /dev/null @@ -1,41 +0,0 @@ - - Evolution Notes - - An Overview of the Evolution Notes - - In the dark ages before email was invented, there were notes. - Even now, notes are an almost necessary part of our lives. It - only makes sense that Evolution has - a Notes feature. Evolution can help - you take notes in the following ways: - - - - You can take down phone numbers, take school notes, take phone - messages, or even write poetry. - - - - - You can color code each note to help cateogrize each note into - a topic. - - - - - Something - - - - - Something - - - - - - You can start writing notes by clicking Notes in the - shortcut bar. - - - diff --git a/doc/C/usage-sync.sgml b/doc/C/usage-sync.sgml deleted file mode 100644 index 07325e1848..0000000000 --- a/doc/C/usage-sync.sgml +++ /dev/null @@ -1,22 +0,0 @@ - - - Synchronizing with a Hand-held Device - - Once you've set up a synchronization system, it pretty much - takes care of itself. Not only that, it's entirely possible - that your system administrator has set it up for you. All - that this chapter covers is how to use that system once it's - installed and configured. If you need to set it up, consult - . - - - - If you've already got Gnome-pilot set up to use - Evolution, put - your hand-held device on the cradle and press the HotSync - button. - - - No, really. That's all there is to it. - - \ No newline at end of file diff --git a/doc/Camel-Classes b/doc/Camel-Classes deleted file mode 100644 index 93aec087dd..0000000000 --- a/doc/Camel-Classes +++ /dev/null @@ -1,35 +0,0 @@ -CamelException -CamelProvider -CamelThreadProxy -CamelURL -GtkObject - + CamelObject - + CamelAddress - | + CamelInternetAddress - | ` CamelNewsAddress - + CamelDataWrapper - | + CamelMedium - | | ` CamelMimePart - | | ` CamelMimeMessage - | ` CamelMultipart - + CamelFolder - | ` CamelFolderPtProxy - + CamelFolderSearch - + CamelFolderSummary - + CamelMimeFilter - | + CamelMimeFilterBasic - | + CamelMimeFilterCharset - | + CamelMimeFilterIndex - | ` CamelMimeFilterSave - + CamelService - | + CamelStore - | ` CamelTransport - + CamelSession - + CamelStream - | + CamelSeekableStream - | | + CamelSeekableSubstream - | | + CamelStreamFs - | | ` CamelStreamMem - | + CamelStreamBuffer - | ` CamelStreamFilter - ` CamelThreadProxy \ No newline at end of file diff --git a/doc/ChangeLog b/doc/ChangeLog deleted file mode 100644 index 9aedca8af0..0000000000 --- a/doc/ChangeLog +++ /dev/null @@ -1,329 +0,0 @@ -2000-08-09 Aaron Weber - - * C/usage-mainwindow.sgml: Redid menubar description. - - - * C/config-prefs.sgml: Added coverage of folder config, requested - that feature be transferred to config section. Switched to - variablelist in "Other" config section. - - * C/usage-mail.sgml: Added coverage of right-click on messages, - threaded-view. - - * C/usage-mainwindow.sgml: Right-click on folder menu reinstated. - -2000-08-07 Aaron Weber - - * C/config-prefs.sgml: Added news server coverage. Other config - proofing changes. - - -2000-08-05 Aaron Weber - - * C/apx-gpl.sgml: New file. Contains contents of "COPYING", - but marked up (probably not very well, but valid) as docbook - (SGML). - - * C/evolution-guide.sgml: Subtle change to the legal notice: - distinguished manual license from software license. Linked to - apx-gpl.sgml above. - - * C/usage-calendar.sgml: I redid all the usage files. - -2000-07-21 Aaron Weber - - * C/usage-mail.sgml: Added password remembering/forgetting feature. - - * C/config-prefs.sgml: Mostly moved to variablelists, a few - language changes. - - * C/config-setupassist.sgml: Minor changes to formatting, wording. - - * C/usage-notes.sgml: Changed trademark references, other minor - changes. - - * C/usage-calendar.sgml: Minor fixes, added additional calendar - section, removed references to unimplemented features. Spellcheck, - prep for 0.3 release. - -2000-07-19 Aaron Weber - - * C/usage-mail.sgml: lots of minor fixes to language. added - desc. of clahey's cool button-address thing. - - * C/usage-mainwindow.sgml: fixed itemizedlists, ch. to shortcut - bar & folder descs, removed refs to trash. - -2000-07-18 Aaron Weber - - * C/usage-contact.sgml: Altered category addition stuff, plus - suggestions from Kevin. - - * C/apx-gloss.sgml: Added ldap and signature definitions (from - Kevin). - - * C/usage-mail.sgml: Move to variablelists from itemizedlists. - -2000-07-14 Aaron Weber - - * C/usage-contact.sgml: moved to variablelists from itemizedlists - * C/usage-calendar.sgml: moved to variablelists from itemizedlists - -2000-06-29 Aaron Weber - - * C/preface.sgml: Minor fixes. - - * C/usage-notes.sgml: New File for feature that is yet to come. - * C/evolution-guide.sgml: Added entity for notes chapter. - * C/usage-mainwindow.sgml: Un-commented references to notes section. - - * C/apx-authors.sgml: Removed dcm from author list. - - * C/usage-calendar.sgml: Added to-do list features. - -2000-06-28 Aaron Weber - - * C/usage-contact.sgml: commented out future features; redid - contact editor stuff. - - * C/apx-gloss.sgml: Removed "live doc" and added "minicard" - -2000-06-27 Aaron Weber - - * C/devel-action.sgml: Removed file. - * C/devel-script.sgml: Same. - * C/devel-component.sgml: Same. - * C/preface.sgml: Removed references to devel section. - * C/evolution-guide.sgml: Removed references to devel section. - -2000-06-23 Aaron Weber - - * C/evolution-guide.sgml: Made moderate to major stylistic updates - to this, apx-gloss.sgml, and to all files beginning with "usage," - especially wrt HTML mail. - - -<<<<<<< ChangeLog -2000-06-15 Aaron Weber - - * C/usage-contact.sgml: Category stuff improved. - - * C/usage-calendar.sgml: Now covers how to add an event properly. - -======= -======= -======= -2000-07-17 Federico Mena Quintero - - * Makefile.am (SUBDIRS): Added the devel directory. - ->>>>>>> 1.15 -2000-06-28 Peter Williams - - * C/Makefile.am (SGML_FILES): Don't depend on the newly-removed - devel-*.sgml files. - ->>>>>>> 1.13 -2000-06-16 Damon Chaplin - - * C/.cvsignore: added evolution-guide and evolution-guide.junk - so we don't get the '? doc/C/evolution-guide' messages each time we - do a cvs update. - ->>>>>>> 1.12 -2000-06-14 Aaron Weber - - * C/usage-mainwindow.sgml: added sect on menubar, other minor changes. - - * C/usage-mail.sgml: Improved filter and vfolder - description, and some minor changes from me and Kevin. - -2000-06-07 Aaron Weber - - * C/config-prefs.sgml: finished adding calendar prefs. screenshots. - * C/fig/config-cal.png: new file (screenshot for above) - * C/fig/config-mail.png: same - -2000-06-05 Aaron Weber - - * C/usage-calendar.sgml: Incorporated chgs from Kevin. - - * C/config-prefs.sgml: began total overhaul of structure and added - content reflecting new prefs items. needs LOTS more work. - - * C/usage-mail.sgml: changed some references to id's in the - config-prefs section. - - * C/fig/config-mail.png: changed filename from config-prefs.png - -2000-06-01 Aaron Weber - - * C/config-prefs.sgml: filename was wrong, altered. - - * C/usage-mail.sgml: improved filter instructions, vFolder - instructions. still need work though. - - - * C/usage-contact.sgml: added screenshot. - - * C/usage-calendar.sgml: added screenshot. - - * C/config-prefs.sgml: added screenshots, and now describes the - actual prefs dialogs. - - * C/fig/config-camel.png: new (screenshot) file - * C/fig/filter-druid.png: same - * C/fig/vfolder-druid.png: same - * C/fig/calendar.png: same - * C/fig/contact.png: same - * C/fig/vfolder-createrule-fig.png: same - * C/fig/filter-new-fig.png: same - * C/fig/config-camel.png: same - -2000-06-01 Dan Winship - - * Makefile.am: recurse into the C directory - - * C/Makefile.am: Rules to build and install the docs. Mostly - stolen from gnomecal. Only works if you have GDP stuff - (http://www.gnome.org/gdp/) set up on your machine, but won't make - the build fail if you don't. - -2000-05-29 Aaron Weber - - * C/usage-contact.sgml: incorporated kevins notes. - * C/usage-mainwindow.sgml: incorporated kevins notes. - -2000-05-27 Aaron Weber - - * C/evolution-guide.sgml: added Kevin Breit to author and - copyright. - - * C/apx-authors.sgml: Put app authors in a simplelist. - - * C/usage-mail.sgml: Removed USAGE-SETUP insertion, added xref to send - users to config-setupassist chapter. This and the following changes - take setup druid coverage out of usage - section and put it in config section. - * C/config-setupassist.sgml: Added mail druid coverage from - usage-setup.sgml. - * C/usage-setup.sgml: Removed file. contents in - config-setupassist.sgml. - * C/evolution-guide.sgml: Removed - USAGE-SETUP entity (and file usage-setup.sgml.) - - -2000-05-26 Aaron Weber - - * C/fig/mainwindow-pic.png: new file - * C/fig/mail-druid-pic.png: new file - * C/fig: New directory, for figure graphics. - - * C/apx-gloss.sgml: new file. glossary. thx. to kevin from chicago. - - * C/usage-setup.sgml: More accurate description of druid, and - moved to mail section-- see usage-mail.sgml entry. This is a new - location for this entity, and it may move more later. - - - * C/usage-mainwindow.sgml: altered description of starting - evolution. added screenshot for main-window picture. - - * C/usage-mail.sgml: added screenshots, added coverage of setup - druid and put it into get-and-send section, which is probably not - where it should stay. Also started filter druid coverage and - clarified examples, esp. in Bcc: section. - - * C/usage-contact.sgml: Clarified examples. - - * C/preface.sgml: rewording of "what is" and "about book" sections. - - * C/evolution-guide.sgml: added glossary entity APX-GLOSS, altered - phrasing in part intros, changed order of Setup-assistant section. - - * C/config-prefs.sgml: changed wording, removed ref. to re-running - setup assistant. - -2000-05-18 Aaron Weber - - * C/evo_book_0.1.sgml: removed. - - * C/apx-authors.sgml: new file. - * C/apx-bugs.sgml: same. - * C/apx-fdl.sgml: same. - * C/config-prefs.sgml: same. - * C/config-setupassist.sgml: same. - * C/config-sync.sgml: same. - * C/devel-action.sgml: same. - * C/devel-component.sgml: same. - * C/devel-script.sgml: same. - * C/evolution-guide.sgml: same. - * C/preface.sgml: same. - * C/usage-calendar.sgml: same. - * C/usage-contact.sgml: same. - * C/usage-mail.sgml: same. - * C/usage-mainwindow.sgml: same. - * C/usage-setup.sgml: same. - * C/usage-sync.sgml: same. - -2000-05-07 Dan Winship - - * Camel-Classes: sync - -2000-04-16 Aaron Weber - - * C/evo_book_0.1.sgml: new file (doc sgml) - - * C/ : New directory for doc sgml & graphics - -2000-03-05 Christopher James Lahey - - * white-papers/widgets/e-table.sgml: Added Miguel to the author - list for ETable. - -2000-03-03 Christopher James Lahey - - * white-papers/widgets/, white-papers/widgets/e-table.sgml: New - doc for the ETable widget. - - * ChangeLog: Created a ChangeLog file for the docs file and - integrated the individual ChangeLogs. - -2000-03-01 Dan Winship - - * ibex.sgml: Ibex white paper - -2000-02-29 Federico Mena Quintero - - * calendar.sgml: Sections for the calendar user agent and the - calendar client library. - -2000-02-29 Dan Winship - - * camel.sgml: Reorg a bit more, make the 
 section narrower,
-	add more references to graphics (the graphics themselves are
-	still in beta), add a section on CamelStream.
-
-2000-02-28  Federico Mena Quintero  
-
-	* calendar.sgml: Section for the personal calendar server.
-
-2000-02-28  Dan Winship  
-
-	* camel.sgml: add Bertrand to authors, edit his additions
-
-2000-02-28  bertrand  
-
-	* camel.sgml: add a blurb about camel offering
-	uniform interface. needs style and grammar corrections. 
-	Talk about virtual folders.
-	Talk about lightweight messages
-	Talk about IMAP. 
-
-2000-02-28  Dan Winship  
-
-	* camel.sgml: Beginnings of a Camel white paper
-
-2000-02-25  Federico Mena Quintero  
-
-	* calendar.sgml: New file for the Evolution calendaring white paper.
diff --git a/doc/Design b/doc/Design
deleted file mode 100644
index 7b7cf6f821..0000000000
--- a/doc/Design
+++ /dev/null
@@ -1,201 +0,0 @@
-
-The Evolution Project specification
-Miguel de Icaza.
-
-
-* Introduction
-
-	Evolution is a project aiming at providing the free software
-	community with a professional, high-quality tool for managing
-	mail, appointments, tasks and other personal information
-	tools.  
-
-	We want to make Evolution a system that addresses our needs
-	(the free software development community) and we believe that
-	by addressing our needs, we will provide a system that will
-	scale in the years to come for other users that are just
-	starting to use computers and the internet.
-
-	The main objectives of Evolution are to provide these powerful
-	features, and to make the user interface as pretty and
-	polished as possible.
-
-	Evolution is a GNOME application and a number of auxiliary
-	CORBA servers that act as the storage backends. 
-
-	Evolution will copy the best user interface bits and the best
-	ideas and features found on contemporary groupware systems.
-
-* Evolution internals.
-
-	Evolution can store its information locally (files for mail,
-	calendar and address book) or on a remote server (imap/pop,
-	cap, ldap).  
-
-	Given the importance of syncing in this modern PDA world,
-	the Evolution GUI acts as a client to the data repository.
-	The data repository is a GUI-less CORBA server called Wombat.
-
-	Wombat provides a unified access system to the calendar and
-	addressbook data (doing mail is a bit hard, so we are leaving
-	this as a TODO item for now).
-
-	Wombat's CORBA interfaces are notifier-based.  This means that
-	CORBA requests sent to Wombat do not return values
-	inmediately, but rather than for Wombat requests the user has
-	to provide a CORBA object that will be notified of what
-	happened.
-
-	Yes, that sounds hairy.  It is actually pretty simple.  It
-	basically means that you submit requests to Wombat, and a
-	callback is invoked in your code when the request has been
-	carried away. 
-
-	This enables a Palm to sync to the repository without having
-	the GUI for Evolution running.  It also means that volunteers
-	will be able to write text-based and web-based versions of
-	Evolution (not me though :-).
-
-* Evolution as a platform
-
-	Evolution is more than a client for managing the above
-	information: Evolution is a platform for building groupware
-	applications that use the above components to get their work done.
-
-	To achieve this Evolution is designed to be scriptable, and it
-	exports its internals trough CORBA/Bonobo.  It is implemented
-	as a collection of Bonobo containers and Bonobo components.
-
-	There is a clean separation between the views (the user
-	interface) and the model (the view).  The views that we are
-	writing are GNOME based, and they talk to the Wombat CORBA
-	server.
-
-	Wombat takes care of notifications to the various clients for
-	the data. 
-
-* The overall organization
-
-	A bar similar to outlook provides shortcuts for accessing the
-	various resources managed by Evolution: mail folders,
-	contacts, tasks, journal entries, notes, messages and other
-	user-defined destinations. 
-
-* User interface widgets
-
-** The ETable package
-
-	This package provides a way of displaying and editing tables.
-
-	Tables are displayed based on a TableColumn definition that
-	defines the layout used for the display.  Table Columns can be
-	nested, and the package does grouping of information displayed
-	according to the criteria defined there.
-
-	This is used in multiple places troughout evolution: it is
-	used for the Mail summary display, for the TODO display and
-	TODO new data entry and for the address book.
-
-	Nesting in the address book can be performed on various
-	fields.  For example, a first level of nesting could be
-	"Company" and a second level would be "Country" the result is
-	a 2-level tree that can be collapsed expanded and contains the
-	information sorted/grouped by those two criteria.
-
-	The user interface for this will be copied from Outlook: the
-	possibility of adding and removing fields with drag and drop
-	as well as grouping using drag and drop.
-
-* The Mail system
-
-** The Mail sources
-
-	The mail system will support 4 sources of mail:
-
-		POP3 (transfer to a local file).
-		IMAP
-		Local mbox format in $MAIL.
-		Local mbox format that have other delivery points.
-
-	On top of that, it will be possible to browse existing mbox
-	archives (and possibly other formats in the future, like
-	Mailbox and Maildir).
-
-** Storing the mail
-
-	Mail that gets incorporated into the system is stored in mbox
-	format, and summary files are provided for quick access to the
-	files.  No modifications to the file on disk is performed (I
-	am not quite sure about this, perhaps we want to add the
-	status flags and some method for adding metadata to the mail).
-
-	Summary files are rebuilt on demand or rebuild if the mbox
-	file and the summary file have got out of sync.
-
-	A Metadata system that will enable us to attach information to
-	a message will have to be designed and implemented (enabling
-	users to add annotations to mails, and special keywords and
-	flags in a per-message fashion).
-
-** Folders
-
-	Michael Zucchi is working on a system that will let users
-	easily define rules for splitting their incoming mail into
-	physical folders.  
-
-	A further refinement to Folders are Virtual Folders.  This
-	basically provides a powerful search and viewing facility for
-	mail.  It works like this: when a mail is "incorporated" into
-	Evolution it is scanned and indexed.
-
-	Then users can enter queries into Evolution that will search
-	the entire database of messages.	
-
-** Virtual folders
-
-	Virtual folders will enable users to read/browse their mail in
-	new ways: by specifying search criterias, these folders will
-	contain messages that match the criteria given.  
-
-	There is more information about this in the libcamel
-	directory. 
-
-	We will index all headers from a message, and possible the
-	contents of messages and keep those on a separate file, to
-	enable users to query their mail database.
-
-** Mail summary display
-
-	The summary will be displayed using the ETable package, to
-	enable users to add a number of sorting criteria and various
-	display methods for the summary view.
-
-	The Outlook methods for displaying will be present on the
-	system.
-
-	Message threading will be supported in Evolution.
-
-** Message display engine
-
-	We are going to be using a combination of
-	libcamel/limime/libjamie to parse messages and render them
-	into an HTML buffer.
-
-* The HTML engine
-
-	The GtkHTML engine will be used to display messages, and will
-	be extended to support a number of features that we require:
-	internal handling of characters will be based on Unicode
-
-* The message composer
-
-	Regular features found in composers will be added: connecting
-	the composer to the address book, support for drag and drop
-	for including attachments, editing the message, archiving
-	drafts and archiving messages sent.
-
-	Ettore has been working on adding editing support to the
-	GtkHTML and he is working currently on a Bonobo component that
-	will provide a ready-to-use Bonobo control for embedding into
-	other applications.
-
diff --git a/doc/Makefile.am b/doc/Makefile.am
deleted file mode 100644
index 7b5420fee8..0000000000
--- a/doc/Makefile.am
+++ /dev/null
@@ -1 +0,0 @@
-SUBDIRS = C devel
diff --git a/doc/devel/.cvsignore b/doc/devel/.cvsignore
deleted file mode 100644
index c24a54fbcc..0000000000
--- a/doc/devel/.cvsignore
+++ /dev/null
@@ -1,4 +0,0 @@
-Makefile
-Makefile.in
-html
-evolution-devel-guide.html
diff --git a/doc/devel/ChangeLog b/doc/devel/ChangeLog
deleted file mode 100644
index 7e0c8147ba..0000000000
--- a/doc/devel/ChangeLog
+++ /dev/null
@@ -1,35 +0,0 @@
-2000-08-14  Federico Mena Quintero  
-
-	* calendar/cal-util/*: Integrated the cal-util library into the
-	documentation framework.
-
-	* calendar/Makefile.am (SUBDIRS): Added the cal-util directory.
-
-	* evolution-devel-guide.sgml: Added entities for the cal-util stuff.
-	Added entity for libical.
-
-	* calendar/reference.sgml: Added the cal-util reference entries.
-
-	* calendar/cal-client/evolution-cal-client-sections.txt: Updated
-	for new API.
-
-2000-08-09  Peter Williams  
-
-	* Makefile.am (maintainer-clean-local): Don't depend
-	on 'clean'; this messes up maintainer-clean.
-
-2000-07-17  Federico Mena Quintero  
-
-	* calendar/cal-client/tmpl/cal-client.sgml: Populated.
-
-	* evolution-devel-guide.sgml: New  toplevel for the
-	Evolution Developer's Guide.
-
-	* calendar/evolution-calendar.sgml: New  for the calendar
-	developer's documentation.
-
-	* calendar/architecture.sgml: New  for the calendar
-	architecture.
-
-	* calendar/reference.sgml: New  for the calendar API
-	reference.
diff --git a/doc/devel/Makefile.am b/doc/devel/Makefile.am
deleted file mode 100644
index 0d3cec5a1c..0000000000
--- a/doc/devel/Makefile.am
+++ /dev/null
@@ -1,64 +0,0 @@
-SUBDIRS = calendar
-
-# The name of the module.
-DOC_MODULE=evolution-devel-guide
-
-# The top-level SGML file.
-DOC_MAIN_SGML_FILE=evolution-devel-guide.sgml
-
-HTML_DIR=$(datadir)/gnome/html
-
-TARGET_DIR=$(HTML_DIR)/$(DOC_MODULE)
-
-evolution_devel_guidedir = $(HTML_DIR)
-evolution_devel_guide_DATA =			\
-	evolution-devel-guide.html
-
-content_files =					\
-	evolution-devel-guide.sgml
-
-EXTRA_DIST = 					\
-	$(evolution_devel_guide_DATA)		\
-	$(content_files)
-
-if ENABLE_GTK_DOC
-evolution-devel-guide.html: html/book1.html
-	-cd $(srcdir) && cp html/book1.html evolution-devel-guide.html
-else
-evolution-devel-guide.html:
-endif
-
-html/book1.html: $(content-files)
-	$(MAKE) html
-
-html:
-	test -d $(srcdir)/html || mkdir $(srcdir)/html
-	-cd $(srcdir)/html && gtkdoc-mkhtml $(DOC_MODULE) ../$(DOC_MAIN_SGML_FILE)
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local:
-	cd $(srcdir) && rm -rf html
-
-install-data-local:
-	$(mkinstalldirs) $(DESTDIR)$(TARGET_DIR)
-	(installfiles=`echo $(srcdir)/html/*.html`; \
-	if test "$$installfiles" = '$(srcdir)/html/*.html'; \
-	then echo '-- Nothing to install' ; \
-	else \
-	  for i in $$installfiles; do \
-	    echo '-- Installing '$$i ; \
-	    $(INSTALL_DATA) $$i $(DESTDIR)$(TARGET_DIR); \
-	  done; \
-	  echo '-- Installing $(srcdir)/html/index.sgml' ; \
-	  $(INSTALL_DATA) $(srcdir)/html/index.sgml $(DESTDIR)$(TARGET_DIR); \
-	  echo '-- Fixing Crossreferences' ; \
-	  gtkdoc-fixxref --module=$(DOC_MODULE) --html-dir=$(HTML_DIR)|| true; \
-	fi)
-
-dist-hook:
-	mkdir $(distdir)/html
-	-cp $(srcdir)/html/*.html $(srcdir)/html/*.css $(distdir)/html
-
-.PHONY: html
diff --git a/doc/devel/calendar/.cvsignore b/doc/devel/calendar/.cvsignore
deleted file mode 100644
index 282522db03..0000000000
--- a/doc/devel/calendar/.cvsignore
+++ /dev/null
@@ -1,2 +0,0 @@
-Makefile
-Makefile.in
diff --git a/doc/devel/calendar/Makefile.am b/doc/devel/calendar/Makefile.am
deleted file mode 100644
index 2220e1d59b..0000000000
--- a/doc/devel/calendar/Makefile.am
+++ /dev/null
@@ -1,6 +0,0 @@
-SUBDIRS = cal-client cal-util
-
-EXTRA_DIST =				\
-	architecture.sgml		\
-	evolution-calendar.sgml		\
-	reference.sgml
diff --git a/doc/devel/calendar/architecture.sgml b/doc/devel/calendar/architecture.sgml
deleted file mode 100644
index 08e4c82b35..0000000000
--- a/doc/devel/calendar/architecture.sgml
+++ /dev/null
@@ -1,94 +0,0 @@
-  
-    Architecture of the Calendar
-
-    
-      This chapter gives an overview of the Evolution Calendar
-      architecture.  It describes the model/view split of the calendar
-      into a personal calendar server, or PCS, and the GUI clients
-      that appear inside the Evolution shell.
-    
-
-    
-
-    
-      Model/View Separation
-
-      
-	Like other base components in Evolution, the calendar
-	separates the data model from the views or clients.  This is
-	done so that multiple clients can access the same calendar
-	data in an orderly fashion and without clashes.  For example,
-	the user may be running a graphical calendar client.  If he
-	then wants to synchronize his calendar with a handheld device,
-	then the corresponding synchronization program (e.g. a conduit
-	for the gnome-pilot package) will
-	also need to access the calendar storage.  It is important
-	that both the GUI client and the synchronization program keep
-	a consistent view of the calendar at all times, otherwise one
-	of them will be left in an inconsistent state if the
-	calendar's data changes unexpectedly.
-      
-
-      
-	Evolution puts the calendar storage in a daemon called the
-	Wombat and completely separates it from clients who wants to
-	access calendar data.  This part of the Wombat is called the
-	personal calendar server, or &PCS;.  Clients must contact the
-	&PCS; and ask it to open an existing calendar or create a new
-	one.  When a calendar component object (e.g. an appointment or
-	to-do item) changes in the &PCS; it will notify all the
-	clients that are using the component's parent calendar.
-      
-    
-
-    
-
-    
-      Personal Calendar Server
-
-      
-	The personal calendar server, or &PCS;, provides centralized
-	management and storage of a user's personal calendar.
-	Multiple clients can connect to the &PCS; simultaneously to
-	query and modify the user's calendar in a synchronized
-	fashion.  The main features of the &PCS; are as follows:
-      
-
-      
-	Storage
-
-	
-	  The &PCS; is responsible for loading and saving calendars.
-	  Centralizing the loading and saving functionality allows
-	  multiple clients to use the same calendar at the same time
-	  without having to worry about each other.
-	
-      
-
-      
-	Basic Queries
-
-	
-	  The &PCS; provides functions to do basic queries on a
-	  calendar, for example, a client can ask the server for a
-	  list of all the appointments in the calendar, or for all the
-	  data for a specific appointment.
-	
-      
-
-      
-	Recurrence and Alarm Queries
-
-	
-	  
-	
-      
-    
-  
-
-
diff --git a/doc/devel/calendar/cal-client/.cvsignore b/doc/devel/calendar/cal-client/.cvsignore
deleted file mode 100644
index 0842a93f7a..0000000000
--- a/doc/devel/calendar/cal-client/.cvsignore
+++ /dev/null
@@ -1,3 +0,0 @@
-sgml
-Makefile
-Makefile.in
diff --git a/doc/devel/calendar/cal-client/Makefile.am b/doc/devel/calendar/cal-client/Makefile.am
deleted file mode 100644
index 44d43639a8..0000000000
--- a/doc/devel/calendar/cal-client/Makefile.am
+++ /dev/null
@@ -1,76 +0,0 @@
-## Process this file with automake to produce Makefile.in
-
-# The name of the module.
-DOC_MODULE=evolution-cal-client
-
-# The top-level SGML file.
-DOC_MAIN_SGML_FILE=evolution-cal-client.sgml
-
-# The directory containing the source code (if it contains documentation).
-DOC_SOURCE_DIR=$(EVOLUTION_DIR)/calendar/cal-client
-
-CFLAGS ="						\
-	-I$(top_srcdir)/calendar			\
-	-I$(top_srcdir)					\
-	-I$(top_builddir)				\
-	-I$(top_builddir)/libical/src/libical		\
-	-I$(top_srcdir)/libical/src/libical		\
-	$(BONOBO_VFS_GNOME_CFLAGS)			\
-	"
-
-LDFLAGS="								\
-	$(BONOBO_VFS_GNOME_LIBS)					\
-	$(top_builddir)/calendar/cal-client/.libs/libcal-client.a	\
-	$(top_builddir)/calendar/cal-util/.libs/libcal-util.a		\
-	$(top_builddir)/libical/src/libical/libical.a			\
-	$(top_builddir)/libversit/.libs/libversit.al			\
-	"
-
-HTML_DIR=$(datadir)/gnome/html
-
-TARGET_DIR=$(HTML_DIR)/$(DOC_MODULE)
-
-tmpl_sources =					\
-	tmpl/cal-client.sgml			\
-	tmpl/evolution-cal-client-unused.sgml
-
-evolution_cal_client_docdir = $(HTML_DIR)
-evolution_cal_client_doc_DATA =			\
-	evolution-cal-client.hierarchy		\
-	evolution-cal-client.types		\
-	evolution-cal-client-decl.txt		\
-	evolution-cal-client-sections.txt
-
-EXTRA_DIST = 					\
-	$(evolution_cal_client_doc_DATA)
-
-sgml/evolution-cal-client-doc.bottom: $(tmpl_sources)
-	$(MAKE) sgml
-
-scan:
-	-(cd $(srcdir) \
-	&& env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS) \
-		 gtkdoc-scanobj --module=$(DOC_MODULE) \
-	&& gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) --ignore-headers="cal-listener.h evolution-calendar.h" )
-
-templates: scan
-	cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE)
-
-sgml:
-	cd $(srcdir) \
-	&& gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local: clean
-	cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt
-
-dist-hook:
-	mkdir $(distdir)/sgml
-	mkdir $(distdir)/tmpl
-	-cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl
-	-cp $(srcdir)/sgml/*.sgml $(distdir)/sgml
-	-cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml
-
-.PHONY : sgml templates scan
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client-decl.txt b/doc/devel/calendar/cal-client/evolution-cal-client-decl.txt
deleted file mode 100644
index 0574d70678..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client-decl.txt
+++ /dev/null
@@ -1,132 +0,0 @@
-
-CAL_CLIENT_TYPE
-#define CAL_CLIENT_TYPE            (cal_client_get_type ())
-
-
-CAL_CLIENT
-#define CAL_CLIENT(obj)            (GTK_CHECK_CAST ((obj), CAL_CLIENT_TYPE, CalClient))
-
-
-CAL_CLIENT_CLASS
-#define CAL_CLIENT_CLASS(klass)    (GTK_CHECK_CLASS_CAST ((klass), CAL_CLIENT_TYPE, CalClientClass))
-
-
-IS_CAL_CLIENT
-#define IS_CAL_CLIENT(obj)         (GTK_CHECK_TYPE ((obj), CAL_CLIENT_TYPE))
-
-
-IS_CAL_CLIENT_CLASS
-#define IS_CAL_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((klass), CAL_CLIENT_TYPE))
-
-
-CalClient
-
-
-CalClientClass
-
-
-CalClientLoadStatus
-typedef enum {
-	CAL_CLIENT_LOAD_SUCCESS,
-	CAL_CLIENT_LOAD_ERROR,
-	CAL_CLIENT_LOAD_IN_USE,
-	CAL_CLIENT_LOAD_METHOD_NOT_SUPPORTED
-} CalClientLoadStatus;
-
-
-CalClientGetStatus
-typedef enum {
-	CAL_CLIENT_GET_SUCCESS,
-	CAL_CLIENT_GET_NOT_FOUND,
-	CAL_CLIENT_GET_SYNTAX_ERROR
-} CalClientGetStatus;
-
-
-CalClient
-struct CalClient {
-	GtkObject object;
-
-	/* Private data */
-	gpointer priv;
-};
-
-
-cal_client_get_type
-GtkType  
-void
-
-
-cal_client_construct
-CalClient  *
-CalClient *client
-
-
-cal_client_new
-CalClient  *
-void
-
-
-cal_client_load_calendar
-gboolean  
-CalClient *client, const char *str_uri
-
-
-cal_client_create_calendar
-gboolean  
-CalClient *client, const char *str_uri
-
-
-cal_client_get_n_objects
-int  
-CalClient *client, CalObjType type
-
-
-cal_client_get_object
-CalClientGetStatus  
-CalClient *client,const char *uid,CalComponent **comp
-
-
-cal_client_get_uid_by_pilot_id
-CalClientGetStatus  
-CalClient *client,unsigned long pilot_id,char **uid
-
-
-cal_client_update_pilot_id
-void  
-CalClient *client, char *uid,unsigned long pilot_id,unsigned long pilot_status
-
-
-cal_client_get_uids
-GList  *
-CalClient *client, CalObjType type
-
-
-cal_client_get_objects_in_range
-GList  *
-CalClient *client, CalObjType type,time_t start, time_t end
-
-
-cal_client_generate_instances
-void  
-CalClient *client, CalObjType type,time_t start, time_t end,CalRecurInstanceFn cb, gpointer cb_data
-
-
-cal_client_get_alarms_in_range
-GList  *
-CalClient *client, time_t start, time_t end
-
-
-cal_client_get_alarms_for_object
-gboolean  
-CalClient *client, const char *uid,time_t start, time_t end,GList **alarms
-
-
-cal_client_update_object
-gboolean  
-CalClient *client, CalComponent *comp
-
-
-cal_client_remove_object
-gboolean  
-CalClient *client, const char *uid
-
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client-sections.txt b/doc/devel/calendar/cal-client/evolution-cal-client-sections.txt
deleted file mode 100644
index c37b223247..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client-sections.txt
+++ /dev/null
@@ -1,37 +0,0 @@
-cal-client/cal-client.h
-
-

-cal-client
-CAL_CLIENT
-CalClient
-
-CalClientLoadStatus
-CalClientGetStatus
-cal_client_new
-cal_client_load_calendar
-cal_client_create_calendar
-cal_client_get_n_objects
-cal_client_get_object
-cal_client_get_objects_in_range
-cal_client_generate_instances
-cal_client_get_uid_by_pilot_id
-cal_client_update_pilot_id
-cal_client_get_uids
-cal_client_get_alarms_in_range
-cal_client_get_alarms_for_object
-cal_client_update_object
-cal_client_remove_object
-
-
-
-CAL_CLIENT_TYPE
-IS_CAL_CLIENT
-CAL_CLIENT_CLASS
-IS_CAL_CLIENT_CLASS
-cal_client_get_type
-cal_client_construct
-
-
-CalClient
-
-

diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.args b/doc/devel/calendar/cal-client/evolution-cal-client.args
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.hierarchy b/doc/devel/calendar/cal-client/evolution-cal-client.hierarchy
deleted file mode 100644
index 88efa3e673..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client.hierarchy
+++ /dev/null
@@ -1,2 +0,0 @@
-GtkObject
-  CalClient
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.signals b/doc/devel/calendar/cal-client/evolution-cal-client.signals
deleted file mode 100644
index 97e360b6a2..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client.signals
+++ /dev/null
@@ -1,21 +0,0 @@
-
-CalClient::cal-loaded
-void
-CalClient *calclient
-GtkEnum  arg1
-
-
-
-CalClient::obj-updated
-void
-CalClient *calclient
-GtkString  arg1
-
-
-
-CalClient::obj-removed
-void
-CalClient *calclient
-GtkString  arg1
-
-
diff --git a/doc/devel/calendar/cal-client/evolution-cal-client.types b/doc/devel/calendar/cal-client/evolution-cal-client.types
deleted file mode 100644
index 84d65a6637..0000000000
--- a/doc/devel/calendar/cal-client/evolution-cal-client.types
+++ /dev/null
@@ -1,4 +0,0 @@
-#include 
-#include 
-
-cal_client_get_type
diff --git a/doc/devel/calendar/cal-client/tmpl/cal-client.sgml b/doc/devel/calendar/cal-client/tmpl/cal-client.sgml
deleted file mode 100644
index a146709b8a..0000000000
--- a/doc/devel/calendar/cal-client/tmpl/cal-client.sgml
+++ /dev/null
@@ -1,291 +0,0 @@
-
-CalClient
-
-
-GTK+ object for communication with personal calendar server.
-
-
-  
-    The #CalClient object provides a nice GTK+ wrapper for the CORBA
-    interfaces that are used to communicate between calendar clients
-    and the personal calendar server in the user's Wombat daemon.
-  
-
-  
-    After a #CalClient object is created with cal_client_new(), it
-    should be asked to send a request to the personal calendar server
-    to load or create a calendar based on its URI.  The server will
-    asynchronously notify the client about completion of the request,
-    and will return an appropriate result code; this should be noted
-    by the client with the cal_loaded signal.
-  
-
-  
-    When a client asks the server to update or delete a calendar
-    component from the storage, the server will do so and then notify
-    all the clients about the update or removal.  This is the core of
-    the model/view split between calendar clients and the storage in
-    the personal calendar server.  Clients should watch the obj_updated and obj_removed signals on the
-    CalClient objects they create so that they can be notified about
-    changes in the storage.
-  
-
-
-  
-
-  
-
-
-  
-    Casts a #GtkObject to a #CalClient.
-  
-
-@obj: A GTK+ object.
-
-
-
-  
-    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.
-  
-
-@CAL_CLIENT_LOAD_SUCCESS: Indicates a successful load or create
-  operation; the corresponding calendar is ready for use.
-@CAL_CLIENT_LOAD_ERROR: Indicates an error while loading or creating
-  the calendar.
-@CAL_CLIENT_LOAD_IN_USE: Indicates that a create request failed
-  because the specified calendar was already being used by another
-  client.
-@CAL_CLIENT_LOAD_METHOD_NOT_SUPPORTED: Indicates an error due to
-  trying to load a calendar for which a backend type is not present.
-
-
-  
-    These values describe the result of the cal_client_get_object()
-    function.
-  
-
-@CAL_CLIENT_GET_SUCCESS: Indicates a successful get operation.
-@CAL_CLIENT_GET_NOT_FOUND: Indicates that the requested object was
-  not found.
-@CAL_CLIENT_GET_SYNTAX_ERROR: Indicates a syntax error when parsing
-  the requested object.  This could indicate a bug in the calendar
-  client libraries or in the Wombat server.
-
-
-
-
-
-
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@str_uri: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@str_uri: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@uid: 
-@comp: 
-@Returns: 
-
-@ico: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@start: 
-@end: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@start: 
-@end: 
-@cb: 
-@cb_data: 
-
-
-
-
-
-
-
-@client: 
-@pilot_id: 
-@uid: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@uid: 
-@pilot_id: 
-@pilot_status: 
-
-
-
-
-
-
-
-@client: 
-@type: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@start: 
-@end: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@uid: 
-@start: 
-@end: 
-@alarms: 
-@Returns: 
-
-
-
-
-
-
-
-@client: 
-@comp: 
-@Returns: 
-
-@ico: 
-
-
-
-
-
-
-
-@client: 
-@uid: 
-@Returns: 
-
-
-
-  
-    This signal is emitted some time after the calendar clients sends
-    a load or create request to the personal calendar server.  The
-    server will notify the client asynchronously of the completion of
-    the request.  The @status parameter indicates the status of the
-    request.
-  
-
-@calclient: the object which received the signal.
-@arg1: 
-
-@client: Calendar client which received the notification.
-@status: Status of the request.  See the description of
-  #CalClientLoadStatus for more details.
-
-
-  
-    This signal is emitted when the calendar clients receives
-    notification of a calendar component's data being changed in the
-    personal calendar server.  Graphical clients may want to get the
-    new version of the object and update their display, for example.
-  
-
-@calclient: the object which received the signal.
-@arg1: 
-
-@client: Calendar client which received the notification.
-@uid: Unique identifier of the calendar component that changed in the
-  personal calendar server's storage.
-
-
-  
-    This signal is emitted when the calendar client receives
-    notification for a calendar component being removed from the
-    storage in the personal calendar server.  Graphical clients may
-    want to delete the corresponding object from their display, for
-    example.
-  
-
-@calclient: the object which received the signal.
-@arg1: 
-
-@client: Calendar client which received the notification.
-@uid: Unique identifier of the calendar component that was removed
-  from the personal calendar server's storage.
-
-
-
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
deleted file mode 100644
index 5576dbd57f..0000000000
--- a/doc/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-
-
-
-@client: 
-@start: 
-@end: 
-@Returns: 
-
diff --git a/doc/devel/calendar/cal-util/.cvsignore b/doc/devel/calendar/cal-util/.cvsignore
deleted file mode 100644
index 0842a93f7a..0000000000
--- a/doc/devel/calendar/cal-util/.cvsignore
+++ /dev/null
@@ -1,3 +0,0 @@
-sgml
-Makefile
-Makefile.in
diff --git a/doc/devel/calendar/cal-util/Makefile.am b/doc/devel/calendar/cal-util/Makefile.am
deleted file mode 100644
index 8861aa03cb..0000000000
--- a/doc/devel/calendar/cal-util/Makefile.am
+++ /dev/null
@@ -1,75 +0,0 @@
-## Process this file with automake to produce Makefile.in
-
-# The name of the module.
-DOC_MODULE=evolution-cal-util
-
-# The top-level SGML file.
-DOC_MAIN_SGML_FILE=evolution-cal-util.sgml
-
-# The directory containing the source code (if it contains documentation).
-DOC_SOURCE_DIR=$(EVOLUTION_DIR)/calendar/cal-util
-
-CFLAGS ="						\
-	-I$(top_srcdir)/calendar			\
-	-I$(top_srcdir)					\
-	-I$(top_builddir)				\
-	-I$(top_builddir)/libical/src/libical		\
-	-I$(top_srcdir)/libical/src/libical		\
-	$(BONOBO_VFS_GNOME_CFLAGS)			\
-	"
-
-LDFLAGS="								\
-	$(BONOBO_VFS_GNOME_LIBS)					\
-	$(top_builddir)/calendar/cal-util/.libs/libcal-util.a		\
-	$(top_builddir)/libical/src/libical/libical.a			\
-	$(top_builddir)/libversit/.libs/libversit.al			\
-	"
-
-HTML_DIR=$(datadir)/gnome/html
-
-TARGET_DIR=$(HTML_DIR)/$(DOC_MODULE)
-
-tmpl_sources =					\
-	tmpl/cal-util.sgml			\
-	tmpl/evolution-cal-util-unused.sgml
-
-evolution_cal_util_docdir = $(HTML_DIR)
-evolution_cal_util_doc_DATA =			\
-	evolution-cal-util.hierarchy		\
-	evolution-cal-util.types		\
-	evolution-cal-util-decl.txt		\
-	evolution-cal-util-sections.txt
-
-EXTRA_DIST = 					\
-	$(evolution_cal_util_doc_DATA)
-
-sgml/evolution-cal-util-doc.bottom: $(tmpl_sources)
-	$(MAKE) sgml
-
-scan:
-	-(cd $(srcdir) \
-	&& env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS) \
-		 gtkdoc-scanobj --module=$(DOC_MODULE) \
-	&& gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) --ignore-headers="calobj.h icalendar-save.h icalendar.h" )
-
-templates: scan
-	cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE)
-
-sgml:
-	cd $(srcdir) \
-	&& gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR)
-
-clean-local:
-	rm -f *~ *.bak *.signals *-unused.txt
-
-maintainer-clean-local: clean
-	cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt
-
-dist-hook:
-	mkdir $(distdir)/sgml
-	mkdir $(distdir)/tmpl
-	-cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl
-	-cp $(srcdir)/sgml/*.sgml $(distdir)/sgml
-	-cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml
-
-.PHONY : sgml templates scan
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util-decl.txt b/doc/devel/calendar/cal-util/evolution-cal-util-decl.txt
deleted file mode 100644
index eb108b868f..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util-decl.txt
+++ /dev/null
@@ -1,852 +0,0 @@
-
-CAL_COMPONENT_TYPE
-#define CAL_COMPONENT_TYPE            (cal_component_get_type ())
-
-
-CAL_COMPONENT
-#define CAL_COMPONENT(obj)            (GTK_CHECK_CAST ((obj), CAL_COMPONENT_TYPE, CalComponent))
-
-
-CAL_COMPONENT_CLASS
-#define CAL_COMPONENT_CLASS(klass)    (GTK_CHECK_CLASS_CAST ((klass), CAL_COMPONENT_TYPE,	\
-				       CalComponentClass))
-
-
-IS_CAL_COMPONENT
-#define IS_CAL_COMPONENT(obj)         (GTK_CHECK_TYPE ((obj), CAL_COMPONENT_TYPE))
-
-
-IS_CAL_COMPONENT_CLASS
-#define IS_CAL_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((klass), CAL_COMPONENT_TYPE))
-
-
-CalComponentVType
-typedef enum {
-	CAL_COMPONENT_NO_TYPE,
-	CAL_COMPONENT_EVENT,
-	CAL_COMPONENT_TODO,
-	CAL_COMPONENT_JOURNAL,
-	CAL_COMPONENT_FREEBUSY,
-	CAL_COMPONENT_TIMEZONE
-} CalComponentVType;
-
-
-CalComponentField
-typedef enum {
-	CAL_COMPONENT_FIELD_CATEGORIES,		/* concatenation of the categories list */
-	CAL_COMPONENT_FIELD_CLASSIFICATION,
-	CAL_COMPONENT_FIELD_COMPLETED,
-	CAL_COMPONENT_FIELD_DTEND,
-	CAL_COMPONENT_FIELD_DTSTART,
-	CAL_COMPONENT_FIELD_DUE,
-	CAL_COMPONENT_FIELD_GEO,
-	CAL_COMPONENT_FIELD_PERCENT,
-	CAL_COMPONENT_FIELD_PRIORITY,
-	CAL_COMPONENT_FIELD_SUMMARY,
-	CAL_COMPONENT_FIELD_TRANSPARENCY,
-	CAL_COMPONENT_FIELD_URL,
-	CAL_COMPONENT_FIELD_HAS_ALARMS,		/* not a real field */
-	CAL_COMPONENT_FIELD_ICON,		/* not a real field */
-	CAL_COMPONENT_FIELD_COMPLETE,		/* not a real field */
-	CAL_COMPONENT_FIELD_RECURRING,		/* not a real field */
-	CAL_COMPONENT_FIELD_OVERDUE,		/* not a real field */
-	CAL_COMPONENT_FIELD_COLOR,		/* not a real field */
-	CAL_COMPONENT_FIELD_NUM_FIELDS
-} CalComponentField;
-
-
-CalComponentClassification
-typedef enum {
-	CAL_COMPONENT_CLASS_NONE,
-	CAL_COMPONENT_CLASS_PUBLIC,
-	CAL_COMPONENT_CLASS_PRIVATE,
-	CAL_COMPONENT_CLASS_CONFIDENTIAL,
-	CAL_COMPONENT_CLASS_UNKNOWN
-} CalComponentClassification;
-
-
-CalComponentDateTime
-typedef struct {
-	/* Actual date/time value */
-	struct icaltimetype *value;
-
-	/* Timezone ID */
-	const char *tzid;
-} CalComponentDateTime;
-
-
-CalComponentPeriodType
-typedef enum {
-	CAL_COMPONENT_PERIOD_DATETIME,
-	CAL_COMPONENT_PERIOD_DURATION
-} CalComponentPeriodType;
-
-
-CalComponentPeriod
-typedef struct {
-	CalComponentPeriodType type;
-
-	struct icaltimetype start;
-
-	union {
-		struct icaltimetype end;
-		struct icaldurationtype duration;
-	} u;
-} CalComponentPeriod;
-
-
-CalComponentText
-typedef struct {
-	/* Description string */
-	const char *value;
-
-	/* Alternate representation URI */
-	const char *altrep;
-} CalComponentText;
-
-
-CalComponentTransparency
-typedef enum {
-	CAL_COMPONENT_TRANSP_NONE,
-	CAL_COMPONENT_TRANSP_TRANSPARENT,
-	CAL_COMPONENT_TRANSP_OPAQUE,
-	CAL_COMPONENT_TRANSP_UNKNOWN
-} CalComponentTransparency;
-
-
-CalComponentAlarm
-
-
-CalComponent
-
-
-CalComponentClass
-
-
-CalComponentPrivate
-
-
-CalComponent
-struct CalComponent {
-	GtkObject object;
-
-	/* Private data */
-	CalComponentPrivate *priv;
-};
-
-
-cal_component_get_type
-GtkType  
-void
-
-
-cal_component_gen_uid
-char  *
-void
-
-
-cal_component_new
-CalComponent  *
-void
-
-
-cal_component_clone
-CalComponent  *
-CalComponent *comp
-
-
-cal_component_set_new_vtype
-void  
-CalComponent *comp, CalComponentVType type
-
-
-cal_component_set_icalcomponent
-gboolean  
-CalComponent *comp, icalcomponent *icalcomp
-
-
-cal_component_get_icalcomponent
-icalcomponent  *
-CalComponent *comp
-
-
-cal_component_get_vtype
-CalComponentVType  
-CalComponent *comp
-
-
-cal_component_get_as_string
-char  *
-CalComponent *comp
-
-
-cal_component_commit_sequence
-void  
-CalComponent *comp
-
-
-cal_component_get_uid
-void  
-CalComponent *comp, const char **uid
-
-
-cal_component_set_uid
-void  
-CalComponent *comp, const char *uid
-
-
-cal_component_get_categories_list
-void  
-CalComponent *comp, GSList **categ_list
-
-
-cal_component_set_categories_list
-void  
-CalComponent *comp, GSList *categ_list
-
-
-cal_component_get_classification
-void  
-CalComponent *comp, CalComponentClassification *classif
-
-
-cal_component_set_classification
-void  
-CalComponent *comp, CalComponentClassification classif
-
-
-cal_component_get_comment_list
-void  
-CalComponent *comp, GSList **text_list
-
-
-cal_component_set_comment_list
-void  
-CalComponent *comp, GSList *text_list
-
-
-cal_component_get_completed
-void  
-CalComponent *comp, struct icaltimetype **t
-
-
-cal_component_set_completed
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_created
-void  
-CalComponent *comp, struct icaltimetype **t
-
-
-cal_component_set_created
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_description_list
-void  
-CalComponent *comp, GSList **text_list
-
-
-cal_component_set_description_list
-void  
-CalComponent *comp, GSList *text_list
-
-
-cal_component_get_dtend
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_set_dtend
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_get_dtstamp
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_set_dtstamp
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_dtstart
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_set_dtstart
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_get_due
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_set_due
-void  
-CalComponent *comp, CalComponentDateTime *dt
-
-
-cal_component_get_exdate_list
-void  
-CalComponent *comp, GSList **exdate_list
-
-
-cal_component_set_exdate_list
-void  
-CalComponent *comp, GSList *exdate_list
-
-
-cal_component_get_exrule_list
-void  
-CalComponent *comp, GSList **recur_list
-
-
-cal_component_set_exrule_list
-void  
-CalComponent *comp, GSList *recur_list
-
-
-cal_component_get_geo
-void  
-CalComponent *comp, struct icalgeotype **geo
-
-
-cal_component_set_geo
-void  
-CalComponent *comp, struct icalgeotype *geo
-
-
-cal_component_get_last_modified
-void  
-CalComponent *comp, struct icaltimetype **t
-
-
-cal_component_set_last_modified
-void  
-CalComponent *comp, struct icaltimetype *t
-
-
-cal_component_get_percent
-void  
-CalComponent *comp, int **percent
-
-
-cal_component_set_percent
-void  
-CalComponent *comp, int *percent
-
-
-cal_component_get_priority
-void  
-CalComponent *comp, int **priority
-
-
-cal_component_set_priority
-void  
-CalComponent *comp, int *priority
-
-
-cal_component_get_rdate_list
-void  
-CalComponent *comp, GSList **period_list
-
-
-cal_component_set_rdate_list
-void  
-CalComponent *comp, GSList *period_list
-
-
-cal_component_has_rdates
-gboolean  
-CalComponent *comp
-
-
-cal_component_get_rrule_list
-void  
-CalComponent *comp, GSList **recur_list
-
-
-cal_component_set_rrule_list
-void  
-CalComponent *comp, GSList *recur_list
-
-
-cal_component_has_rrules
-gboolean  
-CalComponent *comp
-
-
-cal_component_get_sequence
-void  
-CalComponent *comp, int **sequence
-
-
-cal_component_set_sequence
-void  
-CalComponent *comp, int *sequence
-
-
-cal_component_get_summary
-void  
-CalComponent *comp, CalComponentText *summary
-
-
-cal_component_set_summary
-void  
-CalComponent *comp, CalComponentText *summary
-
-
-cal_component_get_transparency
-void  
-CalComponent *comp, CalComponentTransparency *transp
-
-
-cal_component_set_transparency
-void  
-CalComponent *comp, CalComponentTransparency transp
-
-
-cal_component_get_url
-void  
-CalComponent *comp, const char **url
-
-
-cal_component_set_url
-void  
-CalComponent *comp, const char *url
-
-
-cal_component_get_pilot_id
-void  
-CalComponent *comp, unsigned long *pilot_id
-
-
-cal_component_set_pilot_id
-void  
-CalComponent *comp, unsigned long pilot_id
-
-
-cal_component_get_pilot_status
-void  
-CalComponent *comp, unsigned long *pilot_status
-
-
-cal_component_set_pilot_status
-void  
-CalComponent *comp, unsigned long pilot_status
-
-
-cal_component_free_categories_list
-void  
-GSList *categ_list
-
-
-cal_component_free_datetime
-void  
-CalComponentDateTime *dt
-
-
-cal_component_free_exdate_list
-void  
-GSList *exdate_list
-
-
-cal_component_free_geo
-void  
-struct icalgeotype *geo
-
-
-cal_component_free_icaltimetype
-void  
-struct icaltimetype *t
-
-
-cal_component_free_percent
-void  
-int *percent
-
-
-cal_component_free_priority
-void  
-int *priority
-
-
-cal_component_free_period_list
-void  
-GSList *period_list
-
-
-cal_component_free_recur_list
-void  
-GSList *recur_list
-
-
-cal_component_free_sequence
-void  
-int *sequence
-
-
-cal_component_free_text_list
-void  
-GSList *text_list
-
-
-CalComponentAlarmAction
-typedef enum {
-	CAL_COMPONENT_ALARM_NONE,
-	CAL_COMPONENT_ALARM_AUDIO,
-	CAL_COMPONENT_ALARM_DISPLAY,
-	CAL_COMPONENT_ALARM_EMAIL,
-	CAL_COMPONENT_ALARM_PROCEDURE,
-	CAL_COMPONENT_ALARM_UNKNOWN
-} CalComponentAlarmAction;
-
-
-CalComponentAlarmTriggerType
-typedef enum {
-	CAL_COMPONENT_ALARM_TRIGGER_RELATIVE,
-	CAL_COMPONENT_ALARM_TRIGGER_ABSOLUTE
-} CalComponentAlarmTriggerType;
-
-
-CalComponentAlarmTriggerRelated
-typedef enum {
-	CAL_COMPONENT_ALARM_TRIGGER_RELATED_START,
-	CAL_COMPONENT_ALARM_TRIGGER_RELATED_END
-} CalComponentAlarmTriggerRelated;
-
-
-CalComponentAlarmTrigger
-typedef struct {
-	CalComponentAlarmTriggerType type;
-
-	union {
-		struct {
-			struct icaldurationtype duration;
-			CalComponentAlarmTriggerRelated related;
-		} relative;
-
-		struct icaltimetype absolute;
-	} u;
-} CalComponentAlarmTrigger;
-
-
-cal_component_get_first_alarm
-CalComponentAlarm  *
-CalComponent *comp
-
-
-cal_component_get_next_alarm
-CalComponentAlarm  *
-CalComponent *comp
-
-
-cal_component_alarm_free
-void  
-CalComponentAlarm *alarm
-
-
-cal_component_alarm_get_action
-void  
-CalComponentAlarm *alarm, CalComponentAlarmAction *action
-
-
-cal_component_alarm_set_action
-void  
-CalComponentAlarm *alarm, CalComponentAlarmAction action
-
-
-cal_component_alarm_get_trigger
-void  
-CalComponentAlarm *alarm, CalComponentAlarmTrigger **trigger
-
-
-cal_component_alarm_set_trigger
-void  
-CalComponentAlarm *alarm, CalComponentAlarmTrigger *trigger
-
-
-cal_component_alarm_free_trigger
-void  
-CalComponentAlarmTrigger *trigger
-
-
-CalRecurType
-typedef enum {
-	CAL_RECUR_YEARLY,
-	CAL_RECUR_MONTHLY,
-	CAL_RECUR_WEEKLY,
-	CAL_RECUR_DAILY,
-	CAL_RECUR_HOURLY,
-	CAL_RECUR_MINUTELY,
-	CAL_RECUR_SECONDLY
-} CalRecurType;
-
-
-CalRecurrence
-typedef struct {
-	CalRecurType   type;
-
-	int            interval;
-
-	/* Specifies the end of the recurrence. No occurrences are generated
-	   after this date. If it is 0, the event recurs forever. */
-	time_t         enddate;
-
-	/* WKST property - the week start day: 0 = Monday to 6 = Sunday. */
-	gint	       week_start_day;
-
-
-	/* NOTE: I've used GList's here, but it doesn't matter if we use
-	   other data structures like arrays. The code should be easy to
-	   change. So long as it is easy to see if the modifier is set. */
-
-	/* For BYMONTH modifier. A list of GINT_TO_POINTERs, 0-11. */
-	GList	      *bymonth;
-
-	/* For BYWEEKNO modifier. A list of GINT_TO_POINTERs, [+-]1-53. */
-	GList	      *byweekno;
-
-	/* For BYYEARDAY modifier. A list of GINT_TO_POINTERs, [+-]1-366. */
-	GList	      *byyearday;
-
-	/* For BYMONTHDAY modifier. A list of GINT_TO_POINTERs, [+-]1-31. */
-	GList	      *bymonthday;
-
-	/* For BYDAY modifier. A list of GINT_TO_POINTERs, in pairs.
-	   The first of each pair is the weekday, 0 = Monday to 6 = Sunday.
-	   The second of each pair is the week number [+-]0-53. */
-	GList	      *byday;
-
-	/* For BYHOUR modifier. A list of GINT_TO_POINTERs, 0-23. */
-	GList	      *byhour;
-
-	/* For BYMINUTE modifier. A list of GINT_TO_POINTERs, 0-59. */
-	GList	      *byminute;
-
-	/* For BYSECOND modifier. A list of GINT_TO_POINTERs, 0-60. */
-	GList	      *bysecond;
-
-	/* For BYSETPOS modifier. A list of GINT_TO_POINTERs, +ve or -ve. */
-	GList	      *bysetpos;
-} CalRecurrence;
-
-
-CalObjTime
-
-
-CalObjTime
-struct CalObjTime {
-	guint16 year;
-	guint8 month;		/* 0 - 11 */
-	guint8 day;		/* 1 - 31 */
-	guint8 hour;		/* 0 - 23 */
-	guint8 minute;		/* 0 - 59 */
-	guint8 second;		/* 0 - 59 (maybe 60 for leap second) */
-};
-
-
-CalRecurInstanceFn
-gboolean 
-CalComponent *comp,
-					 time_t        instance_start,
-					 time_t        instace_end,
-					 gpointer      data
-
-
-cal_recur_generate_instances
-void 	
-CalComponent		*comp,time_t			 start,time_t			 end,CalRecurInstanceFn	 cb,gpointer                cb_data
-
-
-cal_recur_from_icalrecurrencetype
-CalRecurrence  *
-struct icalrecurrencetype *ir
-
-
-cal_recur_free
-void  
-CalRecurrence *r
-
-
-CalObjInstance
-typedef struct {
-	char *uid;			/* UID of the object */
-	time_t start;			/* Start time of instance */
-	time_t end;			/* End time of instance */
-} CalObjInstance;
-
-
-cal_obj_instance_list_free
-void  
-GList *list
-
-
-CalAlarmInstance
-typedef struct {
-	char *uid;			/* UID of object */
-#if 0
-	enum AlarmType type;		/* Type of alarm */
-#endif
-	time_t trigger;			/* Alarm trigger time */
-	time_t occur;			/* Occurrence time */
-} CalAlarmInstance;
-
-
-cal_alarm_instance_list_free
-void  
-GList *list
-
-
-CalObjType
-typedef enum {
-	CALOBJ_TYPE_EVENT   = 1 << 0,
-	CALOBJ_TYPE_TODO    = 1 << 1,
-	CALOBJ_TYPE_JOURNAL = 1 << 2,
-	CALOBJ_TYPE_ANY     = 0x07
-} CalObjType;
-
-
-cal_obj_uid_list_free
-void  
-GList *list
-
-
-time_from_icaltimetype
-time_t  
-struct icaltimetype itt
-
-
-time_from_isodate
-time_t  
-char *str
-
-
-time_from_start_duration
-time_t  
-time_t start, char *duration
-
-
-isodate_from_time_t
-char    *
-time_t t
-
-
-get_time_t_hour
-int  
-time_t t
-
-
-isodiff_to_secs
-int  
-char *str
-
-
-isodiff_from_secs
-char    *
-int secs
-
-
-time_add_minutes
-time_t  
-time_t time, int minutes
-
-
-time_add_day
-time_t  
-time_t time, int days
-
-
-time_add_week
-time_t  
-time_t time, int weeks
-
-
-time_add_month
-time_t  
-time_t time, int months
-
-
-time_add_year
-time_t  
-time_t time, int years
-
-
-format_simple_hour
-char  *
-int hour, int use_am_pm
-
-
-time_days_in_month
-int  
-int year, int month
-
-
-time_from_day
-time_t  
-int year, int month, int day
-
-
-time_day_hour
-time_t  
-time_t t, int hour
-
-
-time_year_begin
-time_t  
-time_t t
-
-
-time_year_end
-time_t  
-time_t t
-
-
-time_month_begin
-time_t  
-time_t t
-
-
-time_month_end
-time_t  
-time_t t
-
-
-time_week_begin
-time_t  
-time_t t
-
-
-time_week_end
-time_t  
-time_t t
-
-
-time_day_begin
-time_t  
-time_t t
-
-
-time_day_end
-time_t  
-time_t t
-
-
-parse_date
-time_t  
-char *str
-
-
-print_time_t
-void  
-time_t t
-
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util-sections.txt b/doc/devel/calendar/cal-util/evolution-cal-util-sections.txt
deleted file mode 100644
index cd928fc7e3..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util-sections.txt
+++ /dev/null
@@ -1,166 +0,0 @@
-

-cal-component
-CAL_COMPONENT
-CalComponent
-
-CalComponentVType
-CalComponentField
-CalComponentClassification
-CalComponentDateTime
-CalComponentPeriodType
-CalComponentPeriod
-CalComponentText
-CalComponentTransparency
-CalComponentAlarm
-CalComponentPrivate
-
-cal_component_gen_uid
-cal_component_new
-cal_component_clone
-cal_component_set_new_vtype
-cal_component_set_icalcomponent
-cal_component_get_icalcomponent
-cal_component_get_vtype
-cal_component_get_as_string
-cal_component_commit_sequence
-cal_component_get_uid
-cal_component_set_uid
-cal_component_get_categories_list
-cal_component_set_categories_list
-cal_component_get_classification
-cal_component_set_classification
-cal_component_get_comment_list
-cal_component_set_comment_list
-cal_component_get_completed
-cal_component_set_completed
-cal_component_get_created
-cal_component_set_created
-cal_component_get_description_list
-cal_component_set_description_list
-cal_component_get_dtend
-cal_component_set_dtend
-cal_component_get_dtstamp
-cal_component_set_dtstamp
-cal_component_get_dtstart
-cal_component_set_dtstart
-cal_component_get_due
-cal_component_set_due
-cal_component_get_exdate_list
-cal_component_set_exdate_list
-cal_component_get_exrule_list
-cal_component_set_exrule_list
-cal_component_get_geo
-cal_component_set_geo
-cal_component_get_last_modified
-cal_component_set_last_modified
-cal_component_get_percent
-cal_component_set_percent
-cal_component_get_priority
-cal_component_set_priority
-cal_component_get_rdate_list
-cal_component_set_rdate_list
-cal_component_has_rdates
-cal_component_get_rrule_list
-cal_component_set_rrule_list
-cal_component_has_rrules
-cal_component_get_sequence
-cal_component_set_sequence
-cal_component_get_summary
-cal_component_set_summary
-cal_component_get_transparency
-cal_component_set_transparency
-cal_component_get_url
-cal_component_set_url
-cal_component_get_pilot_id
-cal_component_set_pilot_id
-cal_component_get_pilot_status
-cal_component_set_pilot_status
-
-cal_component_free_categories_list
-cal_component_free_datetime
-cal_component_free_exdate_list
-cal_component_free_geo
-cal_component_free_icaltimetype
-cal_component_free_percent
-cal_component_free_priority
-cal_component_free_period_list
-cal_component_free_recur_list
-cal_component_free_sequence
-cal_component_free_text_list
-
-CalComponentAlarmAction
-CalComponentAlarmTriggerType
-CalComponentAlarmTriggerRelated
-CalComponentAlarmTrigger
-
-cal_component_get_first_alarm
-cal_component_get_next_alarm
-cal_component_alarm_free
-cal_component_alarm_get_action
-cal_component_alarm_set_action
-cal_component_alarm_get_trigger
-cal_component_alarm_set_trigger
-cal_component_alarm_free_trigger
-
-
-CAL_COMPONENT_TYPE
-CAL_COMPONENT_CLASS
-IS_CAL_COMPONENT
-IS_CAL_COMPONENT_CLASS
-cal_component_get_type
-
-
-CalComponent
-
-

-
-

-cal-recur
-CalRecurType
-CalRecurrence
-CalObjTime
-CalRecurInstanceFn
-cal_recur_generate_instances
-cal_recur_from_icalrecurrencetype
-cal_recur_free
-

-
-

-cal-util
-CalObjInstance
-cal_obj_instance_list_free
-CalAlarmInstance
-cal_alarm_instance_list_free
-CalObjType
-cal_obj_uid_list_free
-

-
-

-timeutil
-time_from_icaltimetype
-time_from_isodate
-time_from_start_duration
-isodate_from_time_t
-get_time_t_hour
-isodiff_to_secs
-isodiff_from_secs
-time_add_minutes
-time_add_day
-time_add_week
-time_add_month
-time_add_year
-format_simple_hour
-time_days_in_month
-time_from_day
-time_day_hour
-time_year_begin
-time_year_end
-time_month_begin
-time_month_end
-time_week_begin
-time_week_end
-time_day_begin
-time_day_end
-parse_date
-print_time_t
-

diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.args b/doc/devel/calendar/cal-util/evolution-cal-util.args
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.hierarchy b/doc/devel/calendar/cal-util/evolution-cal-util.hierarchy
deleted file mode 100644
index cc235653f2..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util.hierarchy
+++ /dev/null
@@ -1,2 +0,0 @@
-GtkObject
-  CalComponent
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.signals b/doc/devel/calendar/cal-util/evolution-cal-util.signals
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/calendar/cal-util/evolution-cal-util.types b/doc/devel/calendar/cal-util/evolution-cal-util.types
deleted file mode 100644
index 52b2d9bf90..0000000000
--- a/doc/devel/calendar/cal-util/evolution-cal-util.types
+++ /dev/null
@@ -1,4 +0,0 @@
-#include 
-#include 
-
-cal_component_get_type
diff --git a/doc/devel/calendar/cal-util/tmpl/cal-component.sgml b/doc/devel/calendar/cal-util/tmpl/cal-component.sgml
deleted file mode 100644
index 2f800e583f..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/cal-component.sgml
+++ /dev/null
@@ -1,934 +0,0 @@
-
-CalComponent
-
-
-RFC 2445 iCalendar component object.
-
-
-  
-    The #CalComponent object provides a wrapper over the &libical;
-    functions for manipulating calendar components.  #CalComponent
-    presents a GTK+-like interface to calendar components according to
-    RFC 2445.
-  
-
-  
-    While &libical; supports almost all of the features of the
-    iCalendar RFCs, applications are normally not interested in all
-    the mindless gunk that is there.  Still, applications should do
-    their best not to drop extension fields from calendar components
-    or any other extra information they do not support (including
-    standard fields they are not interested in).  The #CalComponent
-    object provides a wrapper over
-    icalcomponent structures from &libical;
-    so that no information in them will be lost even if the
-    application is not designed to handle it.  Also, #CalComponent
-    provides a higher-level API to many of the &libical; operations so
-    as to make it less painful to deal with iCalendar components.
-  
-
-  
-    A #CalComponent object starts out empty.  It must be initialized
-    from an existing icalcomponent structure
-    by using the cal_component_set_icalcomponent() function, or from a
-    completely new data by specifying the desired component type to
-    the cal_component_set_new_vtype() function.
-  
-
-  
-    #CalComponent will create an internal map of the properties in the
-    icalcomponent structure and then allow
-    random access to them via the #CalComponent API functions;
-    normally the &libical; API would have to be used by creating many
-    iterators and other unpleasant constructs.  #CalComponent keeps
-    handles to the properties it scanned from the
-    icalcomponent and will let the parent
-    application modify them at any time without having to do any
-    iteration.
-  
-
-  
-    Eventually a #CalComponent may be turned into the RFC 2445 string
-    representation of an iCalendar component by using the
-    cal_component_get_as_string() function.  Applications can then
-    transfer this interoperable
-    
-      
-	“Interoperable.”  Heavens, I love that word.
-      
-    
-    string to other programs that deal with iCalendar.
-  
-
-
-  
-
-  
-
-
-  
-    Casts a #GtkObject to a #CalComponent.
-  
-
-@obj: A GTK+ object.
-
-
-
-  
-    Calendar component types as defined by RFC 2445.  These values can
-    be used to create a new calendar component by passing them to the
-    cal_component_set_new_vtype() function.  They are also the return
-    value of the cal_component_get_vtype() function.  The only time
-    the @CAL_COMPONENT_NO_TYPE value is used is when querying the
-    vtype of an uninitialized #CalComponent.
-  
-
-@CAL_COMPONENT_NO_TYPE: Returned from cal_component_get_vtype() to
-  indicate an uninitialized #CalComponent object.
-
-@CAL_COMPONENT_EVENT: Indicates a VEVENT component.
-@CAL_COMPONENT_TODO: Indicates a VTODO component.
-@CAL_COMPONENT_JOURNAL: Indicates a VJOURNAL component.
-@CAL_COMPONENT_FREEBUSY: Indicates a VFREEBUSY component.
-@CAL_COMPONENT_TIMEZONE: Indicates a VTIMEZOME component.
-
-
-  
-    These values are used as identifiers for #ETable columns.  These
-    are used by the calendar GUI code in Evolution.
-  
-
-@CAL_COMPONENT_FIELD_CATEGORIES: Component's list of categories.
-@CAL_COMPONENT_FIELD_CLASSIFICATION: Component's classification.
-@CAL_COMPONENT_FIELD_COMPLETED: Component's completion date.
-@CAL_COMPONENT_FIELD_DTEND: Component's ending date.
-@CAL_COMPONENT_FIELD_DTSTART: Component's starting date.
-@CAL_COMPONENT_FIELD_DUE: Component's due date.
-@CAL_COMPONENT_FIELD_GEO: Component's geographical position.
-@CAL_COMPONENT_FIELD_PERCENT: Component's percent completed value.
-@CAL_COMPONENT_FIELD_PRIORITY: Component's priority.
-@CAL_COMPONENT_FIELD_SUMMARY: Component's summary.
-@CAL_COMPONENT_FIELD_TRANSPARENCY: Component's transparency value.
-@CAL_COMPONENT_FIELD_URL: Component's URL.
-@CAL_COMPONENT_FIELD_HAS_ALARMS: Whether the component has any alarms.
-@CAL_COMPONENT_FIELD_ICON: Which icon to use for the component.
-@CAL_COMPONENT_FIELD_COMPLETE: Whether the component has been completed.
-@CAL_COMPONENT_FIELD_RECURRING: Whether the component has any recurrences.
-@CAL_COMPONENT_FIELD_OVERDUE: Whether the component is overdue.
-@CAL_COMPONENT_FIELD_COLOR: Which color to use for the component.
-@CAL_COMPONENT_FIELD_NUM_FIELDS: Total number of enumerated fields.
-
-
-  
-    Values for the access classification property of a calendar
-    component.
-  
-
-@CAL_COMPONENT_CLASS_NONE: Indicates that no access classification has
-    been set for the corresponding component.
-
-@CAL_COMPONENT_CLASS_PUBLIC: Public access.
-@CAL_COMPONENT_CLASS_PRIVATE: Private access.
-@CAL_COMPONENT_CLASS_CONFIDENTIAL: Confidential access.
-
-@CAL_COMPONENT_CLASS_UNKNOWN: Unknown access classification value,
-  used when &libical; returns something #CalComponent does not know
-  about.
-
-
-  
-    This structure defines a date and time value.
-  
-
-
-
-  
-    Defines how a period of time is specified.
-  
-
-@CAL_COMPONENT_PERIOD_DATETIME: Indicates that the period is specified
-  by starting and ending date/time values.
-
-@CAL_COMPONENT_PERIOD_DURATION: Indicates that the period is specified
-  as a starding date/time and a duration value.
-
-
-  
-    This structure defines a period of time.
-  
-
-
-
-  
-    This structure defines the value of a text property that may have
-    an alternate representation parameter.
-  
-
-
-
-
-
-
-
-@CAL_COMPONENT_TRANSP_NONE: 
-@CAL_COMPONENT_TRANSP_TRANSPARENT: 
-@CAL_COMPONENT_TRANSP_OPAQUE: 
-@CAL_COMPONENT_TRANSP_UNKNOWN: 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@Returns: 
-
-
-
-
-
-
-
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@type: 
-
-
-
-
-
-
-
-@comp: 
-@icalcomp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-
-
-
-
-
-
-
-@comp: 
-@uid: 
-
-
-
-
-
-
-
-@comp: 
-@uid: 
-
-
-
-
-
-
-
-@comp: 
-@categ_list: 
-
-
-
-
-
-
-
-@comp: 
-@categ_list: 
-
-
-
-
-
-
-
-@comp: 
-@classif: 
-
-
-
-
-
-
-
-@comp: 
-@classif: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@text_list: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@dt: 
-
-
-
-
-
-
-
-@comp: 
-@exdate_list: 
-
-
-
-
-
-
-
-@comp: 
-@exdate_list: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@geo: 
-
-
-
-
-
-
-
-@comp: 
-@geo: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@t: 
-
-
-
-
-
-
-
-@comp: 
-@percent: 
-
-
-
-
-
-
-
-@comp: 
-@percent: 
-
-
-
-
-
-
-
-@comp: 
-@priority: 
-
-
-
-
-
-
-
-@comp: 
-@priority: 
-
-
-
-
-
-
-
-@comp: 
-@period_list: 
-
-
-
-
-
-
-
-@comp: 
-@period_list: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@recur_list: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@sequence: 
-
-
-
-
-
-
-
-@comp: 
-@sequence: 
-
-
-
-
-
-
-
-@comp: 
-@summary: 
-
-
-
-
-
-
-
-@comp: 
-@summary: 
-
-
-
-
-
-
-
-@comp: 
-@transp: 
-
-
-
-
-
-
-
-@comp: 
-@transp: 
-
-
-
-
-
-
-
-@comp: 
-@url: 
-
-
-
-
-
-
-
-@comp: 
-@url: 
-
-
-
-
-
-
-
-@comp: 
-@pilot_id: 
-
-
-
-
-
-
-
-@comp: 
-@pilot_id: 
-
-
-
-
-
-
-
-@comp: 
-@pilot_status: 
-
-
-
-
-
-
-
-@comp: 
-@pilot_status: 
-
-
-
-
-
-
-
-@categ_list: 
-
-
-
-
-
-
-
-@dt: 
-
-
-
-
-
-
-
-@exdate_list: 
-
-
-
-
-
-
-
-@geo: 
-
-
-
-
-
-
-
-@t: 
-
-
-
-
-
-
-
-@percent: 
-
-
-
-
-
-
-
-@priority: 
-
-
-
-
-
-
-
-@period_list: 
-
-
-
-
-
-
-
-@recur_list: 
-
-
-
-
-
-
-
-@sequence: 
-
-
-
-
-
-
-
-@text_list: 
-
-
-
-
-
-
-
-@CAL_COMPONENT_ALARM_NONE: 
-@CAL_COMPONENT_ALARM_AUDIO: 
-@CAL_COMPONENT_ALARM_DISPLAY: 
-@CAL_COMPONENT_ALARM_EMAIL: 
-@CAL_COMPONENT_ALARM_PROCEDURE: 
-@CAL_COMPONENT_ALARM_UNKNOWN: 
-
-
-
-
-
-
-@CAL_COMPONENT_ALARM_TRIGGER_RELATIVE: 
-@CAL_COMPONENT_ALARM_TRIGGER_ABSOLUTE: 
-
-
-
-
-
-
-@CAL_COMPONENT_ALARM_TRIGGER_RELATED_START: 
-@CAL_COMPONENT_ALARM_TRIGGER_RELATED_END: 
-
-
-
-
-
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@Returns: 
-
-
-
-
-
-
-
-@alarm: 
-
-
-
-
-
-
-
-@alarm: 
-@action: 
-
-
-
-
-
-
-
-@alarm: 
-@action: 
-
-
-
-
-
-
-
-@alarm: 
-@trigger: 
-
-
-
-
-
-
-
-@alarm: 
-@trigger: 
-
-
-
-
-
-
-
-@trigger: 
-
-
-
diff --git a/doc/devel/calendar/cal-util/tmpl/cal-recur.sgml b/doc/devel/calendar/cal-util/tmpl/cal-recur.sgml
deleted file mode 100644
index 703f8b2b85..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/cal-recur.sgml
+++ /dev/null
@@ -1,88 +0,0 @@
-
-cal-recur
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@CAL_RECUR_YEARLY: 
-@CAL_RECUR_MONTHLY: 
-@CAL_RECUR_WEEKLY: 
-@CAL_RECUR_DAILY: 
-@CAL_RECUR_HOURLY: 
-@CAL_RECUR_MINUTELY: 
-@CAL_RECUR_SECONDLY: 
-
-
-
-
-
-
-
-
-
-
-
-
-@year: 
-@month: 
-@day: 
-@hour: 
-@minute: 
-@second: 
-
-
-
-
-
-
-@comp: 
-@instance_start: 
-@instace_end: 
-@data: 
-@Returns: 
-
-
-
-
-
-
-
-@comp: 
-@start: 
-@end: 
-@cb: 
-@cb_data: 
-
-
-
-
-
-
-
-@ir: 
-@Returns: 
-
-
-
-
-
-
-
-@r: 
-
-
diff --git a/doc/devel/calendar/cal-util/tmpl/cal-util.sgml b/doc/devel/calendar/cal-util/tmpl/cal-util.sgml
deleted file mode 100644
index 8d4516c2ec..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/cal-util.sgml
+++ /dev/null
@@ -1,62 +0,0 @@
-
-cal-util
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@list: 
-
-
-
-
-
-
-
-
-
-
-
-
-
-@list: 
-
-
-
-
-
-
-
-@CALOBJ_TYPE_EVENT: 
-@CALOBJ_TYPE_TODO: 
-@CALOBJ_TYPE_JOURNAL: 
-@CALOBJ_TYPE_ANY: 
-
-
-
-
-
-
-@list: 
-
-
diff --git a/doc/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml b/doc/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml
deleted file mode 100644
index e69de29bb2..0000000000
diff --git a/doc/devel/calendar/cal-util/tmpl/timeutil.sgml b/doc/devel/calendar/cal-util/tmpl/timeutil.sgml
deleted file mode 100644
index 3b62fbba3f..0000000000
--- a/doc/devel/calendar/cal-util/tmpl/timeutil.sgml
+++ /dev/null
@@ -1,260 +0,0 @@
-
-timeutil
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-@itt: 
-@Returns: 
-
-
-
-
-
-
-
-@str: 
-@Returns: 
-
-
-
-
-
-
-
-@start: 
-@duration: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@str: 
-@Returns: 
-
-
-
-
-
-
-
-@secs: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@minutes: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@days: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@weeks: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@months: 
-@Returns: 
-
-
-
-
-
-
-
-@time: 
-@years: 
-@Returns: 
-
-
-
-
-
-
-
-@hour: 
-@use_am_pm: 
-@Returns: 
-
-
-
-
-
-
-
-@year: 
-@month: 
-@Returns: 
-
-
-
-
-
-
-
-@year: 
-@month: 
-@day: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@hour: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-@Returns: 
-
-
-
-
-
-
-
-@str: 
-@Returns: 
-
-
-
-
-
-
-
-@t: 
-
-
diff --git a/doc/devel/calendar/evolution-calendar.sgml b/doc/devel/calendar/evolution-calendar.sgml
deleted file mode 100644
index f3936d9bbc..0000000000
--- a/doc/devel/calendar/evolution-calendar.sgml
+++ /dev/null
@@ -1,51 +0,0 @@
-  
-    
-      
-	
-	  Federico
-	  Mena Quintero
-	  
-	    

-	      federico@helixcode.com
-	    

-	  
-	
-      
-    
-
-    Developing Applications for the Evolution Calendar
-
-    
-      
-	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.
-      
-
-      
-	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.
-      
-
-      
-	This part does not describe the internal interfaces of the
-	Evolution Calendar; for that you should read the Evolution
-	Internals Guide.  You should only need to read that guide if
-	you are interested in the way the calendar works internally or
-	if you want to make changes directly to the Evolution Calendar
-	code.
-      
-    
-
-    &calendar-architecture;
-  
-
-
diff --git a/doc/devel/calendar/public-reference.sgml b/doc/devel/calendar/public-reference.sgml
deleted file mode 100644
index f8aa6e848d..0000000000
--- a/doc/devel/calendar/public-reference.sgml
+++ /dev/null
@@ -1,24 +0,0 @@
-  
-    Calendar Public API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	public APIs of the different components of the Evolution
-	Calendar.
-      
-    
-
-    &CalClient;
-    &CalComponent;
-    &cal-util;
-    &cal-recur;
-    &timeutil;
-  
-
-
diff --git a/doc/devel/calendar/reference.sgml b/doc/devel/calendar/reference.sgml
deleted file mode 100644
index f8aa6e848d..0000000000
--- a/doc/devel/calendar/reference.sgml
+++ /dev/null
@@ -1,24 +0,0 @@
-  
-    Calendar Public API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	public APIs of the different components of the Evolution
-	Calendar.
-      
-    
-
-    &CalClient;
-    &CalComponent;
-    &cal-util;
-    &cal-recur;
-    &timeutil;
-  
-
-
diff --git a/doc/devel/evolution-devel-guide.sgml b/doc/devel/evolution-devel-guide.sgml
deleted file mode 100644
index ca80ec533a..0000000000
--- a/doc/devel/evolution-devel-guide.sgml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
-
-
-
-
-
-PCS">
-libical">
-]>
-
-
-  
-    Evolution Developer's Guide
-
-    
-      
-	Helix Code, Inc.
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-  
-
-  
-
-  &evolution-calendar;
-
-  
-
-  
-    Evolution Public API Reference
-
-    
-      
-	This part presents the class and function reference for the
-	different libraries and interfaces that Evolution provides.
-	Classes are described together with their methods; individual
-	functions are grouped by functional group.
-      
-    
-
-    &calendar-reference;
-  
-
diff --git a/doc/white-papers/calendar/calendar.sgml b/doc/white-papers/calendar/calendar.sgml
deleted file mode 100644
index 2cb3132e2b..0000000000
--- a/doc/white-papers/calendar/calendar.sgml
+++ /dev/null
@@ -1,209 +0,0 @@
-Evolution">
-CUA">
-PCS">
-Bonobo">
-CORBA">
-GTK+">
-]>
-
-

-
-  
-    &Evolution; Calendaring Framework
-
-    
-      
-	Federico
-	Mena Quintero
-	
-	  

-	    federico@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-    
-      
-	The &Evolution; groupware suite provides a framework for
-	developing calendaring applications, as well as a graphical
-	calendar client and a personal calendar server.  This white
-	paper describes the architecture of the &Evolution;
-	calendaring framework.
-      
-    
-  
-
-  
-
-  
-    Introduction
-
-    
-      Calendaring is an important part of a groupware suite.  A
-      calendaring framework will allow a user to keep a personal
-      calendar and have several applications use it.  Such
-      applications could be a graphical calendar client that the user
-      employs to schedule appointments and keep track of his time, a
-      Palm Pilot synchronization client, or
-      a simple alarm or reminder utility.  A comprehensive calendaring
-      framework will also allow multiple users to schedule
-      appointments between each other; for example, a project director
-      may want to schedule a weekly meeting with the rest of the
-      project members, or a person who owns a large house may want to
-      schedule a big party with his friends.  The attendees will then
-      want to reply with messages such as, “I will
-      attend”, or “I will attend only if the proposed time
-      is changed”.
-    
-
-    
-      The &Evolution; groupware suite provides a framework for
-      developing calendaring applications, as well as a graphical
-      calendar client or calendar user agent (&CUA;) and a personal
-      calendar server (&PCS;).
-    
-
-    
-      The following sections explain the basic calendaring framework,
-      the functions of the calendar user agent and the personal
-      calendar server, and the relationship between the two.
-    
-  
-
-  
-
-  
-    Personal Calendar Server
-
-    
-      The personal calendar server (&PCS;) provides centralized
-      management and storage of a user's personal calendar.  Multiple
-      clients can connect to the &PCS; simultaneously to query and
-      modify the user's calendar in a synchronized fashion.  The main
-      features of the &PCS; are as follows:
-    
-
-    
-      Storage
-
-      
-	The &PCS; is responsible for loading and saving calendars.
-	Centralizing the loading and saving functionality allows
-	multiple clients to use the same calendar at the same time
-	without having to worry about each other.
-      
-    
-
-    
-      Basic Queries
-
-      
-	The &PCS; provides functions to do basic queries on a
-	calendar, for example, a client can ask the server for a list
-	of all the appointments in the calendar, or for all the data
-	for a specific appointment.
-      
-    
-
-    
-      Recurrence and Alarm Queries
-
-      
-	Clients can ask the &PCS; for a list of the appointments that
-	occur within a specified time range; for example a graphical
-	client that has a per-week view could ask the &PCS; for all
-	the appointments that occur in a particular week.  This
-	includes multiple occurrences of a single recurring event; for
-	example, the object for “a 1-hour meeting that occurs on
-	every Tuesday and Thursday” is represented inside the
-	&PCS; as a single event with a recurrence rule.  Similarly,
-	clients can ask the &PCS; for a list of events that have
-	alarms that trigger within a specified time range.
-      
-    
-
-    
-      Notification of Changes
-
-      
-	This is the most important function of the &PCS;, as it allows
-	multiple calendar clients to maintain a unified view of the
-	calendar between the server and themselves.  When a client
-	asks the &PCS; to modify or remove an event, the &PCS;
-	notifies all the clients that are connected to it about the
-	change.  The policy is that “the server is always
-	right”; clients can act as dumb views onto the
-	calendar's data and they will be notified by the &PCS; when
-	something changes.
-      
-    
-  
-
-  
-
-  
-    Calendar User Agent
-
-    
-      A calendar user agent (&CUA;) is a program that lets a user
-      manipulate a calendar.  &Evolution; provides an attractive,
-      graphical calendar client that communicates with the &Evolution;
-      personal calendar server.
-    
-
-    
-      The &Evolution; calendar client just provides a view onto the
-      data that is stored and managed by the personal calendar server.
-      The calendar client does not perform direct manipulations on a
-      calendar's data; instead it offloads those requests to the
-      calendar server, which takes care of making the appropriate
-      modifications in the calendar and then notifies all the clients
-      about the changes.
-    
-  
-
-  
-
-  
-    Calendar Client Library
-
-    
-      Communication between the personal calendar server and calendar
-      clients is defined by a set of &Bonobo; &CORBA; interfaces.
-      Clients can be written by implementing the client-side
-      Listener interface, which defines the
-      notification callbacks that the PCS uses to inform clients about
-      changes to the calendar.
-    
-
-    
-      As a convenience for >K; programmers, &Evolution; also
-      includes a library which provides a
-      CalClient class which can be used for
-      communication with the personal calendar server.  Objects of
-      this class automatically contact the PCS when they are created.
-      CalClient provides functions to request
-      changes in the calendar, and it also emits signals when it gets
-      notification about changes from the PCS.  This makes it easy and
-      convenient to write calendar clients for &Evolution; using
-      >K;.
-    
-
-    
-      The implementation of the CalClient class
-      simply wraps the &Evolution; &CORBA; interfaces for calendaring
-      with a familiar-looking >K; object.  Calls to the
-      Listener interface get translated to
-      signal emissions from the CalClient, thus
-      shielding programmers from the details of the &CORBA;
-      interfaces.
-    
-  
-

diff --git a/doc/white-papers/mail/camel.sgml b/doc/white-papers/mail/camel.sgml
deleted file mode 100644
index a339909f54..0000000000
--- a/doc/white-papers/mail/camel.sgml
+++ /dev/null
@@ -1,339 +0,0 @@
-Evolution">
-
-]>
-
-

-
-  
-    The &Camel; Messaging Library
-
-    
-      
-	Dan
-	Winship
-	
-	  

-	    danw@helixcode.com
-	  

-	
-      
-
-      
-	Bertrand
-	Guiheneuf
-	
-	  

-	    bertrand@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-  
-
-  
-    Introduction
-
-    
-      &Camel; is a generic messaging library. It is being used as the
-      back end for the mail component of &Evolution;. The name
-      "&Camel;" is an acronym; it refers to the fact that the
-      library is capable of going several days without food or water.
-      It means : Camel's Acronym Makes Everyone Laugh.
-    
-
-    
-      &Camel;'s initial design is heavily based on Sun's
-      JavaMail API. It uses the Gtk+ object
-      system, and many of its classes are direct analags of JavaMail
-      classes. Its design has also been influenced by the features of
-      IMAP, and the limitations of the standard UNIX mbox mail store,
-      which set some of the boundaries on its requirements and
-      extensibility.
-    
-
-    
-      &Camel; sees all message repositories as stores containing
-      folders. These folders in turn contain the messages the client
-      actually accesses. The use of such a unified interface allows
-      the client applications to be very extensible. &Camel; includes
-      an external provider mechanism which allows applications to
-      dynamically load and use protocols which were not available when
-      the application was initially written.
-    
-
-    
-      The abstract store/folder mechanism is a powerful and versatile
-      way of accessing messages. No particular asumptions are made on
-      the client side, thus allowing new ways of managing the
-      messages. For example, the messages stored in the folders don't
-      necessarily have to share some common physical location. The
-      folder can be a purely virtual folder, containing only
-      references to the actual messages. This is used by the "vFolder"
-      provider, which allows you select messages meeting particular
-      criteria and deal with them as a group.
-    
-
-    
-      In addition to these possibilities, &Camel; has full MIME
-      support. &Camel; MIME messages are lightweight objects
-      representing the MIME skeleton of the actual message. The data
-      contained in the subparts are never stored in memory except when
-      they are actually needed. The application, when accessing the
-      various MIME objects contained in the message (text parts,
-      attachments, embedded binary objects ...) asks &Camel; for a
-      stream that it can read data from. This scheme is particularly
-      useful with the IMAP provider. IMAP has strong MIME support
-      built-in, which allows &Camel; to download only the parts of
-      messages that it actually needs: attachments need not be
-      downloaded until they are viewed, and unnecessary
-      "multipart/alternative" parts will never be read off the server.
-    
-  
-
-  
-    Overview
-
-    
-
-    
-      To begin using &Camel;, an application first creates a
-      CamelSession object. This object is used
-      to store application defaults, and to coordinate communication
-      between providers and the application.
-    
-
-    
-      A CamelProvider is a dynamically-loadable
-      module that provides functionality associated with a specific
-      service. Examples of providers are IMAP and SMTP. Providers
-      include subclasses of the various other &Camel; classes for
-      accessing and manipulating messages.
-    
-
-    
-      CamelService is an abstract class for
-      describing a connection to a local or remote service. It
-      currently has two subclasses: CamelStore,
-      for services that store messages (such as IMAP servers and mbox
-      files), and CamelTransport, for services
-      that deliver messages (such as SMTP, or a local MTA). A provider
-      could also be both a store and a transport, as in the case of
-      NNTP.
-    
-
-    
-      A CamelStore contains some number of
-      CamelFolder objects, which in turn
-      contain messages. A CamelFolder provides
-      a CamelFolderSummary object, which
-      includes details about the subject, date, and sender of each
-      message in the folder. The folder also includes the messages
-      themselves, as subclasses of CamelMedium.
-    
-
-    
-      Email messages are represented by the
-      CamelMimeMessage class, a subclass of
-      CamelMedium. This class includes
-      operations for accessing RFC822 and MIME headers, accessing
-      subparts of MIME messages, encoding and decoding Base64 and
-      Quoted-Printable, etc.
-    
-
-    
-      CamelTransport includes methods for
-      delivering messages. While the abstract
-      CamelTransport::send method takes a
-      CamelMedium, its subclasses may only be
-      able to deliver messages of specific
-      CamelMedium subclasses. For instance,
-      CamelSendmailTransport requires a
-      CamelMimeMessage, because it needs a
-      message that includes a "To:" header. A hypothetical
-      CamelNNTPTransport would need a
-      CamelNewsMessage, which would have a
-      "Newsgroups:" header.
-    
-
-    
-      The content of messages are referred to using
-      CamelStream and its subclasses. In the
-      case of an mbox-based store, the
-      CamelStream would abstract the operation
-      of reading the correct section of the mbox file. For IMAP,
-      reading off the CamelStream might result
-      in commands being issued to the remote IMAP server and data
-      being read off a socket.
-    
-
-    
-      The final major class in &Camel; is
-      CamelException, which is used to
-      propagate information about errors. Many methods take a
-      CamelException as an argument, which the
-      caller can then check if an error occurs. It includes both a
-      numeric error code which can be interpreted by the program, and
-      a text error message that can be displayed to the user.
-    
-  
-
-  
-    Major Subcomponents
-
-    
-      The Message Store
-
-      
-        A CamelStore inherits the ability to
-        connect and authenticate to a service from its parent class,
-        CamelService. It then adds the ability
-        to retrieve folders. A store must contain at least one folder,
-        which can be retrieved with
-        CamelStore::get_default_folder. There are
-        also methods to retrieve the "top-level" folder (for
-        hieararchical stores), and to retrieve an arbitrary folder by
-        name.
-      
-
-      
-        All CamelFolders must implement certain
-        core operations, most notably generating a summary and
-        retrieving and deleting messages. A
-        CamelFolder must assign a permanently
-        unique identifier to each message it contains. Messages can
-        then be retrieved via
-        CamelFolder::get_message_by_uid. Alternately,
-        within a single mail-reading session, messages can be referred
-        to by their linear position within the store using
-        CamelFolder::get_message_by_number.
-      
-
-      
-        Folders must also implement the
-        get_parent_folder and
-        list_subfolders methods. For stores that
-        don't allow multiple folders, they would return NULL and an
-        empty list, respectively. Stores that do allow multiple
-        folders will also define methods for creating and deleting
-        folders, and for moving messages between them (assuming the
-        folders are writable).
-      
-
-      
-        Folders that support searching can define the
-        search_by_expression method. For mbox
-        folders, this is implemented by indexing the messages with the
-        ibex library and using that to search them later. For IMAP
-        folders, this uses the IMAP SEARCH command. Other folder types
-        might not be able to implement this functionality, in which
-        case users would not be able to do full-content searches on
-        them.
-      
-    
-
-    
-      Messages
-
-      
-        As mentioned before, messages are represented by subclasses of
-        CamelMedium.
-        CamelMedium itself is a subclass of
-        CamelDataWrapper, a generic class for
-        connecting a typed data source to a data sink.
-        CamelMedium adds the concept of message
-        headers versus message body.
-        (CamelDataWrapper has one other
-        important subclass, CamelMultipart,
-        which is used to provide separate access to the multiple
-        independent parts of a multipart MIME type.)
-        CamelMedium's subclasses provide more
-        specialized handling of various headers:
-        CamelMimePart adds special handling for
-        the &ldquot;Content-*&rdquot; headers in MIME messages, and
-        its subclass CamelMimeMessage adds
-        handling for the RFC822 headers.
-      
-
-      
-
-      
-        Consider a message with two parts: a text part (in both plain
-        text and HTML), and an attached image:
-
-	
-
-	  From: Dan Winship <danw@helixcode.com>
-	  To: Matt Loper <matt@helixcode.com>
-	  Subject: the Camel white paper
-	  MIME-Version: 1.0
-	  Content-Type: multipart/mixed;
-		boundary="jhTYrnsRrdhDFGa"
-
-	  This is a multi-part message in MIME format.
-	  --jhTYrnsRrdhDFGa
-	  Content-Type: multipart/alternative;
-		boundary="sFSenbAFDSgDfg"
-
-	  --sFSenbAFDSgDfg
-	  Content-Type: text/plain
-
-	  Hey, Matt
-
-	  Check out this graphic...
-
-	  -- Dan
-
-	  --sFSenbAFDSgDfg
-	  Content-Type: text/html
-
-	  Hey, Matt<br>
-	  <br>
-	  Check out this graphic...<br>
-	  <br>
-	  -- Dan<br>
-	  <br>
-	  --sFSenbAFDSgDfg--
-
-	  --jhTYrnsRrdhDFGa
-	  Content-Type: image/png
-	  Content-Transfer-Encoding: base64
-
-	  F4JLw0ORrkRa8AwAMQJLAaI3UDIGsco9RAaB92...
-	  --jhTYrnsRrdhDFGa--
-	
-
-	
-	  In &Camel;, this would be represented as follows:
-	
-
-        
-      
-
-      
-        Streams
-
-	
-	  Streams are a generic data transport layer. Two basic stream
-	  classes are CamelStreamFs, for
-	  reading and writing files, and
-	  CamelStreamMem, for reading from and
-	  writing to objects that are already in memory.
-	
-
-	
-	  Streams can also be chained together. So a CamelMimePart
-	  containing base64-encoded data can filter its output through
-	  a CamelStreamB64. Other parts of the application that want
-	  to read its data will never need to even realize that the
-	  original data was encoded.
-	
-      
-
-

diff --git a/doc/white-papers/mail/ibex.sgml b/doc/white-papers/mail/ibex.sgml
deleted file mode 100644
index dcb8f5ca4b..0000000000
--- a/doc/white-papers/mail/ibex.sgml
+++ /dev/null
@@ -1,158 +0,0 @@
-Evolution">
-
-
-]>
-
-

-
-  
-    Ibex: an Indexing System
-
-    
-      
-	Dan
-	Winship
-	
-	  

-	    danw@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-  
-
-  
-    Introduction
-
-    
-      &Ibex; is a library for text indexing. It is being used by
-      &Camel; to allow it to quickly search locally-stored messages,
-      either because the user is looking for a specific piece of text,
-      or because the application is contructing a vFolder or filtering
-      incoming mail.
-    
-  
-
-  
-    Design Goals and Requirements for Ibex
-
-    
-      The design of &Ibex; is based on a number of requirements.
-
-    
-      
-        
-	  First, obviously, it must be fast. In particular, searching
-	  the index must be appreciably faster than searching through
-	  the messages themselves, and constructing and maintaining
-	  the index must not take a noticeable amount of time.
-	
-      
-
-      
-        
-	  The indexes must not take up too much space. Many users have
-	  limited filesystem quotas on the systems where they read
-	  their mail, and even users who read mail on private machines
-	  have to worry about running out of space on their disks. The
-	  indexes should be able to do their job without taking up so
-	  much space that the user decides he would be better off
-	  without them.
-	
-
-	
-	  Another aspect of this problem is that the system as a whole
-	  must be clever about what it does and does not index:
-	  accidentally indexing a "text" mail message containing
-	  uuencoded, BinHexed, or PGP-encrypted data will drastically
-	  affect the size of the index file. Either the caller or the
-	  indexer itself has to avoid trying to index these sorts of
-	  things.
-	
-      
-
-      
-        
-	  The indexing system must allow data to be added to the index
-	  incrementally, so that new messages can be added to the
-	  index (and deleted messages can be removed from it) without
-	  having to re-scan all existing messages.
-	
-      
-
-      
-        
-	  It must allow the calling application to explain the
-	  structure of the data however it wants to, rather than
-	  requiring that the unit of indexing be individual files.
-	  This way, &Camel; can index a single mbox-format file and
-	  treat it as multiple messages.
-	
-      
-
-      
-        
-	  It must support non-ASCII text, given that many people send
-	  and receive non-English email, and even people who only
-	  speak English may receive email from people whose names
-	  cannot be written in the US-ASCII character set.
-	
-      
-    
-
-    
-      While there are a number of existing indexing systems, none of
-      them met all (or even most) of our requirements.
-    
-  
-
-  
-    The Implementation
-
-    
-      &Ibex; is still young, and many of the details of the current
-      implementation are not yet finalized.
-    
-
-    
-      With the current index file format, 13 megabytes of Info files
-      can be indexed into a 371 kilobyte index file—a bit under
-      3% of the original size. This is reasonable, but making it
-      smaller would be nice. (The file format includes some simple
-      compression, but gzip can compress an
-      index file to about half its size, so we can clearly do better.)
-    
-
-    
-      The implementation has been profiled and optimized for speed to
-      some degree. But, it has so far only been run on a 500MHz
-      Pentium III system with very fast disks, so we have no solid
-      benchmarks.
-    
-
-    
-      Further optimization (of both the file format and the in-memory
-      data structures) awaits seeing how the library is most easily
-      used by &Evolution;: if the indexes are likely to be kept in
-      memory for long periods of time, the in-memory data structures
-      need to be kept small, but the reading and writing operations
-      can be slow. On the other hand, if the indexes will only be
-      opened when they are needed, reading and writing must be fast,
-      and memory usage is less critical.
-    
-
-    
-      Of course, to be useful for other applications that have
-      indexing needs, the library should provide several options, so
-      that each application can use the library in the way that is
-      most suited for its needs.
-    
-  
-

diff --git a/doc/white-papers/widgets/e-table.sgml b/doc/white-papers/widgets/e-table.sgml
deleted file mode 100644
index 5ff4faf2ae..0000000000
--- a/doc/white-papers/widgets/e-table.sgml
+++ /dev/null
@@ -1,279 +0,0 @@
-Evolution">
-ETable">
-ETableModel">
-ETableSimple">
-ETableHeader">
-ETableSpecification">
-ETableCol">
-]>
-
-

-
-  
-    The ETable Widget
-
-    
-      
-	Chris
-	Lahey
-	
-	  

-	    clahey@helixcode.com
-	  

-	
-      
-      
-	Miguel
-	de Icaza
-	
-	  

-	    miguel@helixcode.com
-	  

-	
-      
-    
-
-    
-      2000
-      Helix Code, Inc.
-    
-
-  
-
-  
-    Introduction
-
-    
-      &ETable; is a table widget on steroids. It is intended to provide
-      all the table functionality needed throughout &Evolution;, and
-      hopefully be general purpose enough to be used in other projects.
-    
-
-    
-      &ETable; provides a lot of interactive control over the data in the
-      table.  Without any work from the programmer, &ETable; provides
-      rearrangeable columns and editable data.  When finished, &ETable; will
-      also provide, again with no programmer intervention, easy interactive
-      sorting and grouping.  
-    
-
-    
-      &ETable; gives you a great deal of functionality, flexibility, and
-      power. Most of this power is internal to the widget, but some of
-      the flexibility requires a bit of work by the programmer.
-      However, once you learn it, &ETable; is not very hard at all to
-      use.
-    
-
-    
-      &ETable;'s power comes from the fact that it is fully
-      model/view/controller based.  Various models are involved into
-      the process of rendering the information, and various views are
-      provided.  The programmer has a wide range of options: from the
-      most finely hand-tuned table to a generic all-encompasing widget
-      that takes over most of tasks.  It is up to the programmer: he
-      can use the simple to use &ETable; widget that takes care of
-      everything in a generic way, or he can use the various
-      components to roll his own tabular display.
-    
-
-    
-      &ETable; ships with a standard set of information renderers:
-      strings, bitmaps, toggle-buttons, check-boxes, and multi-line
-      strings.  But the programmer can write and implement his own
-      renderer for his information.  This means that by default
-      &ETable; provides the basic display facilities that programmers
-      required, but they offer the programmer a complete freedom to
-      incorporate new cell renderers.
-    
-    
-  
-
-  
-    ETableModel
-
-    
-      The data back end for the &ETable; is an &ETableModel;. The
-      &ETableModel is an abstract interface that acts as the
-      information repository for the various &ETable components.
-    
-    
-    
-      To use &ETable; you have to create a subclass of the abstract
-      &ETableModel; class.  However, to save you the work of defining
-      a new GtkClass every time you use
-      &ETable, there is a predefined subclass of &ETableModel; called
-      &ETableSimple; which simply takes a list of function callbacks
-      to perform the various operations.
-    
-
-  
-    
-  
-    Columns
-
-    
-      There are two different meanings to the word "column". The first
-      is the model column (defined by the &ETableCol: object). A model
-      column describes how it maps to the column in the &ETableModel;
-      as well as containing information about its properties (name,
-      resizability, resize dimensions, and a renderer for this
-      specific columns). 
-    
-
-    
-      &ETable; distinguishes between a model column index, and a view
-      column index.  The former reflects the column in which the data
-      is stored in the &ETableModel;  The later represents the actual
-      location at which the column is being displayed in the screen.
-    
-
-    
-      Each view column index corresponds to a specific model column,
-      though a model column may have any number of view columns
-      associated with it (including zero).  For example the same
-      column might be rendered twice, or the data from one column
-      could be used to display different bits of information
-    
-
-    
-      The view column does not necessarily depend on only one model
-      column. In some cases, the view column renderer can be given a
-      reference to another model column to get extra information about
-      its display. For example, a mail program could display deleted
-      messages with a line through them by creating a model column
-      with no corresponding view column that told whether or not the
-      message is deleted, and then having the text column
-      strikethrough the display if the invisible column had a value
-      corresponding to "deleted".
-    
-
-    
-      The view column also specifies a few other pieces of
-      information. One piece of information is the renderer. &ETable;
-      provides a number of renderers to choose from, or you can write
-      your own. Currently, there are renderers for text, image sets,
-      and checkboxes.
-    
-
-    
-      The view column also includes information about the header.
-      There are two types of headers: text, and pixbuf. The first
-      allows you to specify a string which is rendered in the header.
-      The second allows you to specify an image to copy into the
-      header.
-    
-  
-
-  
-    Header
-
-    
-      The &ETableHeader; represents the header information for the
-      table. The &ETableHeader; is used in two different ways. The
-      first is the in the full_header
-      element of an &ETable;. This is the list of possible columns in
-      the view. You add each of your columns to this &ETableHeader;
-      and then pass it into the &ETable;.
-    
-
-    
-      The second use is completely internal. &ETable; uses another
-      &ETableHeader; to store the actual displayed columns. Many of
-      the &ETableHeader; functions are for this purpose. The only
-      functions that users of the library should need to use are
-      e_table_header_new and
-      e_table_header_add_col.
-    
-  
-
-  
-    Layout Specification
-
-    
-      &ETable; uses an &ETableSpecification; to layout the columns of
-      the widget. The &ETableSpecification; is specified as XML data
-      passed into the &ETable; as a string.
-    
-
-    
-      The most powerful part of the &ETableSpecification; is that when
-      finished, &ETable; will allow you to get a copy of an
-      &ETableSpecification; that describes the current view of the
-      tree. This allows the developer to save the current view so that
-      next time the user opens this table, they find it in exactly the
-      state that they left it.
-    
-
-    
-      The XML specification allows for a number of things. First, it
-      allows you to pick a set of default columns to be shown. Thus,
-      even if you had hundreds of pieces of data, you could choose to
-      only display a few that fit on the screen by default.
-    
-
-    
-      The second major thing that the &ETableSpecification; allows you
-      to specify is the column grouping and sorting. &ETable; has a
-      powerful mechanism for allowing the user to choose columns to
-      group by, thus allowing multiple columns of sorting, as well as
-      visual grouping of similar elements and interactive selection of
-      what data to display.
-    
-
-    
-      The grouping in &ETableSpecification; is specified as a
-      hierarchy of columns to group by. Each level of the hierarchy
-      lets you sort by a particular column, either ascending or
-      descending. All levels except the last cause the canvas to group
-      by the given column.
-    
-
-    
-      An example &ETableSpecification; follows.
-    
-
-    
-      <ETableSpecification>
-        <columns-shown frozen_columns="2">
-	  <column> 0 </column>
-	  <column> 1 </column>
-	  <column> 2 </column>
-	  <column> 3 </column>
-	  <column> 4 </column>
-	</columns-shown>
-	<grouping>
-	  <group column="3" ascending="1">
-	    <group column="4" ascending="0">
-	      <leaf column="2" ascending="1"/>
-	    </group>
-	  </group>
-	</grouping>
-      </ETableSpecification>
-    
-
-    
-      This example has 5 columns which are initially in order. It has
-      2 levels of grouping. The first is grouped by the 4th column
-      (all indexes are 0 based) and sorts those groups in ascending
-      order. Inside those groups, the data is grouped by the fifth
-      column and sorted in descending order of the fifth column.
-      Finally, the data in those groups is sorted by the third column
-      in ascending order. Due to the "frozen_columns" attribute on the
-      columns-shown element, the user will not be
-      able to rearrange the first two columns. They will always be the
-      first two.
-    
-  
-
-  
-    Conclusion
-
-    
-      All in all, &ETable; is a very powerful widget. Once you learn
-      to use it, you have access to a vast amount of power requiring a
-      comparatively small amount of work.
-    
-  
-

-- 
cgit