From de2d358926885856d43a5f53aecb3739a9b5f3c8 Mon Sep 17 00:00:00 2001 From: nobody Date: Sun, 21 May 2000 22:40:15 +0000 Subject: This commit was manufactured by cvs2svn to create tag 'gnomoku-0_3'. svn path=/tags/gnomoku-0_3/; revision=3161 --- doc/.cvsignore | 2 - doc/C/apx-authors.sgml | 70 ---- doc/C/apx-bugs.sgml | 19 - doc/C/apx-fdl.sgml | 678 -------------------------------- doc/C/config-prefs.sgml | 209 ---------- doc/C/config-setupassist.sgml | 16 - doc/C/config-sync.sgml | 67 ---- doc/C/devel-action.sgml | 18 - doc/C/devel-component.sgml | 24 -- doc/C/devel-script.sgml | 17 - doc/C/evolution-guide.sgml | 118 ------ doc/C/preface.sgml | 149 ------- doc/C/usage-calendar.sgml | 140 ------- doc/C/usage-contact.sgml | 283 ------------- doc/C/usage-mail.sgml | 644 ------------------------------ doc/C/usage-mainwindow.sgml | 214 ---------- doc/C/usage-setup.sgml | 46 --- doc/C/usage-sync.sgml | 19 - doc/Camel-Classes | 35 -- doc/ChangeLog | 84 ---- doc/Design | 201 ---------- 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 ------------- 25 files changed, 4038 deletions(-) delete mode 100644 doc/.cvsignore 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/config-prefs.sgml delete mode 100644 doc/C/config-setupassist.sgml delete mode 100644 doc/C/config-sync.sgml delete mode 100644 doc/C/devel-action.sgml delete mode 100644 doc/C/devel-component.sgml delete mode 100644 doc/C/devel-script.sgml delete mode 100644 doc/C/evolution-guide.sgml 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-setup.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/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 550bd25cdb..0000000000 --- a/doc/.cvsignore +++ /dev/null @@ -1,2 +0,0 @@ -Makefile - diff --git a/doc/C/apx-authors.sgml b/doc/C/apx-authors.sgml deleted file mode 100644 index f68b395c9f..0000000000 --- a/doc/C/apx-authors.sgml +++ /dev/null @@ -1,70 +0,0 @@ - - - Authors - - Evolution was written by: - - Seth Alves: alves@helixcode.com - Anders Carlssonandersca@helixcode.com - 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 - Dave Mason dcm@redhat.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: winship@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. If you are using - GNOME 1.1 or later, you can also use command - bug-buddy for submitting bug reports. - - - This manual was written by Aaron Weber - (aaron@helixcode.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 eb30901422..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 contact the - Evolution team (bugs@helixcode.com) or use - bug-buddy if you find one we have not - listed, or if you have a patch to fix one. - - - - - 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 7a85c6e4a2..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/config-prefs.sgml b/doc/C/config-prefs.sgml deleted file mode 100644 index 67ca0e7577..0000000000 --- a/doc/C/config-prefs.sgml +++ /dev/null @@ -1,209 +0,0 @@ - - - Advanced Configuration with the Preferences Window - - If you prefer not to use the setup assistant, select - Preferences from the - Settings menu, and work your way through - the page tabs it offers you. They are: - - - - Identity, which allows you to set - your name, email address, and other information. The - default values are the ones found on your system account. - - - - - - Network, which allows you to - specify your network settings. There are no default - values for this information. - - - - - - Mail, which allows you to specify - attachment and HTML handling, forwarding behavior, - filters, and other Evolution - behaviors specific to email. The default behaviors are - those approved by Jamie Zawinski. - - - - - - Contacts, which allows you to - specify behavior that is specific to your contact - manager. - - - - - - Calendar, which allows you to set - the way that your calendar will behave and appear. The - default view is by week and the default calendar is - Western. Date format is determined by the system clock - and localization, and cannot be set here. - - - - - - General, which covers everything - else, including the Evolution - startup screen. - - - - - The Preferences Dialog is shown in - . - - - -
- Preferences Dialog - - Preferences dialog - - - -
- - - - - Identity Settings - - If you have only one email address, or use automatic - forwarding to funnel multiple addresses into one, then you - will only need to configure one identity. To create a single - user with a single identity, enter the following information: - (INSERT detailed DESCRIPTION HERE) - - - - If you have one email accout for your personal life, and one - for work, you'll want to create multiple identities. You - can do this by: (INSERT DESCRIPTION HERE) - - - - Multiple Identities and Network Settings - - If you use multiple network connections—if, for - example, you dial up an ISP for your personal mail, and use - a LAN for your work-related tasks— you will also have - to set seperate network settings for each identity. - - - - - - Setting up the Network - - In order to do much of anything 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 progam, you can almost certainly use the same - settings as you did with that program. Select the - Network tab in the - Preferences window to get started. - - - - Advanced Network Configuration - - INSERT a little introduction paragraph here. - - - Multiple Network Connections - - People with who use multiple ISP's or networks, or who - have multiple email accounts, will need to do a little - more work, but not much. - - - Multiple Identities and Networks - - Nate's laptop goes everywhere with him, and he needs - to be able to use Evolution - from anywhere&mdash a hotel room, an airplane, a - client's office, his office, anywhere at all. (INSERT - HOW EVOLUTION HELPS HIM DO THIS). - - - - - (INSERT DESCRIPTION OF WHAT THESE THINGS ARE AND HOW TO - USE THEM) (I'M THINKING IN TERMS OF THE APPLE LOCATION - MANAGER) (Kill this section if Evolution doesn't support - this for 1.0). - - - - - Other Advanced Network Settings - - I can't think of any at the moment but i'm sure they're - out there. They belong here. - - - - - - Modifying the Mail - - This section discusses mail-specific preferences. Click on - the Mail tab in the - Preferences window to access these - settings. - - - You can set the following options: - - - - - 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. Click - on the Calendar tab in the - Preferences window to access these - settings. - - - You can set the following options: - - - - - - General Preferences - - Overall Evolution prefs-- whatever else doesn't fit. - - - - \ No newline at end of file diff --git a/doc/C/config-setupassist.sgml b/doc/C/config-setupassist.sgml deleted file mode 100644 index 03b85ea12c..0000000000 --- a/doc/C/config-setupassist.sgml +++ /dev/null @@ -1,16 +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 chose not to use it the first time you ran - Evolution, you can run it again by - doing SOMETHING HERE. - - - This paragraph will describe all information required by the - setup assistant. It will include a long itemized list, and a - screenshot or two. - - 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/devel-action.sgml b/doc/C/devel-action.sgml deleted file mode 100644 index 5d40c78bf7..0000000000 --- a/doc/C/devel-action.sgml +++ /dev/null @@ -1,18 +0,0 @@ - - - Actions: Making Evolution Behave - - Build Actions - - How to create an action. - - - - - Using Actions - - How to use an action you or someone else has built. - - - - \ No newline at end of file diff --git a/doc/C/devel-component.sgml b/doc/C/devel-component.sgml deleted file mode 100644 index db4f93c27d..0000000000 --- a/doc/C/devel-component.sgml +++ /dev/null @@ -1,24 +0,0 @@ - - - Evolution Components - Build your own species - - Explain exactly what an Evolution Component is. - - - - Building Evolution Components - - Explain how to build them-- what resources are available, - what interfaces exposed. - - - - - Using Additional Evolution Components - - Once you've got one--either you've built it or borrowed it-- - you can use it. Here's how. - - - \ No newline at end of file diff --git a/doc/C/devel-script.sgml b/doc/C/devel-script.sgml deleted file mode 100644 index 74dbf161cd..0000000000 --- a/doc/C/devel-script.sgml +++ /dev/null @@ -1,17 +0,0 @@ - - - Scripting: Making Evolution Sit up and Beg - - Writing Scripts - - How to write scripts for Evolution. - - - - - Using Scripts - - How to use and install scripts for Evolution. - - - diff --git a/doc/C/evolution-guide.sgml b/doc/C/evolution-guide.sgml deleted file mode 100644 index 3e6b374fca..0000000000 --- a/doc/C/evolution-guide.sgml +++ /dev/null @@ -1,118 +0,0 @@ - - - - - - - - - - - - - - - - -]> - - - - - - A User's Guide to Evolution - AaronWeber - 2000Helix Code, Inc. - - - - PUT THE RIGHT LEGALNOTICE IN HERE - - - - - This is version 0.4 of the Evolution manual. - - - - - - - - - &PREFACE; - - - Using Evolution - A Guide for Everybody - - - 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-SETUP; - &USAGE-MAINWINDOW; - &USAGE-MAIL; - &USAGE-CONTACT; - &USAGE-CALENDAR; - &USAGE-SYNC; - - - - Configuring and Managing Evolution - A guide for Power Users and Administrators - - - 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; - - - Developing for Evolution - An Introduction for the Happy Few - - - There are three levels of developing for - Evolution. You can write actions. - You can write scripts. And you can write full-fledged - Evolution components. INSERT CONTENT: paragraph should describe the - differences. - - - - &DEVEL-ACTION; - &DEVEL-SCRIPT; - &DEVEL-COMPONENT; - - - &APX-BUGS; - &APX-AUTHORS; - &APX-FDL; - - diff --git a/doc/C/preface.sgml b/doc/C/preface.sgml deleted file mode 100644 index 05129eb550..0000000000 --- a/doc/C/preface.sgml +++ /dev/null @@ -1,149 +0,0 @@ - - - - Introduction - -
- What is Evolution, and What Can It Do for Me? - - The idea of evolution as a process of improvement and - development is a strong influence on the developers at Helix - Code. We named our groupware suite - "Evolution" because we knew that it would be able to survive - in the wilderness of the software marketplace for one reason: - it's better. - - - Evolution is a suite of groupware - applications within the GNOME desktop environment that you can - use 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. - - - We built Evolution with three groups of - people in mind: everyday users, system administrators, and - developers. - - - - - For everyday users, we made - Evolution easy to use without - sacrificing power. We made the interface familiar and - intuitive, but also allowed users to customize it to - their liking. We made the setup and configuration as - easy as possible. For any confusion, we wrote a - comprehensive manual and help system. - - - - - For administrators, we made sure - Evolution met and and - exceeded the standards set by currently available - groupware products, and we developed support for most - major network protocols so that it can integrate - seamlessly with existing hardware and network - environments. All of our efforts have made - Evolution both easy to use - and easy to support. - - - - - For developers, we built in - support for 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 offers developers - the ideal environment for cutting-edge application - development. - - - - - For all three groups, we did our best to ensure the - safety of data. - - - - - - In action, Evolution makes most - daily tasks faster, because we built it to work with you - instead of against you. 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 - much 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 is a DRAFT of the Evolution - User's Guide. Please send comments on it to - aaron@helixcode.com. Items that are known to - need action are indicated as such, often with notation like - (INSERT CONTENT HERE). If you have content to add, please - contact me. This paragraph will be removed in later versions - of the manual. - - - - - This book is divided into three 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 advanced users and administrators. If you are - a network administrator, you may find yourself referring to - this section frequently. The third section is a quick developer's guide, for power users and - hackers. If you want to add advanced scripting to - Evolution, write your own - embeddable components, or simply want to find out just how - powerful Evolution can be, this is - the section for you. - - - Throughout the book, you'll find examples, tips and warnings - to help you along. Most of them are decent, hardworking - pieces of information, and genuinely try to be helpful. Some - of the tips, entitled Bad Ideas, - are, in fact, out to trick you. Please don't follow their - advice, no matter how appealing it may sound. - - - Typographical conventions - - Some kinds of words are marked off with special typography. - It's listed below: - - Applications - Commands - Labelsfor menu items and buttons - Other text treatments - more info here - - - -
- \ No newline at end of file diff --git a/doc/C/usage-calendar.sgml b/doc/C/usage-calendar.sgml deleted file mode 100644 index 83e03c80c0..0000000000 --- a/doc/C/usage-calendar.sgml +++ /dev/null @@ -1,140 +0,0 @@ - - - The Evolution Calendar: Time-Tamer Extraordinaire - - To begin using the calendar, select - Calendar from the shortcut - bar. By default, the calendar starts in week view mode (IS - THIS TRUE? CHANGE TEXT TO FIT FEATURE). The calendar week 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. To do so, click BUTTONS SOMEWHERE. - - - Describe the less-obvious differences among the views of - time here. - - - - In addition, Evolution supports - Hebrew, Muslim, and other calendar formats. To switch to a - different calendar format, choose - GUIMENUITEM from the - GUIMENU. - - - Describe the ways that different calendars can work here, - and how the different calendars work together. - - - - 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. You can set overlapping events, although - Evolution will warn you about - trying to do two things at once. You can also set event - reminders 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 - - While looking at the calendar, select New - Appointment from the - MENU, or press - KEYSYM. The New - Appointment dialog will appear. (INSERT - DESCRIPTION OF INTERFACE HERE: Date, Time, Recurrence, - Reminders, and Tentative/Confirmed) - - - You can alter those settings later by clicking once on the - event in the calendar view to - select it, and then choosing Event - Properties from the - Settings menu. - - - - - Appointments for Groups - - If you have your calendar set up to work with other - calendars over a network, you can see when others are - available to meet with you. To browse other people's - calendars over your local network, do this: - - - In addition, you can use - Evolution to mark a meeting - request on another person's calendar. To do so, first - select New Appointment from the - MENU, or press KEYSYM - to bring up the new event window. - Then describe the event as you would any other. Before - you click OK, (INSERT DESCRIPTION - HERE...). Evolution will - automatically send email to each person on the request - list, notifying of the time and date of the meeting you - have requested with them. In addition, it will mark the - event on your calendar and on theirs as tentative, rather than - a confirmed, event. - - - To mark a tentative event as confirmed, click once on the - event in the calendar view to - select it, and then choose Event - Properties from the - Settings menu. In the Event - Properties dialog window, click the - "tentative" button to un-mark the event. (NOTE THAT this - feature may not at all exist!) - - - - - Scheduling privileges - - There are several levels of scheduling privileges. You - can set whether people can see your calendar, whether they - can request meetings or appointments, and whether they can - create appointments. This section may have to be deleted, - because I don't know if we are going to support privileges - at all. - - - - - - Organizing your Appointments - - Until I have Evolution running properly, - I have no idea how this sort of organization will actually work. - - - But this section will have at least two paragraphs, and - probably a screenshot. - - - diff --git a/doc/C/usage-contact.sgml b/doc/C/usage-contact.sgml deleted file mode 100644 index f88a3d5791..0000000000 --- a/doc/C/usage-contact.sgml +++ /dev/null @@ -1,283 +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, Evolution - allows easier updates than an actual paper book, and much - easier synchronization with handheld and remote devices. And - I doubt that you can take your little black book and make it - accessible to the rest of your office over a network. Since - Evolution supports most major - network protocols, including IMAP and - LDAP, it's easy to use over an - existing network. - - - Antother advantage of Evolution - is that the address book is integrated into 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, and when you get an email - with contact information in it, you can create a new address - card very quickly. In addition, searches, folders, and - vFolders all work in the same intuitive way they do in the - other components, so you don't have to learn another system - for similar tasks. - - - This chaper will cover the usage of the - Evolution contact manager, - including organizing large amounts of contact data, sharing - addresses over a network, and the automation - capabilities of the address book. Contact manager - configuration is addressed in . - - - - Getting Started With the Contact Manager - - - To start managing your contacts, click on - Contacts in the shortcut bar. - - - Describe the interface. Include the fact that the - whole book consists of a set of cards, organized into - folders. - - - - Creating, Deleting, and Adding Cards - - You can create a new card by pressing the New - Card button, or by pressing - KEYSYM. The New Card - window will appear. It has the following fields: - - - - Name: Enter the person's name here - - - - - - Address: - - - - Something - - - - Something - - - - - You can choose which fields an address card has, and create - new fields for cards. For example, - Evolution provides for two line - postal addresses by default, but you may have as many or as - few lines to an address as you wish. To change which - fields an address card has, choose DESCRIBE HERE HOW TO DO - THIS - - - - Quick ways to add cards - - You can add cards from within an email message or calendar - appointment. While looking at an email, right-click on - any email address or message, and choose - Create Card for this Address or - Create Card for this Senderfrom - the menu that appears. While looking at a calendar - appointment, right-click any email address, and choose - Create Card for this Address. - (NOTE that feature may change! unimplemented!) - - - - - You delete a card by pressing the Delete - Card button, or by dragging it into the trash folder. - - - - You can move cards around just as you would with email: - dragging and dropping works, as does right-clicking and - selecting Move from the menu - that appears. - - - - - 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. We'll go over categories in a bit. - - - Another useful UNIMPLEMENTED - Evolution feature is its ability - to recognize when people live together. If two people in - your contact manager share an address, and you change the - address for one of them, Evolution will ask you if you wish - to change the address for both of them, or just for one. - - - - Groups of contacts - - Evolution lets you put cards - into folders, mark them as members of different groups, - and search through them in a variety of ways. This - section will describe how to organize and find contact - information using Evolution. - CHANGE THIS paragraph: it needs a great deal of work. - - - - Grouping with Folders - - The simplest way to group address cards is to use - folders. By default, cards start in the - Contacts folder. You can create - more folders inside that one, or create other address - book folders as well. Each card must be in one and only - one folder. - - - To create a new folder, do this: - - - To put a card into a folder, do this: - - - - - 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, do this: - - - Then, you can refer to all the cards in that category - by: - - - If the default categories don't suit you, you can add - your own. Here's how: - - - - - - - Sharing your cards (Or 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 - - I want to schedule a meeting with someone at Company - X, but I'm not sure who to talk to there. Our - corporate network has an address card that states our - contacts there, so I know whom to call. Since we also - share the calendars, I know that Deanna has already - scheduled a meeting with them next Thursday, and I can - just ask her to bring up my concerns at the meeting. - - - - - Of course, you don't want to share all of your cards— - why overload the network with a list of babysitters, or - tell everyone on your network 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, select . The - Sharing will pop up. It contains: - - - - - - Automating the Contact Manager - - The Evolution contact manager - can perform a wide variety of tasks for you. From speeding - up basic tasks like adding a new address card to managing - mailing lists, you'll find that the contact manager is more - than a mere address book. - - - Send me a card: Adding New Cards Quickly - - When you get information 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 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 by doing SOMETHING HERE. - 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. - - - - Map It! and other extra features - - Need a map or directions? Click - MapIt from within the contact - manager, and Evolution will - map the address for you online. - - - - \ No newline at end of file diff --git a/doc/C/usage-mail.sgml b/doc/C/usage-mail.sgml deleted file mode 100644 index c81c384cfb..0000000000 --- a/doc/C/usage-mail.sgml +++ /dev/null @@ -1,644 +0,0 @@ - - - Evolution Mail: Witty Phrase to Come Later - - An Overview of the Evolution Mailer - - Email is an integral part of life these days, and - Evolution mail is here to help - you keep track of it. Evolution - email is like other email programs in all the ways you would - hope: (INSERT GOOD SIMILARITIES). - - - However, Evolution has some - important differences. First, it's built to handle very - large amounts of mail without slowing down or crashing. We - had high mail volumes in mind when we designed our filtering and - searching - functions. 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. - - - - - 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. A preview of 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. - - - Go ahead and right-click on the message, and select - Delete Message from the menu - that appears. The message will move into the - Trash folder. If you want to keep - it, you can open the Trash folder - and drag the message back to your - Inbox. The trash will be - automatically emptied the next time you quit - Evolution. (FEATURE - UNIMPLEMENTED! Text may change to fit featureset) - - - -
- Evolution Mail - - Evolution Mail - - - -
- - - - - - Getting Mail - - To check your email, just click Send and - Receive in the toolbar. - Evolution will download your - mail for you and send any mail you've marked ready to - send. New mail will appear in your - Inbox and also in the - Today View. - - - If you get an error message, you probably need to - change your network preferences. To do that, you can run - the setup assistant again, have a look at , or ask your system - administrator. - - - - Attachments, HTML Mail, and Live Documents - - If you receive a file attached to an email, - Evolution will ask where you - want to put it. Once you've downloaded it, you can - open, move, copy, or execute those files just like any - others, 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. - - - It can also display live - documents, which have scripted or - executable contents— for example, a working - spreadsheet page or a chess game. - - - Bad Idea - - When someone you don't know sends you an attached - program, go ahead and run it. Set your preferences to - always run live documents when you recieve them, too. - Everybody knows all that virus stuff is just a Windows - problem. - - - - - - - Writing and Sending Mail - - You can start writing a new - email message by selecting New - Mail from the File Menu, - or by pressing Ctrl-N. 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 - message in the Message: field, and - press Send and Receive. 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. - Then, when you press Send & - Receive, 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 . - - - - - - There is more to sending mail, though. In the - next few sections, we'll go over 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. (INSERT description of UI for this - feature, once it is decided upon). 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. (QUESTION: will users be able to drag & drop - address cards to send email?). For more information - about using email together with the contact manager and - the calendar, see and . - - - 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 - - Say, for example, 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 - recieved the message, and know that they 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 addresses in the - BCc: field will receive copies of - the message, but they will not receive the list of the - other recipients' addresses, nor will other recipients - know that they have recieved the message. When I send a - generic message to all my friends and I want them to - think I've written a personalized email to every one of - them, I put them all in the BCc: - list. - - - - - 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, or use the - REPLY COMBO hot key. A window like - the New Message window will - appear, but the subject will already be present— - typically, your new message will have 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 may be inserted into - the new message, with the > character 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 select one of the items under the - Reply-To submenu on the - MENU menu. This will allow you to - choose one or several of the other message recipients in - addition to the person who originally sent you the - message. - - Using the Reply-To feature - - Returning to the previous example, the client can - decide whether to reply just to Susan, just to Tim, - or to both of them by selecting a menu item, rather - than by cutting and pasting the email addresses. If - there are large numbers of people in the Cc: fields, - this can save substantial amounts of time. - - - - - - - - Embellishing that email - - Evolution allows you to - make your email more attractive in a number of ways. You - can send messages formatted with HTML, attach any sort - of file to them, and even include live documents, like - spreadhseets or chess games. This section will tell - you how. - - - - - Colors, pictures, and fonts with HTML Mail - - Most email messages are sent as plain text, but they - can also be sent as HTML, which means they can include - color, text style, and other formatting information. - Evolution will read and display HTML properly without - trouble, and also allows you to send outgoing - email messages as HTML. To send an HTML message, just - use the composition toolbar to add formatting; - your message text will appear formatted in the composer - window, and the message will be sent as HTML. - - - A Technical note on HTML Tags - - Any text, including HTML tags, entered into the - message composition window is assumed to be plain - text. If you enter HTML directly into the - composer— say, <BR>Bold Text</BR>, - the the composer will assume you meant exactly that, - and not "make this text bold," as a HTML composition - tool would. For the technically inclined, that - means that when the text <BR> is sent as HTML, it - will be converted to the string - &lt;BR&gt;. - - - - 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 the - default in Evolution is - plain text. If you have an address book entry for - someone who does not wish to receive HTML-enhanced - mail, you can note that preference in their address - card. The mailer will automatically strip the HTML - tags from any messages you send to that address. - - - - - Attachments - - If you want to attach a file to your email message, - you can do so by . If - your recipients can read HTML mail, you can put an - image inside the mail by dragging the file into the - composer window, or by selecting (INSERT DESCRIPTION - HERE) (IS THIS CORRECT?). Still, unless you know what - email client the recipient is using, it's best to send - a message or attachment in the simplest manner - possible. - - - - - - Later versions of Evolution - will allow you to enliven your email with almost any - sort of document, and even with entire - applications. At this point, however, I don't know how - that will work. - - - - - - Forwarding Mail - - Forward is useful if you have - received a message and you think someone else would like - to see it, or if you get a message intended for someone - else. You can forward a message as an attachment to a - new message (the default way of forwarding) 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 entire message you received, - unaltered. 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, first make sure it is selected by - clicking it once in the message list. Then, press - Forward on the toolbar, or select - SOMETHING. To forward a message inline instead of as an - attachment, DO SOMETHING ELSE. 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 and - Receive. To forward it - inline instead of attached, - select Forward Inline from - the Message menu. - - - - Seven Tips for Email Usage - - I started with ten, but four were "Don't send - spam." - - - - 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 them to. - - - - - - Check your spelling and use complete sentences. - - - - - - Don't send nasty emails (flames). If you get one, - don't write back. - - - - - - Don't send spam or forward chain mail. If you - must, verify any rumors, and make sure the - message doesn't have multiple layers of email - quotation symbols (>) indicating multiple - layers of careless inline forwarding. - - - - - - 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, - and Evolution has the tools to - help you do it. - - - - Getting Organized with Folders - - You can create new folders by selecting - ITEM from the - MENU, or by pressing - COMBO. (Will there be a dialog box to - determine name and location? Must wait for feature to - describe) The new folders will appear in the - tree view, and you can drag them - wherever you want to relocate them. You can move messages - into them by dragging, or by selecting them and choosing - ITEM from the - MENU. An email message can be in only - one folder at a time, just like real mail in real folders. - This is also the case for folders of address cards and calendar - information. - - - - - Searching for Messages - - Because Evolution automatically - creates an index of every email you send or receive, it - can search through your old messages and present you with - results very quickly. You can search for messages by - author, subject, keyword, or headers. (INSERT descriptons - of what those terms mean) - - - (INSERT the way one creates a search and so forth) - - - - - Getting Really Organized with Virtual Folders - - If you find yourself performing a search frequently, you - can save it as 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 looks and acts a lot like a folder, but it's - actually a saved search that you can access in most of the - same ways you would a regular folder. The one important - differences between them is that a conventional folder - actually contains messages, but a vFolder is a view of - messages that may be in several different folders. This - means that while a message may fall into several vFolders, - it can be in only one conventional folder. Also, it means - that you cannot remove a message from a vFolder unless you - delete it, and you cannot add a message to a vFolder - unless you change the vFolder's search criteria. - - - 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 it actually exists in 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. 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 larger - the system, the less you can afford that sort of - confusion. 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, by doing (INSERT - PROCESS HERE). 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. - - (INSERT SCREENSHOT HERE) - - - - - - - Staying organized: Mail Filters in Evolution - - Filters sort your email for you as it arrives in your - Inbox, so you don't have to sort them all yourself. - People who subscribe to multiple mailing lists find - filters especially helpful to sort personal from - list-related mail. To create a filter, go to your - Inbox. Then select BLAH BLAH BLAH. - This will open the filters window. - - - - The filters window contains the - following items: - - - - Two Notable Filter Features - - - Any email that does not meet filter - action criteria remains in the Inbox. - - - If you move a folder, your filters - will follow it. - - - - - - - diff --git a/doc/C/usage-mainwindow.sgml b/doc/C/usage-mainwindow.sgml deleted file mode 100644 index 8470189977..0000000000 --- a/doc/C/usage-mainwindow.sgml +++ /dev/null @@ -1,214 +0,0 @@ - - - - The Main Window: Evolution Basics - - After Evolution starts up, you will - see the main window, which looks a lot - like in . On the left of - the main window are the - shortcut bar and the - tree-view. 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 a welcome message. - - - - - -
- Evolution Main Window - - 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, or without the shortcut - bar or tree view. - - - - - - The Shortcut Bar - - The buttons in the shortcut bar give - you quick access to the different functions that - Evolution provides. - - - The buttons in the shortcut bar are: - - - - Today, which will bring up a summary - of any new messages you've recieved, along with the tasks and - appointments you have lined up for today. - - - - - - Inbox, which 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. - - - - - - The Calendar, which can store - appointments for you. Connected to a network, you - can use it to keep a group of people on schedule and - up to date. - - - - - - The Contacts tool 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. - - - - - - The Tasks tool combines a "to - do" list with reminders to help you keep track of - daily events. - - - - - Notes is your catch-all - notepad: write haiku, take down - messages from phone conversations, or keep small - things organized. - - - - - - - - If you prefer to use a keyboard shortcut, or hot - key, you can use those instead. They're - shown... (INSERT DESCRIPTION) 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 Hide/Show Shortcut - Bar from the MENU menu. - - - - - The Tree View - - The tree view is the most comprehensive way to - get to your information: it can show you everything you've - stored with Evolution - appointments, address cards, emails, and so forth. - - The tree view display presents your - data like a file tree— it - starts small at the top, and branches downwards. There are a - few folders you will always see, because they're at the top. - On my computer, they are: (ch. to itemizedlist w/descriptions?) - - Local Mail - Remote Mail - Address Book - Calendar - Trash - . - - - - 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: - - Something - Something - Something - . - - - - Context-Sensitive Help - - 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, right-clicking and - choosing Help is a good way to - find out. - - - - - If a folder has other folders in it, there will be a plus - sign next to it. Click on the plus sign, and you will see - the other folders inside. This may change in the future to - something more attractive, like triangles that drop down as - you click on them to display the rest of the tree. - - - - Any time new information arrives in a folder, that folder - will be highlighted, or its label displayed as bold - text. You can learn more about customizing - Evolution alerts and appearance - in . - - - - (CHANGE that title! THIS SECTION BELONGS SOMEWHERE ELSE!) - You can drag the folders inside the tree view to change - their order or put one folder inside another. To delete a - folder, you can drag it into the trash folder. The same - goes for individual messages, appointments, and address - cards, whether they're in the tree - view or not: drag them where you want them, and - they will go there. (IS THIS TRUE?) - - - You can also use the right-click menu to - move, rename, and delete folders. - Delete function from the - right-click menu. - - - Once you've familiarized yourself with the main - window you can start doing things with it. - We'll start with email: you've got a letter waiting for you - already. - - - \ No newline at end of file diff --git a/doc/C/usage-setup.sgml b/doc/C/usage-setup.sgml deleted file mode 100644 index 1290b000bb..0000000000 --- a/doc/C/usage-setup.sgml +++ /dev/null @@ -1,46 +0,0 @@ - - A Quick Start - - Start Evolution by selecting - Evolution from the - Applications of the Main - Panel Menu, or by typing - evolution at the command-line. If this is - the first time you have run - Evolution, you'll be asked if you - want help setting up your email preferences. If you don't - plan to use email, or if you'd rather configure your email - preferences later, select No, and it - will go away. You can configure your email preferences later - by selecting SOMETHING from SOME MENU. - - - If you answer yes, it will guide you through the network - configuration process. It will ask you for the following - information: (FLESH OUT THIS LIST!) - - - Name— Your full name: eg. William Blake - - - - UserName— Your user or account name: eg. wblake - - - Type of Server— POP vs. SMTP vs.... - - - - - TERM— DESCRIPTION - - - - - - TERM— DESCRIPTION - - - - - \ No newline at end of file diff --git a/doc/C/usage-sync.sgml b/doc/C/usage-sync.sgml deleted file mode 100644 index f28ebc10cc..0000000000 --- a/doc/C/usage-sync.sgml +++ /dev/null @@ -1,19 +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 all you need to do is 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 f20a7856f7..0000000000 --- a/doc/ChangeLog +++ /dev/null @@ -1,84 +0,0 @@ -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/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 v1.2.3