diff options
Diffstat (limited to 'help')
107 files changed, 0 insertions, 15704 deletions
diff --git a/help/.cvsignore b/help/.cvsignore deleted file mode 100644 index 282522db03..0000000000 --- a/help/.cvsignore +++ /dev/null @@ -1,2 +0,0 @@ -Makefile -Makefile.in diff --git a/help/C/.cvsignore b/help/C/.cvsignore deleted file mode 100644 index 2f4c48adbf..0000000000 --- a/help/C/.cvsignore +++ /dev/null @@ -1,9 +0,0 @@ -Makefile -Makefile.in -evolution-guide -evolution-guide.junk -evolution-guide.log -evolution-guide.ps -evolution-guide.dvi -evolution-guide.tex -fig/*.eps
\ No newline at end of file diff --git a/help/C/Makefile.am b/help/C/Makefile.am deleted file mode 100644 index 15f1e047b6..0000000000 --- a/help/C/Makefile.am +++ /dev/null @@ -1,59 +0,0 @@ -evolution_helpdir = $(datadir)/gnome/help/evolution/C - -SGML_FILES = \ - apx-authors.sgml \ - apx-bugs.sgml \ - apx-fdl.sgml \ - apx-gloss.sgml \ - config-prefs.sgml \ - config-setupassist.sgml \ - config-sync.sgml \ - evolution-guide.sgml \ - preface.sgml \ - usage-calendar.sgml \ - usage-contact.sgml \ - usage-mail.sgml \ - usage-mainwindow.sgml \ - usage-sync.sgml - - -EXTRA_DIST = \ - $(SGML_FILES) - -all: evolution-guide - -evolution-guide: $(SGML_FILES) - -db2html evolution-guide.sgml - -dist-hook: - mkdir $(distdir)/evolution-guide - -cp evolution-guide/*.html evolution-guide/*.css $(distdir)/evolution-guide - mkdir $(distdir)/fig - -cp fig/*.png $(distdir)/fig - mkdir $(distdir)/evolution-guide/stylesheet-images - -cp evolution-guide/stylesheet-images/* $(distdir)/evolution-guide/stylesheet-images - -install-data-local: evolution-guide - $(top_srcdir)/mkinstalldirs $(DESTDIR)$(evolution_helpdir) - -for file in $(srcdir)/evolution-guide/*.html $(srcdir)/evolution-guide/*.css; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/$$basefile; \ - done - - $(top_srcdir)/mkinstalldirs $(DESTDIR)$(evolution_helpdir)/fig - -for file in $(srcdir)/fig/*.png; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/fig/$$basefile; \ - done - - $(top_srcdir)/mkinstalldirs $(DESTDIR)$(evolution_helpdir)/stylesheet-images - -for file in $(srcdir)/evolution-guide/stylesheet-images/*; do \ - basefile=`basename $$file`; \ - $(INSTALL_DATA) $$file $(DESTDIR)$(evolution_helpdir)/stylesheet-images/$$basefile; \ - done - -evolution.ps: evolution.sgml - -db2ps $< - -evolution.rtf: evolution.sgml - -db2rtf $< diff --git a/help/C/apx-authors.sgml b/help/C/apx-authors.sgml deleted file mode 100644 index 89f0dd6bc5..0000000000 --- a/help/C/apx-authors.sgml +++ /dev/null @@ -1,75 +0,0 @@ - <appendix id="authors"> - <title>Authors</title> - <para> - <application>Evolution</application> was written by: -<simplelist> - <member>Seth Alves: <email>alves@helixcode.com</email></member> - <member>Anders Carlsson: <email>andersca@gnu.org</email></member> - <member>Damon Chaplin: <email>damon@helixcode.com</email></member> - <member>Clifford R. Conover: <email>rusty@zootweb.com</email></member> - <member>Miguel De Icaza: <email>miguel@helixcode.com</email></member> - <member> Radek Doulik: <email>rodo@helixcode.com</email></member> - <member>Arturo Espinoza: <email>arturo@nucleu.unam.mx</email></member> - <member>Larry Ewing: <email>lewing@helixcode.com</email></member> - <member>Bertrand Guiheneuf: <email>bertrand@helixcode.com</email></member> - <member>Tuomas Kuosmanen: <email>tigert@gimp.org</email></member> - <member>Christopher J. Lahey: <email>clahey@helixcode.com</email></member> - <member>Matthew Loper: <email>matt@loper.org</email></member> - <member>Federico Mena: <email>federico@helixcode.com</email></member> - <member>Eskil Heyn Olsen: <email>deity@eski.dk</email></member> - <member>Nat Friedman: <email>nat@helixcode.com</email></member> - <member>Ettore Perazzoli: <email>ettore@helixcode.com</email></member> - <member>Jeffrey Stedfast: <email>jeff@helixcode.com</email></member> - <member>Russell Steinthal: <email>rms39@columbia.edu</email></member> - <member>Peter Teichman: <email>peter@helixcode.com</email></member> - <member>Chris Toshok: <email>toshok@helixcode.com</email></member> - <member>Peter Williams: <email>peter@newton.cx</email></member> - <member>Dan Winship: <email>danw@helixcode.com</email></member> - <member>Michael Zucchi: <email>notzed@helixcode.com</email></member> -</simplelist> -and other dedicated GNOME programmers. -</para> - <para> - The <application>Evolution</application> code owes a great debt - to the <application>GNOME-pim</application> and - <application>GNOME-Calendar</application> applications, and to - <application>KHTMLW</application>. The developers of - <application>Evolution</application> acknowledge the efforts - and contributions of all who worked on those projects. - </para> - - <para> - For more information please visit the - <application>Evolution</application> <ulink - url="http://www.helixcode.com/apps/evolution.php3" - type="http">Web page</ulink>. Please send all comments, - suggestions, and bug reports to the <ulink - url="http://bugs.gnome.org" type="http">GNOME bug tracking - database</ulink>. Instructions for submitting bug reports can be - found on-line at <ulink - url="http://bugs.gnome.org/Reporting.html" type="http"> - http://bugs.gnome.org/Reporting.html</ulink>. You can also use - command <command>bug-buddy</command> for submitting bug reports. - </para> - <para> - This manual was written by Aaron Weber - (<email>aaron@helixcode.com</email>) and Kevin Breit - (<email>battery841@mypad.com</email>) 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 - <email>docs@gnome.org</email>. You can also add your comments - online by using <ulink type="http" - url="http://www.gnome.org/gdp/doctable/">GNOME Documentation - Status Table</ulink>. - </para> - <!-- For translations: uncomment this: <para> Latin translation - was done by ME (<email>MYNAME@MYADDRESS</email>). Please send - all comments and suggestions regarding this translation to - SOMEWHERE. </para> --> - </appendix> - - - - - diff --git a/help/C/apx-bugs.sgml b/help/C/apx-bugs.sgml deleted file mode 100644 index e4a96a8155..0000000000 --- a/help/C/apx-bugs.sgml +++ /dev/null @@ -1,23 +0,0 @@ - <appendix id="bugs"> - - <title>Known bugs and limitations</title> - <abstract> - <para> - This appendix describes known bugs and limitations of - <application>Evolution</application>. Please use the GNOME - <application>Bug Report Tool</application> (known as - <command>bug-buddy</command> at the command line) if you find one - we have not listed. - </para> - </abstract> - - <para> - Evolution is still beta software, so the bug tracking is best - left to the bugzilla system and to the programmers. However, - there are a number of limitations that will not be addressed - before version 1.0. The most notable are: Import of Microsoft - Outlook .pst files, and compatibility with the Microsoft - Exchange protocol. - </para> - </appendix> - diff --git a/help/C/apx-gloss.sgml b/help/C/apx-gloss.sgml deleted file mode 100644 index 129020aa3d..0000000000 --- a/help/C/apx-gloss.sgml +++ /dev/null @@ -1,459 +0,0 @@ -<glossary id="apx-gloss"> - - <title>Glossary</title> - - <glossentry id="attachment"> - <glossterm>Attachment</glossterm> - <glossdef> - <para> - Any file sent along with an email. Attachments may be embedded in - a message or appended to it. - </para> - </glossdef> - </glossentry> - -<glossentry id="automatic-indexing"> - <glossterm>Automatic Indexing</glossterm> - <glossdef> - <para> - Pre-sorting procedure that allows - <application>Evolution</application> to refer to data quickly. - It enables faster searches and decreases memory usage for - data displays. - </para> - </glossdef> - </glossentry> - - <glossentry id="bcc"> - <glossterm>Bcc (Blind Carbon Copy)</glossterm> - <glossdef> - <para> - A way of addressing a message. Bcc is used to send a group of - people an e-mail, while hiding their names and addresses from each - other. - </para> - </glossdef> - </glossentry> - - <glossentry id="cc"> - <glossterm>Cc (Carbon Copy)</glossterm> - <glossdef> - <para> - Carbon-copies are used to send a 3rd party a copy of the e-mail, - so they an keep up to date on a conversation, without being in the - To: list. - </para> - </glossdef> - </glossentry> - - <glossentry id="conduit"> - <glossterm>Conduit</glossterm> - <glossdef> - <para> - A synchronization conduit is a small application which controls - the transfer of data between a handheld device and a desktop - computer. - </para> - </glossdef> - </glossentry> - - - <glossentry id="druid"> - <glossterm>Druid</glossterm> - <glossdef> - <para> - A tool which guides a user through a series of steps, usually to - configure or set up a program. Equivalent to "Assistant" and - "Wizard." - </para> - </glossdef> - </glossentry> - -<glossentry id="emoticon"> - <glossterm>Emoticon</glossterm> - <glossdef> - <para> - Also called "smileys," emoticons are the little sideways faces made - of colons and parentheses which people use to convey emotion in email. - Examples: :-) or ;( . - </para> - </glossdef> - </glossentry> - - <glossentry id="evolution"> - <glossterm>Evolution</glossterm> - <glossdef> - <para> - <application>Evolution</application> is the <acronym> GNOME - </acronym> groupware application. - </para> - </glossdef> - </glossentry> - - <glossentry id="execute"> - <glossterm>Execute</glossterm> - <glossdef> - <para> - To run a program. Any file that can be run is called an - executable. <application>Evolution</application> can download - executable attachments, but before they can be run, the files must - be marked as executable with a shell or file manager. This - security precaution prevents the automatic or accidental execution - of malicious programs. For more information on executables and file - permissions, see the documentation for your file manager or shell. - </para> - </glossdef> - </glossentry> - - - <glossentry id="filetree"> - <glossterm>File Tree</glossterm> - <glossdef> - <para> - A way of describing a group of files on a computer. With the - perversity typical of computer (and especially Unix and Linux) - nomenclature, the top of the tree is called the root directory, - and denoted by <systemitem><filename>/</filename></systemitem>. - The rest of the "branches" spread downwards from the root. Don't - confuse the root directory with the <systemitem>root</systemitem> - account, or root's home directory, - <systemitem><filename>/home/root</filename></systemitem>. - </para> - </glossdef> - </glossentry> - - <glossentry id="filter"> - <glossterm>Filter</glossterm> - <glossdef> - <para> - Within <application>Evolution</application>, a filter is a method - of sorting mail automatically. You can create filters to perform - one or more actions on a message that meets any (or all) of a wide - range of criteria. - </para> - </glossdef> - </glossentry> - - <glossentry id="forward"> - <glossterm>Forward</glossterm> - <glossdef> - <para> - the user can send a third party a message - which was sent to the user originally. - </para> - </glossdef> - </glossentry> - - <glossentry id="groupware"> - <glossterm>Groupware</glossterm> - <glossdef> - <para> - Groupware is a term describing an application which helps groups - of people work together. Typically, a groupware application will - have several productivity features built into one program. - </para> - </glossdef> - </glossentry> - - <glossentry id="haiku"> - <glossterm>Haiku</glossterm> - <glossdef> - <para> - A traditional Japanese form of poetry. The poems are three lines - long, with first and last lines having five syllables, and the - second line seven syllables. - </para> - </glossdef> - </glossentry> - - <glossentry id="html"> - <glossterm>HTML</glossterm> - <glossdef> - <para> - Hyper-text Markup Language(<acronym>HTML</acronym>) is a language - for describing page layout in electronic documents like web pages, - help files, and email messages. HTML can be used in email and - news posts to insert images and apply text treatments. - </para> - </glossdef> - </glossentry> - - <glossentry id="hot-key"> - <glossterm>Hot Key</glossterm> - <glossdef> - <para> - Hot-keys are keyboard combinations used to do actions on a - computer instead of using the mouse to do the same action. - Hot-keys can speed up computer usage. - </para> - </glossdef> - </glossentry> - - <glossentry id="ical"> - <glossterm>iCal</glossterm> - <glossdef> - <para> - <application>iCal</application> is the program which - <application>Evolution</application> uses to manage the calendar - section. - </para> - </glossdef> - </glossentry> - - <glossentry id="imap"> - <glossterm>IMAP</glossterm> - <glossdef> - <para> - Depending upon whom you ask, IMAP stands for the Internet Mail - Access Protocol, or the Interim Mail Access Protocol. Whatever it - stands for, it allows access to email which is typically (although - not always) stored remotely on a server rather than on a local - hard disk. Often contrasted with <glossterm>POP</glossterm>. - This will not be on the test. - </para> - </glossdef> - </glossentry> - - - <glossentry id="inline"> - <glossterm>Inline</glossterm> - <glossdef> - <para> - Displayed as part of a message or other document, rather than - attached as a separate file. Contrast with <glossterm - linkend="attachment">Attachment</glossterm>. - </para> - </glossdef> - </glossentry> - - <glossentry id="ldap"> - <glossterm>LDAP</glossterm> - <glossdef> - <para> - LDAP, the Lightweight Directory Access Protocol, allows a client - to search through a large database of addresses, phone numbers, - and people stored on a server. - </para> - </glossdef> - </glossentry> - - <glossentry id="mail-client"> - <glossterm>Mail Client</glossterm> - <glossdef> - <para> - A mail client is the application with which a person reads and - sends e-mail. Its counterparts are the various types of mail - servers, which handle user authentication and direct messages from - sender to recipient. - </para> - </glossdef> - </glossentry> - - - <glossentry id="minicard"> - <glossterm>Minicard</glossterm> - <glossdef> - <para> - A format for the display of contact data. Similar in appearance - to a small business card. - </para> - </glossdef> - </glossentry> - - <glossentry id="nautilus"> - <glossterm>Nautilus</glossterm> - <glossdef> - <para> - <application>Nautilus</application> is the next generation file - manager for <acronym>GNOME</acronym> being written by Eazel. - </para> - </glossdef> - </glossentry> - - <glossentry id="nickname"> - <glossterm>Nickname</glossterm> - <glossdef> - <para> - An alias for an e-mail address. - </para> - </glossdef> - </glossentry> - - <glossentry id="pop"> - <glossterm>POP</glossterm> - <glossdef> - <para> - POP, the Post Office Protocol, is a mechanism for email - transport. In contrast to IMAP, it is used only to get mail from - a server and store it locally on your hard disk. - </para> - </glossdef> - </glossentry> - - <glossentry id="protocol"> - <glossterm>Protocol</glossterm> - <glossdef> - <para> - An agreed-upon method of communication, especially one for - sending particular types of information between computer systems. - Examples include POP (Post Office Protocol), for email, and HTTP - (HypterText Transfer Protocol), for web pages. - - </para> - </glossdef> - </glossentry> - - - <glossentry id="regular-expression"> - <glossterm>Regular Expression</glossterm> - <glossdef> - <para> - A regular expression, or "regex", is a way of describing a - string of text using metacharacters or wild-card symbols. For - example, the statement <userinput>fly.*so[a|u]p</userinput> means - "any phrase beginning with 'fly' and ending in 'soup' or - 'soap'". If you searched for that expression, you'd find both - "fly in my soup" and "fly in my soap." There's not room here to - go into depth, but if you want, have a look at the documentation - for the <command>grep</command> command. - </para> - </glossdef> - </glossentry> - - <glossentry id="script"> - <glossterm>Script</glossterm> - <glossdef> - <para> - A program written in an interpreted (rather than compiled) - language. Often used as a synonym for "macro," to denote a series - of pre-recorded commands or actions within an application. - </para> - </glossdef> - </glossentry> - - <glossentry id="sendmail"> - <glossterm>Sendmail</glossterm> - <glossdef> - <para> - As its name implies, <application>sendmail</application> is a - program which sends mail. <application>Evolution</application> - can use it instead of <glossterm>SMTP</glossterm>; some people - prefer it because it offers more flexibility, but is more - difficult to set up. - </para> - </glossdef> - </glossentry> - - - <glossentry id="shortcut-bar"> - <glossterm>Shortcut Bar</glossterm> - <glossdef> - <para> - A portion of <application>Evolution</application> which offers - users fast access to the most frequently used portions of the - application. - </para> - </glossdef> - </glossentry> - - <glossentry id="signature"> - <glossterm>Signature</glossterm> - <glossdef> - <para> - In email terms, a signature is a piece of text placed at the end - of every email sent, like a hand-written signature at the bottom - of a written letter. A signature can be anything from a favorite - quotation to a link to a web page; courtesy dictates that it be - fewer than four lines long. - </para> - </glossdef> - </glossentry> - - <glossentry id="SMTP"> - <glossterm>SMTP</glossterm> - <glossdef> - <para> - This is the most common way of transporting mail messages from - the client's computer (you) to the server. SMTP stands for - Simple Mail Transfer Protocol. - </para> - </glossdef> - </glossentry> - - <glossentry id="spam"> - <glossterm>Spam</glossterm> - <glossdef> - <para> - Useless, unsolicited e-mail. Spam normally comes in forms of - chain letters and advertisements for unscrupulous or clueless - companies. Messages that are merely useless are called "opt-in - newsletters." - </para> - </glossdef> - </glossentry> - - - <glossentry id="tooltip"> - <glossterm>Tool-Tip</glossterm> - <glossdef> - <para> - A small box of explanatory text which appears when the mouse - pointer is held motionless over a button or other interface - element. - </para> - </glossdef> - </glossentry> - - - - - <glossentry id="virus"> - <glossterm>Virus</glossterm> - <glossdef> - <para> - A malicious program which inserts itself into others so that it will be - executed, allowing it to spread to still more programs and other computers. - A virus can cause substantial damage by clogging networks or disk drives, - deleting files, or opening security holes. - </para> - </glossdef> - </glossentry> - - <glossentry id="vcard"> - <glossterm>vCard</glossterm> - <glossdef> - <para> - A file format for the exchange of contact information. When you - get an address card attached to an email, it's probably in vCard - format. Not to be confused with <glossterm - linkend="vfolder">vFolder</glossterm>. - </para> - </glossdef> - </glossentry> - - <glossentry id="vfolder"> - <glossterm>vFolder</glossterm> - <glossdef> - <para> - An email organization tool. vFolders allows you to create a folder - that contains the results of a complex search. Folder contents are - are updated dynamically. - </para> - </glossdef> - </glossentry> - -</glossary> - - - - - - - - - - - - - - diff --git a/help/C/config-prefs.sgml b/help/C/config-prefs.sgml deleted file mode 100644 index 157b61e1cc..0000000000 --- a/help/C/config-prefs.sgml +++ /dev/null @@ -1,646 +0,0 @@ -<!-- <!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> --> -<chapter id="config-prefs"> - - <title>Advanced Configuration</title> - <para> - Perhaps your mail server has changed names. Perhaps you've - grown tired of a certain layout for your appointments. - Whatever the reason, you want to change your - <application>Evolution</application> settings. This chapter - will tell you how to do just that. - </para> - - <sect1 id="config-prefs-mail"> - <title>Mail Settings</title> - <para> - To change your mail settings, select <menuchoice> - <guimenu>Settings</guimenu> <guimenuitem>Mail - configuration</guimenuitem></menuchoice> in the Inbox. This - will open the <interface>mail preferences window</interface>, - illustrated in <xref linkend="config-prefs-mail-fig">. Mail - preferences are separated into several categories: - <variablelist> - <varlistentry> - <term><guilabel>Identities</guilabel></term> - <listitem> - <para> - This allows you to create and alter one or more - identities for your email. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Sources</guilabel></term> - <listitem> - <para> - This tab lets you tell - <application>Evolution</application> where to get the - mail sent to you, and how to get it. - </para> - </listitem> - </varlistentry> - <varlistentry> - - <term><guilabel>Mail Transport</guilabel></term> - <listitem> - <para> - This tab lets you tell - <application>Evolution</application> how to send mail. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>News Servers</guilabel></term> - <listitem> - <para> - If you would like to use - <application>Evolution</application> to read newsgroups, - you can specify your news server preferences here. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Other</guilabel></term> - <listitem> - <para> - Miscellaneous mail and news settings, such as HTML - handling preferences, and how long - <application>Evolution</application> should wait before - marking a message read. - </para> - </listitem> - </varlistentry> - </variablelist> - - </para> - - <!-- ==============Figure===================== --> - <figure id="config-prefs-mail-fig"> - <title>Mail Preferences Dialog</title> - <screenshot> - <screeninfo>Setting mail preferences</screeninfo> - <graphic fileref="fig/config-mail" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - <!-- ==============End of Figure================--> - - - <sect2 id="config-prefs-mail-identity"> - <title>Identity Settings</title> - <para> - If you have only one email account, or send email from only - one address, you will only need to configure one identity. If - you want, however, you can have multiple identities. This - can be useful if you want to keep personal and professional - email separate, or if you wear several hats at work. - - </para> - <para> - To add a new identity, simply click - <guibutton>Add</guibutton>. To alter an existing identity, - click on it in the <guilabel>Identity</guilabel> tab of the - <interface>Preferences</interface> window, and then click - <guibutton>Edit</guibutton>. - </para> - - <para> - <application>Evolution</application> will then present you - with a dialog box containing four fields: - <itemizedlist> - <listitem> - <para> - <guilabel>Full Name:</guilabel> by default, this is the - same name as the full name described in your user - account on your computer. You can select another if you - wish. - </para> - </listitem> - <listitem> - <para> - <guilabel>Email address:</guilabel> Enter your email - address in this space. - </para> - </listitem> - <listitem> - <para> - <guilabel>Organization:</guilabel> If you send email as - a representative of a company or other organization, - enter its name here. - </para> - </listitem> - <listitem> - <para> - <guilabel>Signature file:</guilabel> You may choose a - small text file to be appended to every message that you - send. Typically, signature files include address or - other contact information, or a favorite quotation. - It's good form to keep it to four lines at the maximum. - </para> - </listitem> - </itemizedlist> - </para> - </sect2> - - <sect2 id="config-prefs-mail-network"> - <title>Network Settings</title> - <para> - In order to send mail with - <application>Evolution</application>, you need to connect to - your network. To do that, you'll need to know your user name - and password, what sort of mail sending and receiving - protocols your network uses, and the names of the servers - you'll be using. If you're switching from another groupware - or email program, you can almost certainly use the same - settings as you did with that program. Network-related - settings are in the <guilabel>Mail Sources</guilabel> and - <guilabel>Mail Transport</guilabel> tabs. - </para> - - <sect3 id="config-prefs-network-sources"> - <title>Mail Sources</title> - <para> - The <interface>Mail Sources</interface> tab allows you to - edit, add, or delete methods of retrieving mail from - servers. Clicking on <guibutton>Add</guibutton> or - <guibutton>Edit</guibutton> will bring up a dialog box to - offer you the following options: - <variablelist> - <varlistentry> - <term><guilabel>Mail source type:</guilabel></term> - <listitem> - <para> - Select from <glossterm - linkend="imap">IMAP</glossterm> or <glossterm - linkend="pop">POP</glossterm> servers, or Unix-style - <systemitem><filename>mbox</filename></systemitem> - or <systemitem><filename>mh</filename></systemitem> - files. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term> <guilabel>Server:</guilabel></term> - <listitem> - <para> - Enter the name of the mail source server in this - field. If you use an may or may not be the same as your - <glossterm linkend="smtp">SMTP</glossterm> server. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Username:</guilabel></term> - <listitem> - <para> - Enter the user name for the account you have on the - server-- this should the part of your email address - before the @. If you use - <systemitem><filename>mbox</filename></systemitem> - or <systemitem><filename>mh</filename></systemitem> - files as your mail source, you do not need to enter - a username. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Authentication:</guilabel></term> - <listitem> - <para> - Tell <application>Evolution</application> how to - verify your identity with the server. Your options - vary depending upon the type of server you are - using, and the ways it is configured. Given the - name of a server, - <application>Evolution</application> can detect what - sorts of authentication it offers. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Test Settings</guilabel></term> - <listitem> - <para> - Click this button to have - <application>Evolution</application> check to see if - mail sources are configured correctly. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - <para> - If you have several mail sources, clicking <guibutton>Get - Mail</guibutton> will refresh any IMAP, - <systemitem><filename>mh</filename></systemitem>, or - <systemitem><filename>mbox</filename></systemitem> - listings and check and download mail from all POP servers. - In other words, <guibutton>Get Mail</guibutton> gets your - mail, no matter how many sources you have, or what types - they are. - </para> - </sect3> - - <sect3 id="config-prefs-mail-network-transports"> - <title>Mail Transports</title> - <para> - The <interface>Mail Transports</interface> tab lets you set - how you will send mail. Evolution currently supports two - mail transport options: <glossterm linkend="smtp">SMTP</glossterm>, which - uses a remote mail server, and - <glossterm linkend="sendmail">sendmail</glossterm>, which uses the - <application>sendmail</application> program on your local - system. <application>Sendmail</application> is more - difficult to configure, but offers more flexibility than - <glossterm>SMTP</glossterm>. - </para> - <para> - To use <guilabel>SMTP</guilabel>, you'll need to enter the - name of your SMTP server. It may have the same name as - your mail source server. - </para> - <para> - <application>Evolution</application> can attempt to - determine if you have entered a valid server name. To - have it do so, click the <guilabel>Test - Settings</guilabel> button. - </para> - </sect3> - </sect2> - <sect2 id="config-prefs-network-news"> - <title>News Servers</title> - <para> - Newsgroups are so much like mailing lists that there's no - reason not to keep them right next to your mail. When you - first select the <guilabel>News Servers</guilabel> tab, - you will see a blank box with the three familiar buttons - on the right: <guibutton>Add</guibutton>, - <guibutton>Edit</guibutton>, and - <guibutton>Delete</guibutton>. - </para> - <para> - Click <guibutton>Add</guibutton> to add a news server; you - will be prompted for its name. Enter the name, click - <guibutton>OK</guibutton>, and you're done. You can have - as many mail servers as you like, of course. News servers - will appear next to your IMAP servers in the - <interface>folder bar</interface>. - </para> - </sect2> - - <sect2 id="config-prefs-mail-other"> - <title>Other Mail Preferences</title> - <para> - Not everything fits neatly into categories. This tab - contains some miscellaneous configurations that don't have - too much to do with each other. - <variablelist> - - <varlistentry> - <term> - <guilabel>Send messages in HTML format</guilabel> - </term> - <listitem><para> - If you check this box, you will send - messages as HTML by default. If you leave it unchecked, your - messages will be sent without HTML formatting unless you select - <menuchoice> <guimenu>Format</guimenu> <guimenuitem>HTML</guimenuitem> - </menuchoice> in the message composer. - See <xref linkend="usage-mail-getnsend-send-html"> - for more information about HTML mail. - </para></listitem> - </varlistentry> - <varlistentry> - <term> - <guilabel>Mark Messages as Seen After</guilabel> - </term> - <listitem><para> - When you click on a message, - <application>Evolution</application> will wait a - moment before marking it as seen. You can set the - delay, in milliseconds, here. - </para></listitem> - </varlistentry> - <varlistentry> - <term> - <guilabel>Folder Format</guilabel> - </term> - <listitem> <para> By default, - <application>Evolution</application> saves its mail - in the - <systemitem><filename>mbox</filename></systemitem> - format. You can switch to the - <systemitem><filename>mh</filename></systemitem> - format if you like. Note that this is an advanced - feature and may cause you to lose some messages, so - you should probably make a backup of your - <systemitem><filename>evolution</filename></systemitem> - directory first. In addition, it will take quite - some time if you have a large mailbox. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - </sect1> - - <sect1 id="config-prefs-cal"> - <title>Configuring the Calendar</title> - <para> - To set your calendar preferences, select - <menuchoice><guimenu>Settings</guimenu> - <guimenuitem>Calendar - Configuration</guimenuitem></menuchoice> from the Calendar - view. This will open up the - <interface>Preferences</interface> window. It contains four - tabs: <guilabel>Time display</guilabel>, - <guilabel>Colors</guilabel>, <guilabel>To Do List</guilabel> - and <guilabel>Alarms</guilabel>. The <interface>calendar - preferences window</interface> is illustrated in <xref - linkend="config-prefs-cal-fig">. - - <!-- ==============Figure===================== --> - <figure id="config-prefs-cal-fig"> - <title>Calendar Preferences Dialog</title> - <screenshot> - <screeninfo>If this worked on my job as well as my calendar...</screeninfo> - <graphic fileref="fig/config-cal" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - <!-- ==============End of Figure================--> - </para> - - <sect2 id="config-prefs-cal-time"> - <title>Time Display Settings</title> - <para> - The <guilabel>Time display</guilabel> tab lets you set the - following: - <variablelist> - <varlistentry> - <term>Time format</term> - <listitem> - <para>You may choose between twelve-hour (AM/PM) and - twenty-four hour time formats here by clicking the - appropriate radio button. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Weeks start on</term> - <listitem> - <para>You can set weeks to start on Sunday or on Monday.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>Day range</term> - <listitem> - <para> - When does your work day start, and when does it end? - In the day and week views, - <application>Evolution</application> displays all the - hours in the range you select here, even if there are - no appointments for those times. Of course, you can - still schedule an appointment outside of these hours, - and if you do, the display will be extended to show - it. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - <sect2 id="config-prefs-cal-color"> - <title>Calendar Colors</title> - <para> - The <interface>colors tab</interface> allows you to decide - what color your calendar will be. The tab consists of a - sample calendar on the right and a list of ten items that can - be colored in different ways. If you click on the color - button to the right of each item, you will bring up a - color-selector window where you can choose to alter that - color. By clicking <guibutton>OK</guibutton> in the color - selection dialog, you can see the results of the color on the - sample calendar. - </para> - <para>The display elements whose color you can set are: - - <itemizedlist> - <listitem> - <para> - <guilabel>Outline:</guilabel> The lines between days - and at the top of the display. - </para> - </listitem> - - <listitem> - <para> <guilabel>Headings:</guilabel> Text color for day - and month names and other headings. - </para> - </listitem> - - <listitem> - <para> <guilabel>Empty days:</guilabel> This is the - background color for any time slots in which you have no appointments. - </para> - </listitem> - - <listitem> - <para> - <guilabel>Appointments:</guilabel> This is the - background color for any time slots in which you have appointments. - </para> - </listitem> - - <listitem> - <para> <guilabel>Highlighted day:</guilabel> The - background color for a selected time slot. - </para> - </listitem> - - - <listitem> - <para> - <guilabel>Day numbers:</guilabel> Text color for date numbers. - </para> - </listitem> - - - <listitem> - <para> - <guilabel>Current day's number:</guilabel> Text color for today's date. - </para> - </listitem> - - <listitem> - <para> <guilabel>To-Do item that is not yet - due:</guilabel> Text color for To-Do list items that are - not yet due. (Or maybe background color? find out!) - </para> - </listitem> - - - <listitem> - <para> <guilabel>To-Do item that is due today:</guilabel> - Text color for today's tasks. - </para> - </listitem> - - <listitem> - <para> <guilabel>To-Do item that is overdue:</guilabel> - Text color for overdue tasks. - </para> - </listitem> - - </itemizedlist> - </para> - </sect2> - - <sect2 id="config-prefs-cal-todo"> - <title>To Do List Settings</title> - <para> - You can choose what information the To Do list displays and the - way it is displayed. The two areas of the <interface>To Do - List</interface> tab offer several options each: - <variablelist> - <varlistentry> - <term>Show on To Do List</term> - <listitem> - <para> - This box contains three items. If you select the - check boxes next to them, that information will appear - in the To Do list for each task it contains: - <itemizedlist> - <listitem> - <para><guilabel>Due Date</guilabel></para> - </listitem> - <listitem> - <para><guilabel>Time Until Due</guilabel></para> - </listitem> - <listitem> - <para><guilabel>Priority</guilabel></para> - </listitem> - </itemizedlist> - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Style Options</term> - <listitem> - <para> - Select among the following checkboxes to determine - how your To Do list will look: - <itemizedlist> - <listitem> - <para><guilabel>Highlight overdue items</guilabel></para> - </listitem> - <listitem> - <para><guilabel>Highlight items due today</guilabel></para> - </listitem> - <listitem> - <para><guilabel>Highlight not yet due items</guilabel></para> - </listitem> - </itemizedlist> - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="config-prefs-cal-alarms"> - <title>Alarms Settings</title> - <para> - The <interface>alarms tab</interface> enables you to select from three boxes: - <itemizedlist> - <listitem> - <para><guilabel>Beep on display alarms</guilabel>: select - this box to have <application>Evolution</application> beep - at you for any alarms you have set. If you leave this box - unchecked, <application>Evolution</application> will only - alert you to events by opening a dialog box. These beeps - are distinct from full-fledged audio alarms. - </para> - </listitem> - <listitem> - <para><guilabel>Audio alarms timeout after: </guilabel> - Select this button to have your audio alarms stop - automatically after a certain number of seconds. </para> - </listitem> - <listitem> - <para><guilabel>Enable snoozing for:</guilabel> If you - would like to have the option to tell - <application>Evolution</application> to repeat an alarm in - a few minutes, select this button and decide how long - you'd like it to wait. - </para> - </listitem> - </itemizedlist> - </para> - </sect2> - - </sect1> - - <sect1 id="config-prefs-contact"> - <title>Managing the Contact Manager</title> - <para> - To set the behavior of your Contact Manager, click on the - <guibutton>Contact Manager</guibutton> tab in the - <interface>Preferences</interface> window. - </para> - <para> - You can set the following options: <!--insert variable list - here--> - </para> - - <sect2 id="config-prefs-contact-ldap-add"> - <title>Adding Directory Servers</title> - <para> - To add a new LDAP server to your available contact - folders, select <menuchoice> <guimenu>Actions</guimenu> - <guimenuitem>New Directory Server</guimenuitem> - </menuchoice>. This brings up a small dialog box which - will let you enter the following options: - <itemizedlist> - <listitem><para> - <guilabel>Name</guilabel> — any name you choose for the server. - </para></listitem> - - <listitem><para> - <guilabel>Description</guilabel> — a longer description of the server. - </para></listitem> - - <listitem><para> - <guilabel>LDAP Server</guilabel> — the network address of the server. - </para></listitem> - - <listitem><para> - <guilabel>Port Number</guilabel> — by default, the port number is 389. - </para></listitem> - - <listitem><para> - <guilabel>Root DN</guilabel> — enter the root DN here. - </para></listitem> - </itemizedlist> - </para> - </sect2> - </sect1> - - - - <sect1 id="config-prefs-general"> - <title>General Preferences</title> - <para> - Additional configuration options will be covered here, as - they become available. - </para> - </sect1> -</chapter> - - - - - - diff --git a/help/C/config-setupassist.sgml b/help/C/config-setupassist.sgml deleted file mode 100644 index b9b72b568a..0000000000 --- a/help/C/config-setupassist.sgml +++ /dev/null @@ -1,213 +0,0 @@ - <chapter id="config-setupassist"> - <title>Easy Setup with the Setup Assistant</title> - <para> - The first time you try to use email, the mail setup assistant - will ask you for some basic information, so - <application>Evolution</application> can let you use email. If - you prefer more detailed configuration, or if you want to make - changes to an existing email setup, see <xref - linkend="config-prefs">. - </para> - - <sect1 id="config-setupassist-mail"> - <title>Mail Setup</title> - <para> - The first time you try to send or receive mail with - <application>Evolution</application>, the <interface>mail - setup assistant</interface> will pop up to help you with your - email preferences. If you don't plan to use email, or if - you'd rather deal with your email preferences later, click - <guibutton>Cancel</guibutton>. - </para> - -<!-- - - Before you get it, though, you should decide where you want to - keep it. Your options will vary a little depending on your - network setup, but they come down to storing the mail on your - hard disk (using <glossterm linkend="pop">POP</glossterm>), or - storing it on the network (using <glossterm - linkend="imap">IMAP</glossterm>). If you store your mail on - your local hard disk, you can read it whether you're online or - not, but you can only read it from one computer. If you store - it on the network, you can only read it when you're online, - but you can access it from almost any computer with a network - connection, even if it doesn't have - <application>Evolution</application>. - - - If you choose POP, you'll be putting mail in the - <guilabel>Inbox</guilabel> in the <guilabel>Local</guilabel> - folder. If you choose IMAP, it's the - <guilabel>Inbox</guilabel> of a folder with the same name as - your mail server. That's so you can maintain several distinct - IMAP servers if you want. See <xref - linkend="config-prefs-mail"> for more information about mail - servers. ---> - - <para> - The setup assistant (sometimes called a - <glossterm>Druid</glossterm>, by analogy with the "Wizards" - that some other programs use) will guide you through the - network configuration process. It will ask you for some - basic information; your system administrator or ISP should - have the answers you'll need. The mail setup assistant is - pictured in <xref linkend="usage-setup-fig">. - -<!-- ==============Figure=================================== --> -<!-- druid-pic should eventually become assistant-pic --> - - <figure id="usage-setup-fig"> - <title>Mail Setup Assistant</title> - <screenshot> - <screeninfo>Evolution Main Window</screeninfo> - <graphic fileref="fig/mail-druid-pic" format="png" srccredit="Kevin Breit"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> - - - - The assistant will ask you for the following information: - <variablelist> - - <varlistentry> - <term> <guilabel>Name:</guilabel> </term> <listitem> - <para>Your full name. </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Email address:</guilabel></term> - <listitem><para> - Your complete email address. - </para></listitem> - </varlistentry> - - <varlistentry> - <term> <guilabel>Organization:</guilabel></term> - <listitem> - <para> - Any organization you represent, or the company where you - work. Leave this blank if you wish, or type "My own bad - self" so people know your opinions are yours alone. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Signature File:</guilabel></term> - <listitem> - <para> - A text file appended to any email you send. A signature - file typically consists of your name and email address, - or a quotation you like. It's good form to keep your - "sig" on the short side: four lines is plenty. Remember, - this is attached to every email you send. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term> <guilabel>Mail source type:</guilabel></term> - <listitem> - <para> - <application>Evolution</application> supports several - mail sources: <glossterm linkend="pop">POP</glossterm> and - <glossterm linkend="imap">IMAP</glossterm> servers, and UNIX-style - <systemitem><filename>mbox</filename></systemitem> and - <systemitem><filename>mh</filename></systemitem> files. - POP servers retrieve your mail and store it on your - local system so you can refer to it even when not - connected to a network; <glossterm>IMAP</glossterm> - servers store the mail on the server so you can access - it from multiple locations; - <systemitem><filename>mbox</filename>></systemitem> - files are used by your computer for internal mail, and - may be useful if you want to switch from another email - client such as <application>Spruce</application> or - <application>Netscape Communicator</application>. Ask - your system administrator which you should use, or keep - guessing until one works. You may use multiple sources - if you wish; see <xref - linkend="config-prefs-mail-network"> for more - information. - </para> - <para> - If you decide not to have - <application>Evolution</application> use any servers, - the remaining items are not relevant; you only need to - point to the location of the files you wish to access. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term> <guilabel>Server:</guilabel></term> - <listitem> - <para> - This should be the name of the server where you get - incoming mail. It may (or may not) be the same as the - server where you send your outgoing mail. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Username:</guilabel></term> - <listitem> - <para> - Enter the username for your mail server account, if you - have one. In almost all cases, this is the part of your email - address before the @ character, and - <application>Evolution</application> has selected that - value as the default. If you have a different username, - you can enter it here. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Authentication:</guilabel></term> - <listitem> - <para> - Select the type of authentication you will use. You can - click <guibutton>Detect supported types</guibutton> to - find out which authentication protocols your network - allows. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Mail Transport:</guilabel></term> - <listitem> - <para> - This is the mail sending protocol you will want to use. - <application>Evolution</application> supports both - <glossterm linkend="smtp">SMTP</glossterm> and - <application>sendmail</application>; SMTP is by far the - more common. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - <para> - To learn how to configure <application>Evolution</application> - in greater detail, or to change preferences once you have set - them, see <xref linkend="config-prefs">. - </para> - </sect1> - -</chapter> - - - - - - - - - diff --git a/help/C/config-sync.sgml b/help/C/config-sync.sgml deleted file mode 100644 index 0445b474c4..0000000000 --- a/help/C/config-sync.sgml +++ /dev/null @@ -1,124 +0,0 @@ - <chapter id="config-sync"> - <title>Setting up your synchronization system</title> - <para> - Synchronization presents you with two issues you'll need to - deal with. - <simplelist> - <member> - Your computer needs to recognize and access your handheld. - At this time, <application>Evolution</application> only - supports Palm-OS devices like the PalmPilot and the - Handspring Visor. - </member> - <member> - You should decide what sort of synchronization behavior you - want. - </member> - </simplelist> - - </para> - <para> - If you haven't used a handheld device with your computer - before, you'll need to run the GNOME <application>Control - Center</application> and make sure that <application>Pilot - Link</application> is properly configured. Then, select the - <application>Evolution</application> <glossterm - linkend="conduit">conduits</glossterm> under the - <guilabel>Pilot Conduits</guilabel> section of the Control - Center. - </para> - <para> - Once your computer and your Palm-OS device are talking happily - to each other, you'll have to decide what exactly you want - them to do with the data they exchange. Your options may vary - depending on the conduit, but typically they will be: - - <variablelist> - <varlistentry> - <term>Disabled </term> - <listitem> - <para> - Do nothing. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Synchronize</term> - <listitem> - <para> - Copy new data from the computer to the handheld, and - from the handheld to the computer. Remove items - that were on both systems but have been deleted on - one. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Copy From Pilot</term> - <listitem> - <para> - If there is any new data on the the handheld device, - copy it to the computer. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Copy To Pilot</term> - <listitem> - <para> - Copy new data from the computer to the handheld. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Merge From Pilot</term> - <listitem> - <para> - Copy new data from the handheld to the computer, and - remove any information from the computer that has - been deleted on the handheld. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Merge To Pilot</term> - <listitem> - <para> - Copy new data from the computer to the handheld, and - remove any information from the handheld that has - been deleted on the computer. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - - <para> - Select a behavior for each conduit available. For the most - part, you'll want to stick with - <guilabel>Synchronize</guilabel>. Then, put your handheld on - its cradle and press the synchronization button. - </para> - - - <para> - <warning> - <title>Data Loss Prevention</title> - <para> - It's always a good idea to make a backup. To do that, - make a copy of your <systemitem> - <filename>~/evolution</filename> </systemitem> directory. - </para> - </warning> - </para> - - </chapter> - - - - diff --git a/help/C/evolution.sgml b/help/C/evolution.sgml deleted file mode 100644 index 114f2e87d9..0000000000 --- a/help/C/evolution.sgml +++ /dev/null @@ -1,145 +0,0 @@ -<!DOCTYPE book PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"[ - -<!ENTITY PREFACE SYSTEM "preface.sgml"> -<!ENTITY USAGE-MAINWINDOW SYSTEM "usage-mainwindow.sgml"> -<!ENTITY USAGE-EXEC-SUMMARY SYSTEM "usage-exec-summary.sgml"> -<!ENTITY USAGE-MAIL SYSTEM "usage-mail.sgml"> -<!ENTITY USAGE-CONTACT SYSTEM "usage-contact.sgml"> -<!ENTITY USAGE-CALENDAR SYSTEM "usage-calendar.sgml"> -<!ENTITY USAGE-SYNC SYSTEM "usage-sync.sgml"> -<!ENTITY USAGE-PRINT SYSTEM "usage-print.sgml"> -<!ENTITY CONFIG-SETUPASSIST SYSTEM "config-setupassist.sgml"> -<!ENTITY CONFIG-PREFS SYSTEM "config-prefs.sgml"> -<!ENTITY CONFIG-SYNC SYSTEM "config-sync.sgml"> -<!ENTITY MENUREF SYSTEM "menuref.sgml"> -<!ENTITY APX-GLOSS SYSTEM "apx-gloss.sgml"> -<!ENTITY APX-BUGS SYSTEM "apx-bugs.sgml"> -<!ENTITY APX-AUTHORS SYSTEM "apx-authors.sgml"> - -]> - - -<!-- Almost every chapter is an entity. Files, Chapter id's, and -entity names correspond. APX is for appendix. Note that there is no -entity for apx-notes.sgml, which is still included in the file -set. Reinstate the entity if and when the Notes feature is -implemented. --> - -<book id="index"> - <bookinfo> - <title>A User's Guide to Evolution</title> - <authorgroup> - <author><firstname>Aaron</firstname><surname>Weber</surname></author> - <author><firstname>Kevin</firstname><surname>Breit</surname></author> - </authorgroup> - <copyright> - <year>2000</year> - <holder> Ximian, Inc., </holder> - <holder> Kevin Breit </holder> - </copyright> - - <legalnotice id="legalnotice"> - - <para> - Permission is granted to copy, distribute and/or modify this - document under the terms of the <ulink type="help" - url="gnome-help:fdl"><citetitle>GNU Free Documentation - License</citetitle></ulink>, Version 1.1 or any later version - published by the Free Software Foundation with no Invariant - Sections, no Front-Cover Texts, and no Back-Cover Texts. You - may obtain a copy of the <citetitle>GNU Free Documentation - License</citetitle> from the Free Software Foundation by - visiting <ulink type="http" url="http://www.fsf.org">their - Web site</ulink> or by writing to: Free Software Foundation, - Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, - USA. - </para> - <para> - Many of the names used by companies to distinguish their - products and services are claimed as trademarks. Where those - names appear in any GNOME documentation, and those trademarks - are made aware to the members of the GNOME Documentation - Project, the names have been printed in caps or initial caps. - </para> - </legalnotice> - - <releaseinfo> - This is version 0.9 of the Evolution manual. - </releaseinfo> - - </bookinfo> - - &PREFACE; - - <part id="usage"> - <title>Using Evolution</title> - <partintro> - <para> - Part one of the <application>Evolution</application> manual - describes how to use <application>Evolution</application> for - email, contact management, and appointment and task - scheduling. You'll find as you go along that there's more - than one way to do things, and you can pick whichever method - you like best. - </para> - </partintro> - - &USAGE-MAINWINDOW; - &USAGE-EXEC-SUMMARY; - &USAGE-MAIL; - &USAGE-CONTACT; - &USAGE-CALENDAR; -<!-- &USAGE-NOTES; --> - &USAGE-SYNC; - &USAGE-PRINT; - </part> - <part id="config"> - <title>Configuring and Managing Evolution</title> - <partintro> - <para> - <application>Evolution</application> is highly configurable. - Usually, when developers say that, they mean that they didn't - test it out thoroughly and have left it to other programmers - to "configure" themselves a working system. In the case of - <application>Evolution</application>, "configurable" means - what it ought to. It means that, while you can expect the - program to work perfectly well in its default settings, it's - also easy to alter its behavior in a wide variety of ways, so - that it fits your needs exactly. This part of the book will - describe that process, from the quickest glimpse of the Setup - Assistant to an in-depth tour of the preferences dialogs. - </para> - </partintro> - - &CONFIG-SETUPASSIST; - &CONFIG-PREFS; - &CONFIG-SYNC; - </part> - - <part> - <title>Comprehensive Menu reference</title> - <partintro> - <para> - The following reference covers all, or nearly all, of the - menus and menu commands that - <application>Evolution</application> has to offer you. - </para> - </partintro> - &MENUREF; - </part> - - &APX-GLOSS; - &APX-BUGS; - &APX-AUTHORS; -</book> - - - - - - - - - - - diff --git a/help/C/fig/calendar.png b/help/C/fig/calendar.png Binary files differdeleted file mode 100644 index c9703f4903..0000000000 --- a/help/C/fig/calendar.png +++ /dev/null diff --git a/help/C/fig/config-cal.png b/help/C/fig/config-cal.png Binary files differdeleted file mode 100644 index 25b5b68621..0000000000 --- a/help/C/fig/config-cal.png +++ /dev/null diff --git a/help/C/fig/config-mail.png b/help/C/fig/config-mail.png Binary files differdeleted file mode 100644 index cd8543d94e..0000000000 --- a/help/C/fig/config-mail.png +++ /dev/null diff --git a/help/C/fig/contact-editor.png b/help/C/fig/contact-editor.png Binary files differdeleted file mode 100644 index 988ad2f918..0000000000 --- a/help/C/fig/contact-editor.png +++ /dev/null diff --git a/help/C/fig/contact.png b/help/C/fig/contact.png Binary files differdeleted file mode 100644 index a9ed02251a..0000000000 --- a/help/C/fig/contact.png +++ /dev/null diff --git a/help/C/fig/filter-assist-fig.png b/help/C/fig/filter-assist-fig.png Binary files differdeleted file mode 100644 index 5248e0effe..0000000000 --- a/help/C/fig/filter-assist-fig.png +++ /dev/null diff --git a/help/C/fig/filter-new-fig.png b/help/C/fig/filter-new-fig.png Binary files differdeleted file mode 100644 index a8b41ca678..0000000000 --- a/help/C/fig/filter-new-fig.png +++ /dev/null diff --git a/help/C/fig/mail-composer.png b/help/C/fig/mail-composer.png Binary files differdeleted file mode 100644 index 22c16365b5..0000000000 --- a/help/C/fig/mail-composer.png +++ /dev/null diff --git a/help/C/fig/mail-druid-pic.png b/help/C/fig/mail-druid-pic.png Binary files differdeleted file mode 100644 index f29f3e77be..0000000000 --- a/help/C/fig/mail-druid-pic.png +++ /dev/null diff --git a/help/C/fig/mail-inbox.png b/help/C/fig/mail-inbox.png Binary files differdeleted file mode 100644 index b4f18640b4..0000000000 --- a/help/C/fig/mail-inbox.png +++ /dev/null diff --git a/help/C/fig/mainwindow-pic.png b/help/C/fig/mainwindow-pic.png Binary files differdeleted file mode 100644 index 28bf487bf9..0000000000 --- a/help/C/fig/mainwindow-pic.png +++ /dev/null diff --git a/help/C/fig/print-dest.png b/help/C/fig/print-dest.png Binary files differdeleted file mode 100644 index 464705711e..0000000000 --- a/help/C/fig/print-dest.png +++ /dev/null diff --git a/help/C/fig/print-preview.png b/help/C/fig/print-preview.png Binary files differdeleted file mode 100644 index 7f9a8d661a..0000000000 --- a/help/C/fig/print-preview.png +++ /dev/null diff --git a/help/C/fig/vfolder-createrule-fig.png b/help/C/fig/vfolder-createrule-fig.png Binary files differdeleted file mode 100644 index 162bebf48c..0000000000 --- a/help/C/fig/vfolder-createrule-fig.png +++ /dev/null diff --git a/help/C/menuref.sgml b/help/C/menuref.sgml deleted file mode 100644 index d82191cb17..0000000000 --- a/help/C/menuref.sgml +++ /dev/null @@ -1,1470 +0,0 @@ -<!-- -<!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> - -<chapter id="menuref"> - <title>Menu Reference</title> - <para> - <application>Evolution</application>'s menus may not hold the - secret to happiness, they do hold every ability that - <application>Evolution</application> has. This section will serve - as a reference for all those menus, and the capabilites that they - offer you. - </para> - <para> - In addition, the editor tools for messages, appointments, and - contacts all have menu bars of their own. From left to right, the - menus available to you when you are reading mail are: - <guimenu>File</guimenu>, <guimenu>Edit</guimenu>, - <guimenu>View</guimenu>, <guimenu>Settings</guimenu>, - <guimenu>Message</guimenu>, <guimenu>Folder</guimenu>and - <guimenu>Help</guimenu>. - - </para> - <para> - Menus in <application>Evolution</application> are - context-sensitive, which means that they vary depending on what - you're doing. If you're reading your mail, you'll have - mail-related menus; for your calendar, you'll have - calendar-related menu items. Some menus, of course, like - <guimenu>Help</guimenu> and <guimenu>File</guimenu> don't much, if - at all, because they have more universal functions. But you'd - never mark an address card as "read," or set the recurrence for an - email message you've recieved. depending on whether you're looking - at mail, contacts, or calendar information. - </para> - - - - <sect1 id="menuref-universal"> - <title>Menus that are the same everywhere</title> - <para> - The <guimenu>File</guimenu> and <guimenu>Help</guimenu> menus in - the main <application>Evolution</application> window do not - change, because they refer to universal items. Other menus have - contents that change depending on context. - </para> - - <sect2 id="menuref-universal-file"> - <title>File Menu</title> - <para> - <variablelist> - - <varlistentry> - <term><guisubmenu>New...</guisubmenu> Submenu</term> - <listitem><para> - <itemizedlist> - <listitem><para> - <guimenuitem>Folder</guimenuitem> — - Create a new folder. See <xref - linkend="usage-mainwindow-folderbar"> - for more information about folders. - </para></listitem> - <listitem><para> - <guimenuitem>Shortcut</guimenuitem> — - Create a new Shortcut in the Shortcut Bar. - </para></listitem> - <listitem><para> - <guimenuitem>Mail Message</guimenuitem> — - Compose a new mail message. Covered in - <xref linkend="usage-mail-getnsend-send">. - </para></listitem> - <listitem><para> - <guimenuitem>Appointment</guimenuitem> — - Enter a new appointment in your calendar. See <xref - linkend="usage-calendar-apts-basic"> for more information. - </para></listitem> - <listitem><para> - <guimenuitem>Task</guimenuitem> — - Enter a new to-do item in your taskpad. Covered in - <xref linkend="usage-calendar-todo">. - </para></listitem> - </itemizedlist> - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Go to Folder</guimenuitem></term> - <listitem><para> - View the items in a particular folder. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Create New Folder</guimenuitem></term> - <listitem><para> - This item doesn't belong here any more. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Print Message</guimenuitem></term> - <listitem><para> - Print the current message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Exit</guimenuitem></term> - <listitem><para> - Quit using <application>Evolution</application>. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-universal-help"> - <title>The Help Menu</title> - <para> - <variablelist> - <varlistentry> - <term><guimenuitem>Help Index</guimenuitem></term> - <listitem><para> - Displays the table of contents for this document. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Getting Started</guimenuitem></term> - <listitem><para> - A quick look around, and a summary of the things - <application>Evolution</application> can do for you. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Using the Mailer</guimenuitem></term> - <listitem><para> - An in-depth tour of <application>Evolution</application> Mail. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Using the Calendar</guimenuitem></term> - <listitem><para> - A step-by-step guide to using the Calendar. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Using the Contact Manager</guimenuitem></term> - <listitem><para> - Find your way around the Contact Manager. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Submit Bug Report</guimenuitem></term> - <listitem><para> - If you don't report them, they can't fix them. Select this item to let the - developers know what's wrong. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>About Evolution</guimenuitem></term> - <listitem><para> - Displays a window with information about the application and its authors. - This has the same information as <xref linkend="authors">. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - </sect1> - - <sect1 id="menuref-exec"> - <title>Executive Summary Menus</title> - <para> - We'll leave this section blank until the UI stabilizes a little - more. - </para> - </sect1> - - - - <sect1 id="menuref-mail"> - <title>Mail Menus</title> - <para> - <application>Evolution</application> Mail has more specialized - menus, and more specialized menu items, than any other part of - the application. - </para> - - <sect2 id="menuref-mail-edit"> - <title>The Edit Menu</title> - <para> - This menu is currently empty. - </para> - </sect2> - - <sect2 id="menuref-mail-view"> - <title>The Mail View Menu</title> - <para> - This menu lets you control the way - <application>Evolution</application> displays your information - for you. - <variablelist> - <varlistentry> - <term><guimenuitem>Show Shortcut Bar</guimenuitem></term> - <listitem><para> - Toggle the shortcut bar on and off with this item. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Show Folder Bar</guimenuitem></term> - <listitem><para> - Toggle the folder bar on and off with this item. - See <xref linkend="usage-mainwindow-folderbar"> for - more information about the folder bar. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Threaded Message List</guimenuitem></term> - <listitem><para> - This item controls whether your message list is displayed by thread - or by other criteria. The default order is by date; see - <xref linkend="usage-mail-listorder"> for information about the - order of the message list. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-mail-tools"> - <title>The Mail Settings Menu</title> - <para> - <variablelist> - <varlistentry> - <term><guimenuitem>Mail Filters</guimenuitem></term> - <listitem><para> - Edit your mail filters here. - See <xref linkend="usage-mail-organize-filters"> - for more information about mail filtering. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Virtual Folder Editor</guimenuitem></term> - <listitem><para> - Create, edit, and delete Virtual Folders (<glossterm>vFolders</glossterm>) - with this tool. - To learn about using vFolders with mail, see - <xref linkend="usage-mail-organize-vfolders">. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Mail Configuration</guimenuitem></term> - <listitem><para> - Tools for setting up all your mail account preferences. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Manage Subscriptions</guimenuitem></term> - <listitem><para> - Tools for newsgroup and IMAP folder subscriptions. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Forget Passwords</guimenuitem></term> - <listitem><para> - This item will cause <application>Evolution</application> - to forget what your password is. - </para></listitem> - </varlistentry> - - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-mail-folder"> - <title>The Mail Folder Menu</title> - <para> - The items in this menu relate to - <application>Evolution</application> mail folders. - </para> - <para> - You can: - <variablelist> - - <varlistentry> - <term><guimenuitem>Mark all as Read</guimenuitem></term> - <listitem><para> - <application>Evolution</application> keeps track of which messages - you've seen; to mark everything in a folder as read, choose this item. - You can mark a single message as read by right-clicking it in the message bar. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Delete All</guimenuitem></term> - <listitem><para> - This is a favorite item of everyone with too much junk-mail: one click, and it - deletes every message in the current folder. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Expunge</guimenuitem></term> - <listitem><para> - Empties the trash folder, erasing messages permanently. - Once you've done this, they're gone for good. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Configure Folder</guimenuitem></term> - <listitem><para> - Use this item to set the file format in which - <application>Evolution</application> stores mail. You - can choose from standard UNIX-style - <systemitem><filename>mbox</filename></systemitem> - files, or the - <systemitem><filename>mh</filename></systemitem> format. - Converting large mailboxes may take a long time, and - it's a good idea to have a backup copy beforehand. - </para></listitem> - </varlistentry> - - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-mail-message"> - <title>The Mail Message Menu</title> - <para> - The items in this menu relate to - <application>Evolution</application> mail messages. Most of - them require you to have a message selected, and are also - available by right-clicking on a message in the message - list. - </para> - <para> - <variablelist> - - - <varlistentry> - <term><guimenuitem>Open in New Window</guimenuitem></term> - <listitem><para> - Displays the selected message in a new window. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Edit Message</guimenuitem></term> - <listitem><para> - Open the selected message in the message composer. You - can only edit a message you have written: drafts and messages in - the <guilabel>Sent</guilabel> box. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Print Message</guimenuitem></term> - <listitem><para> - Displays the <interface>Print Preview</interface> window, - ready for printing. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Reply to Sender</guimenuitem></term> - <listitem><para> - Opens a message composition window addressed to the - author of the message. Covered in detail in - <xref linkend="usage-mail-getnsend-send-reply">. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Reply to All</guimenuitem></term> - <listitem><para> - Opens a message composition window addressed to the - author of the message and all known recipients. - Covered in detail in <xref linkend="usage-mail-getnsend-send-reply">. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Forward</guimenuitem></term> - <listitem><para> - Appends the body of the selected message to a new message. - Covered in detail in <xref linkend="usage-mail-getnsend-fwd">. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Delete Message</guimenuitem></term> - <listitem><para> - Marks a message for deletion. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Move Message</guimenuitem></term> - <listitem><para> - Choose a folder in which to place this message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Copy Message</guimenuitem></term> - <listitem><para> - Copy the selected message to another folder. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>VFolder on Subject</guimenuitem></term> - <listitem><para> - This item, and the three that follow it, will create vFolders - which you may customize further or save as-is. This one will - create a vFolder which will display all messages that contain the - subject line of the selected message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>VFolder on Sender</guimenuitem></term> - <listitem><para> - Creates a vFolder to hold all messages from the sender of - the selected message. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>VFolder on Recipients</guimenuitem></term> - <listitem><para> - Creates a VFolder to hold all messages addressed to the - recipient of the selected message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Filter on Subject</guimenuitem></term> - <listitem><para> - This item, and the three that follow it, will create Filters - for which you must select actions. You may keep the criteria as - they are, or alter them as you wish. This one will - create a filter which will affect all messages that contain the - subject line of the selected message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Filter on Sender</guimenuitem></term> - <listitem><para> - Creates a filter which affects all messages from the sender of - the selected message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Filter on Recipients</guimenuitem></term> - <listitem><para> - Creates a filter which will affect all messages addressed to the - recipient of the selected message. - </para></listitem> - </varlistentry> - - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-mail-messagelistheader"> - <title>The Message Heading Right-Click Menu</title> - <para> - At the top of the message list is the message list heading - bar; you can click on an individual heading — - <guilabel>Subject</guilabel>, for example, to have the - message list sorted by that attribute. However, if you right - click on a heading, you'll get the following menu: - </para> - - <para> - <variablelist> - - <varlistentry> - <term><guimenuitem>Sort Ascending</guimenuitem></term> - <listitem><para> - Sort the list, in ascending order, by the attribute you clicked. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Sort Descending</guimenuitem></term> - <listitem><para> - Sort the list in descending order. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Unsort</guimenuitem></term> - <listitem><para> - Undo any sorting by this attribute, and leave the message list sorted - by the previous one. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Group by this Field</guimenuitem></term> - <listitem><para> - Instead of sorting the messages, group them in boxes. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Group by Box</guimenuitem></term> - <listitem><para> If you have your messages grouped in - boxes, you can arrange the boxes as well, by choosing - this item. </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Remove this column</guimenuitem></term> - <listitem><para> - Choose this to remove the column from the message list display. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Field Chooser</guimenuitem></term> - <listitem><para> - Opens a palette of columns. You can drag the columns - you want from the palette into position in the - message list heading bar; red arrows appear - when you get close enough to a possibile position.</para> - - <para> - Your options are: - <itemizedlist> - <listitem><para> - <guiicon>An Envelope</guiicon> which indicates whether a message has been read (closed for unread, open for read). - </para></listitem> - - <listitem><para> - <guiicon>An Exclamation Point</guiicon> for priority - </para></listitem> - - <listitem><para> - <guiicon>A Penguin</guiicon> which indicates something, although I'm not sure what. - </para></listitem> - - <listitem><para> - <guiicon>A Paper Clip</guiicon> which indicates that there is an attachment to the message. - </para></listitem> - - <listitem><para> - <guilabel>From</guilabel>, for the <guilabel>From</guilabel> field of a message. - </para></listitem> - <listitem><para> - <guilabel>Subject</guilabel>, for the <guilabel>Subject</guilabel> field of a message. - </para></listitem> - - <listitem><para> - <guilabel>Date</guilabel>, for the date and time a message was sent. - </para></listitem> - - <listitem><para> - <guilabel>Received</guilabel>, for the date and time you got the message. - </para></listitem> - - <listitem><para> - <guilabel>To</guilabel>, for the <guilabel>To</guilabel> field. - </para></listitem> - - <listitem><para> - <guilabel>Size</guilabel>, for a message's size. - </para></listitem> - </itemizedlist> - </para> - - </listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Alignment</guimenuitem></term> - <listitem><para> Use this item to decide upon the - alignment of the message attributes within their - columns. </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Best Fit</guimenuitem></term> - <listitem><para> - Alters the width of the message list columns to maximize the amount of information displayed. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Format Columns...</guimenuitem></term> - <listitem><para> - This item is not yet available. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Customize - Views...</guimenuitem></term> <listitem><para> Opens a - dialog box that lets you choose a complex set of - arrangements for your message list, so you can combine - sorting and grouping in as many ways as you like. - </para></listitem> - </varlistentry> - - </variablelist> - </para> - </sect2> - </sect1> - - <sect1 id="menuref-mail-editor"> - <title>The Message Composer Menus</title> - <para> - The message composition window has its own set of menus: - <guimenu>File</guimenu>, which controls operations on files and - data, <guimenu>Edit</guimenu>, for text editing, - <guimenu>Format</guimenu>, which controls the file format of - messages you send, <guimenu>View</guimenu>, to set how you view - the message, and <guimenu>Insert</guimenu>, which holds tools - for embedding files and other items in messages. Here's what's in them: - </para> - <sect2 id="menuref-mail-editor-file"> - <title>The Message Composer's File Menu</title> - <para> - <variablelist> - <varlistentry> - <term><guimenu>Open</guimenu></term> - <listitem><para> - Open a text file or a draft mail message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenu>Save</guimenu></term> - <listitem><para> - Save a mail message as a text file. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenu>Save As</guimenu></term> - <listitem><para> - Choose a file name and location for - a message you want to save as a text file. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenu>Save in Folder</guimenu></term> - <listitem><para> - Save a message as a draft, rather than - as a separate text file. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenu>Insert Text File</guimenu></term> - <listitem><para> - Open a text file and insert it into - the current message. (FIXME: belongs under "Insert"). - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenu>Send Now</guimenu></term> - <listitem><para> - Sends the message immediately. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenu>Send Later</guimenu></term> - <listitem><para> - Queue - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenu>Close</guimenu></term> - <listitem><para> - Closes the message composer. If you have not done so, - <application>Evolution</application> - will ask you if you want to save your message. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - <sect2 id="menuref-mail-editor-edit"> - <title>The Message Composer's Edit Menu</title> - <para> - The <guimenu>Edit</guimenu> menu in the message composer - contains the following items. Keyboard shortcuts are listed - next to the items in the menus themselves. - - <variablelist> - - <varlistentry> - <term><guimenuitem>Undo</guimenuitem></term> - <listitem><para> - Undoes the last action you performed. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Redo</guimenuitem></term> - <listitem><para> - If you change your mind about Undoing something, - you can always use this item. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Cut</guimenuitem></term> - <listitem><para> - Removes the selected text from the text entry window and - retains it in the system "clipboard" memory, ready for pasting. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Copy</guimenuitem></term> - <listitem><para> - Copies selected text to the system clipboard without deleting it. - The text can then be inserted elsewhere with the - <guimenuitem>Paste</guimenuitem> command. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Paste</guimenuitem></term> - <listitem><para> - Inserts the contents of the system clipboard at the - location of the cursor. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Find</guimenuitem></term> - <listitem><para> - Enter a phrase and find your match in your message body. - As with <guimenuitem>Find Regex</guimenuitem>, - <guimenuitem>Find Again</guimenuitem>, and - <guimenuitem>Replace</guimenuitem>, <application>Evolution</application> - will offer you the option to search forwards or backwards. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Find Regex</guimenuitem></term> - <listitem><para> - If you are familiar with <glossterm>regular expressions</glossterm>, - often called "regexes," you can search for something more complicated, - using wildcards and boolean logic. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Find Again</guimenuitem></term> - <listitem><para> - Repeats your last search. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Replace</guimenuitem></term> - <listitem><para> - Enter a word or phrase and the word or phrase with which you'd like - to replace it. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Properties</guimenuitem></term> - <listitem><para> - This item brings up the Message Composer Properties Capplet, - a portion of the GNOME Control Center that determines the - key bindings for the message composer. Help for this capplet is - available directly from the Control Center. - (FIXME: Write that help doc too) (FIXME: this is in the wrong place!) - </para></listitem> - </varlistentry> - - </variablelist> - </para> - </sect2> - <sect2 id="menuref-mail-composer-format"> - <title>The Message Composer's Format Menu</title> - <para> - The <guimenu>Format</guimenu> menu has only one item: - <variablelist> - <varlistentry> - <term><guimenuitem>HTML</guimenuitem></term> - <listitem><para> - Toggles HTML mode for the message composer. When selected, - the message is displayed and sent in HTML. If you have written a - message in HTML and turn HTML off, most formatting will be lost. - <application>Evolution</application> will attempt to preserve spacing - and to remove formatting gracefully, however. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - <sect2 id="menuref-mail-composer-view"> - <title>The Message Composer's View Menu</title> - <para> - The <guimenu>View</guimenu> menu controls the way messages are - displayed, and how much of the message, its headers, and - attachments appear. It contains: - <variablelist> - <varlistentry> - <term><guimenuitem>Show Attachments</guimenuitem></term> - <listitem><para> - Toggles the display of attachments. When this item is selected, - <application>Evolution</application> will create a separate pane - of the composition window to show what attachments you are appending - to the message. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - <sect2 id="menuref-mail-composer-insert"> - <title>The Message Composer's Insert Menu</title> - <para> - The <guimenu>Insert</guimenu> menu holds tools that allow you - to include images, horizontal rules, and other objects - in the body of your message. The tools are: - <variablelist> - - <varlistentry> - <term><guimenuitem>Image</guimenuitem></term> - <listitem><para> - This tool will prompt you to select an image file to - insert into your HTML message. For text messages, this - is the same as attaching an image file. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Link</guimenuitem></term> - <listitem><para> - Opens the <interface>link creation window</interface>, - which lets you specify the URL and text description - for a link in your message. This only works with HTML - messages. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Rule</guimenuitem></term> - <listitem><para> - Opens the<interface> horizontal rule creation dialog</interface>, which lets you - create an HTML horizontal rule. For more information, - see <xref linkend="usage-mail-getnsend-send-html">. - This tool only works with HTML messages. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Text File</guimenuitem></term> - <listitem><para> - Open a text file and insert it into the current message. - This tool works with both plain text and HTML messages. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - </sect1> - - <sect1 id="menuref-cal"> - <title>The Calendar Menus</title> - <para> - The Main window of the calendar has the same menus as the main - window of the mail client. However, their contents vary in a - number of ways. - </para> - <sect2 id="menuref-cal-edit"> - <title>The Calendar Edit Menu</title> - <para> - The contents of the Edit menu are currently so borked that I - refuse to document them right now. (That means FIXME). They - should be: - - <variablelist> - <varlistentry> - <term><guimenuitem>Item</guimenuitem></term> - <listitem><para> - Description - </para></listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Item</guimenuitem></term> - <listitem><para> - Description - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Item</guimenuitem></term> - <listitem><para> - Description - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - <sect2 id="menuref-cal-view"> - <title>The Calendar View Menu</title> - <para> - The Calendar's <guimenu>View</guimenu> menu contains the following items: - - <variablelist> - <varlistentry> - <term><guimenuitem>Show Shortcut Bar</guimenuitem></term> - <listitem><para> - Toggle the Shortcut Bar on and off with this item. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Show Folder Bar</guimenuitem></term> - <listitem><para> - Toggle the folder bar on and off with this item. - See <xref linkend="usage-mainwindow-folderbar"> for - more information about the folder bar. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>View By Day</guimenuitem></term> - <listitem><para> - Switch to the day view for your calendar. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>View Five Days</guimenuitem></term> - <listitem><para> - View five calendar days at once. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>View by Week</guimenuitem></term> - <listitem><para> - Switch the calendar view to full week mode. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>View By Month</guimenuitem></term> - <listitem><para> - Look at a month at a time. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-cal-settings"> - <title>The Calendar Settings Menu</title> - <para> - This menu is empty. - </para> - </sect2> - - </sect1> - - <sect1 id="menuref-cal-editor"> - <title>The Appointment Editor Menus</title> - <para> - The appointment editor has its own menus, to help you use its - wide-ranging abilities. - </para> - - <sect2 id="menuref-cal-editor-file"> - <title>The Appointment Editor's File Menu</title> - <para> - This menu contains several items, including a <guisubmenu>New</guisubmenu> submenu - that is identical to that in the - <link linkend="menuref-universal-file">main window's file menu</link>. - Its other contents are: - <variablelist> - - <varlistentry> - <term><guimenuitem>Send</guimenuitem></term> - <listitem><para> - Opens a mail message with the appointment attached to it. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Save</guimenuitem></term> - <listitem><para> - Save this appointment in the existing location and name. If you have not yet - chosen a location and name, this is the same as <guimenuitem>Save As</guimenuitem>. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Save As</guimenuitem></term> - <listitem><para> - Choose a location and name for this appointment, and save it. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Delete</guimenuitem></term> - <listitem><para> - Deletes the appointment. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Move to Folder</guimenuitem></term> - <listitem><para> - Chose a folder, and move the appointment into it. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Copy to Folder</guimenuitem></term> - <listitem><para> - Chose a folder, and put a copy of the appointment into it. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Page Setup Submenu</guimenuitem></term> - <listitem><para> - This menu contains two items: - <itemizedlist> - <listitem><para> - <guimenuitem>Memo Style</guimenuitem> — - FIXME: What does this do? - </para></listitem> - - <listitem><para> - <guimenuitem>Define Print Styles</guimenuitem> — - FIXME: What does this do? - </para></listitem> - </itemizedlist> - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Print Preview</guimenuitem></term> - <listitem><para> Shows you what your appointment will look - like if you print it. See <xref linkend="usage-print"> - for details on printing and the Print Preview function. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Print</guimenuitem></term> - <listitem><para> - Prints the appointment without preview. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Properties</guimenuitem></term> - <listitem><para> - FIXME: What does this do? - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Close</guimenuitem></term> - <listitem><para> - Close the appointment editor window. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-cal-editor-edit"> - <title>The Appointment Editor's Edit Menu</title> - <para> - FIXME: this menu is copied and pasted entirely from somewhere - else. - </para> - </sect2> - - <sect2 id="menuref-cal-editor-view"> - <title>The Appointment Editor's View Menu</title> - <para> - This menu allows you to look at different appointments, and - set the way you look at them, without having to move back to - the <interface>Main Window</interface>. It contains: - <variablelist> - - <varlistentry> - <term><guisubmenu>Previous</guisubmenu></term> - <listitem><para> - The items in this submenu will take you to appointments - prior to the current one. (FIXME: describe). - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guisubmenu>Next</guisubmenu></term> - <listitem><para> - The items in this submenu will take you to appointments - scheduled to occur after the current one. (FIXME: describe). - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Calendar</guimenuitem></term> - <listitem><para> - FIXME: What does this item do? - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guisubmenu>Toolbars</guisubmenu></term> - <listitem><para> - The <guisubmenu>Toolbars</guisubmenu> submenu - allows you to choose which toolbars - are displayed in the - <interface>Appointment Editor</interface>. They are: - <itemizedlist> - <listitem><para> - <guimenuitem>Standard</guimenuitem> — - Toggle the standard toolbar on and off. - </para></listitem> - - <listitem><para> - <guimenuitem>Formatting</guimenuitem> — - Toggle the formatting toolbar on and off. - </para></listitem> - - <listitem><para> - <guimenuitem>Customize</guimenuitem> — - Select the contents of the formatting and standard toolbars. - </para></listitem> - </itemizedlist> - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-cal-editor-insert"> - <title>The Appointment Editor's Insert Menu</title> - <para> - This menu contains: (FIXME: Insert Content Here) - <variablelist> - <varlistentry> - <term><guimenuitem>File</guimenuitem></term> - <listitem><para> - Choose a file to append to your appointment or appointment request. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Item</guimenuitem></term> - <listitem><para> - FIXME: ? - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Object</guimenuitem></term> - <listitem><para> - FIXME: ? - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-cal-editor-format"> - <title>The Appointment Editor's Format Menu</title> - <para> - This menu contains two items, neither of which - have any functionality yet: - <variablelist> - <varlistentry> - <term><guimenuitem>Font</guimenuitem></term> - <listitem><para> - FIXME: ? - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Paragraph</guimenuitem></term> - <listitem><para> - FIXME: ? - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-cal-editor-tools"> - <title>The Appointment Editor's Tools Menu</title> - <para> - This menu contains four items, including the - <guisubmenu>Forms</guisubmenu> submenu, which allows you to - alter calendar forms and create your own entries. None of - this works yet, though. - - <variablelist> - - <varlistentry> - <term><guimenuitem>Spelling</guimenuitem></term> - <listitem><para> - Checks the spelling of your calendar entry. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Check Names</guimenuitem></term> - <listitem><para> Checks the names listed here against - those in your address book. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Address Book</guimenuitem></term> - <listitem><para> - FIXME: ? - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guisubmenu>Forms</guisubmenu> Submenu</term> - <listitem><para> - The Forms submenu lets you alter the - appearance of Calendar Forms. - </para></listitem> - </varlistentry> - </variablelist> - - </para> - </sect2> - - <sect2 id="menuref-cal-editor-actions"> - <title>The Appointment Editor's Actions Menu</title> - <para> - This menu contains: - - <variablelist> - <varlistentry> - <term><guimenuitem>Schedule Meeting</guimenuitem></term> - <listitem><para> - Brings up the <interface>Meeting Invitation</interface> window, - described in <xref linkend="usage-calendar-apts">. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Cancel Invitation</guimenuitem></term> - <listitem><para> - Cancels the event, notifying all attendees. You may be prompted - to specify an invitation message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Forward as vCalendar</guimenuitem></term> - <listitem><para> - Opens the message composer with the current event attached. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Forward as Text</guimenuitem></term> - <listitem><para> - Opens the message composer with a text description of the current - event included in the message body. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-cal-editor-help"> - <title>The Appointment Editor's File Menu</title> - <para> - This menu is empty. - </para> - </sect2> - - </sect1> - - <sect1> - <title>Contact Manager Menus</title> - <para> - The contact manager has six menus: <guimenu>File</guimenu>, - <guimenu>Edit</guimenu>, <guimenu>View</guimenu>, - <guimenu>Setting</guimenu>s, <guimenu>Tools</guimenu>, and - <guimenu>Help</guimenu>. - </para> - - <sect2 id="menuref-contact-edit"> - <title>Contact Manager Edit Menu</title> - <para> - This menu is empty. - </para> - </sect2> - - - <sect2 id="menuref-contact-view"> - <title>Contact Manager View Menu</title> - <para> - This menu contains the following items: - - <variablelist> - <varlistentry> - <term><guimenuitem>Show Shortcut Bar</guimenuitem></term> - <listitem><para> - Toggle the Shortcut Bar on and off with this item. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Show Folder Bar</guimenuitem></term> - <listitem><para> - Toggle the folder bar on and off with this item. - See <xref linkend="usage-mainwindow-folderbar"> for - more information about the folder bar. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>As Table</guimenuitem> / <guimenuitem>As Minicards</guimenuitem></term> - <listitem><para> - View your contacts as a table. - When in table-view mode, this menu item reads - <guimenuitem>As Minicards</guimenuitem>, and changes the view - back to the minicard format. - </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="menuref-contact-tools"> - <title>Contact Manager Tools Menu</title> - <para> - This menu contains one item: - - <variablelist> - <varlistentry> - <term><guimenuitem>Search for - Contacts</guimenuitem></term> <listitem><para> Brings up - the in-depth search window. <xref - linkend="contact-search"> describes how to use this - feature. </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - - - <sect2 id="menuref-contact-actions"> - <title>Contact Manager Tools Menu</title> - <para> - This menu contains only one item: - - <variablelist> - <varlistentry> - <term><guimenuitem>New Directory Server</guimenuitem></term> <listitem><para> Brings up - the in-depth search window. <xref - linkend="config-prefs-contact-ldap-add"> describes how to use this - feature. </para></listitem> - </varlistentry> - </variablelist> - - </para> - </sect2> - </sect1> - - <sect1 id="menuref-contact-editor"> - <title>The Contact Editor Menus</title> - <para> - This window has only one menu: the file menu. - </para> - - <sect2 id="menuref-contact-editor-file"> - <title>Contact Editor File Menu</title> - <para> - This menu contains five items: - <variablelist> - - <varlistentry> - <term><guimenuitem>Save</guimenuitem></term> - <listitem><para> - - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Save As</guimenuitem></term> - <listitem><para> - Allows you to save the contact as an external - file in the <glossterm linkend="vcard">VCard</glossterm> format. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Print</guimenuitem></term> - <listitem><para> - Prints the current contact. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Delete</guimenuitem></term> - <listitem><para> - Deletes the current contact. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guimenuitem>Close</guimenuitem></term> - <listitem><para> - Closes the Contact Editor without saving. - </para></listitem> - </varlistentry> - - </variablelist> - </para> - </sect2> - </sect1> - - -</chapter> - - - - - - - diff --git a/help/C/preface.sgml b/help/C/preface.sgml deleted file mode 100644 index ddb6a0d2dd..0000000000 --- a/help/C/preface.sgml +++ /dev/null @@ -1,438 +0,0 @@ -<!-- -<!DOCTYPE preface PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> - - <preface id="introduction"> -<!-- =============Introduction ============================= --> - <title>Introduction</title> - - <sect1 id="what"> - <title>What is Evolution, and What Can It Do for Me?</title> - <para> - Information is useless unless it's organized and accessible; - it's hardly even worth the name if you can't look at it and be - <emphasis>informed</emphasis>. - <application>Evolution</application>'s goal is to make the - tasks of storing, organizing, and retrieving your personal - information easier, so you can work and communicate with - others. That is, it's a highly evolved <glossterm - linkend="groupware">groupware</glossterm> program, an integral - part of the Internet-connected desktop. On the inside, it's a - powerful database; on the outside, it's a tool to help you get - your work done. - </para> - <para> - Because it's part of the GNOME project, - <application>Evolution</application> is Free Software. The - program and its source code are released under the terms of - the GNU <ulink type="help" url="gnome-help:gpl"><citetitle>General - Public License (GPL)</citetitle></ulink>, and the - documentation falls under the <ulink type="help" - url="gnome-help:fdl"><citetitle>Free Documentation - License</citetitle></ulink> (FDL). For more information about - the GPL and the FDL, visit the Free Software Foundation's - website at <ulink - url="http://www.fsf.org">http://www.fsf.org</ulink>. - </para> - <para> - <note> - <title>This is a preview release</title> - <para> - <application>Evolution</application> is not complete, and - still has a lot of flaws. Please help improve it by - letting us know about them. You should do this by - submitting bug reports with the GNOME <application>Bug - Report Tool</application> (known as - <command>bug-buddy</command> at the command line). - </para> - </note> - </para> - - <para> - <application>Evolution</application> can help you work in a - group by handling email, address and other contact - information, and one or more calendars. It can do that on one - or several computers, connected directly or over a network, - for one person or for large groups. - </para> - <para> - The <application>Evolution</application> project has four - central goals: - - <itemizedlist> - <listitem> - <para> - The application must be <emphasis>both powerful and easy - to use</emphasis>. In other words, it needs a familiar - and intuitive interface that users can customize to their - liking, and users should have access to shortcuts for - complex tasks. - </para> - </listitem> - <listitem> - <para> - <application>Evolution</application> must meet and - exceed the standards set by other groupware products. - It must include support for major network <glossterm - linkend="protocol">protocols</glossterm> so that it can - integrate seamlessly with existing hardware and network - environments. - </para> - </listitem> - <listitem> - <para> - The project must support open standards and be open to - expansion, so that it can become a development platform - as well as an application. From the simplest scripting - to the most complex network and component programming, - <application>Evolution</application> must offer - developers an environment for cutting-edge application - development. - </para> - </listitem> - <listitem> - <para> - Data must be safe: <application>Evolution</application> - must not lose mail, corrupt mailbox files or other - data, execute arbitrary <glossterm linkend="script">scripts</glossterm>, - or delete files from your hard disk. - </para> - </listitem> - </itemizedlist> - </para> - <para> - <application>Evolution</application> is designed to make most - daily tasks faster. For example, it takes only one or two - clicks to enter an appointment or an address card sent to you - by email, or to send email to a contact or appointment. - <application>Evolution</application> makes displays faster and - more efficient, so searches are faster and memory usage is - lower. People who get lots of mail will appreciate advanced - features like <link - linkend="usage-mail-organize-vFolders">Virtual Folders</link>, - which let you save searches as though they were ordinary mail - folders. - </para> - - </sect1> - - <sect1 id="aboutbook"> - <title>About This Book</title> - <!-- ************** FOLLOWING PARAGRAPH FOR DRAFT ONLY ************* --> - <para> - This version of the <application>Evolution</application> - User's Guide is a <emphasis>draft</emphasis>. It describes - version 0.6 of the software. It is missing huge - chunks of information, and many of the features it describes - are unimplemented. All the content is subject to change, - especially if you help. Please send comments on the guide to - <email>aaron@ximian.com</email>. If you would like to work - on the guide please contact me or see the GNOME Documentation - project <ulink - url="http://developer.gnome.org/projects/gdp">web - site</ulink>. This paragraph will be removed in later - versions of the manual. - </para> - <!-- ************* END DRAFT ONLY PARAGRAPH ************** --> - - <para> - This book is divided into two parts, with several - appendices. The first part is a <link linkend="usage">guided - tour</link>— it will explain how to use - <application>Evolution</application>. If you are new to - <application>Evolution</application> or to groupware in - general, this section is for you. The second section, covering - <link linkend="config">configuration</link>, is targeted at - more advanced users, but anyone who wants to change the way - <application>Evolution</application> looks or acts can benefit - from reading it. In addition, there is a comprehensive <link - linkend="menuref">menu reference</link> which describes nearly - every capability that <application>Evolution</application> has - to offer. - </para> - <formalpara> - <title>Typographical conventions</title> - <para> - Some kinds of words are marked off with special typography: - <simplelist> - <member><application>Applications</application></member> - <member><command>Commands</command> typed at the command line</member> - <member><guilabel>Labels</guilabel> for interface items</member> - - <member> Menu selections look like this: - <menuchoice> - <guimenu>Menu</guimenu> - <guisubmenu>Submenu</guisubmenu> - <guimenuitem>Menu Item</guimenuitem> - </menuchoice> - </member> - <member><guibutton>Buttons</guibutton> you can - click</member> <member><userinput>Anything you type - in</userinput></member> <member><computeroutput>Text - output from a computer</computeroutput></member> - <member><glossterm linkend="apx-gloss">Words</glossterm> - that are defined in the <xref linkend="apx-gloss">.</member> - </simplelist> - </para> - </formalpara> - </sect1> - <sect1 id="commontasks"> - <title>Quick Reference for Common Tasks</title> - <para> - You might want to copy this section and tape it to - the wall next to your computer: it's a very short summary of - most of the things you'll want to do with - <application>Evolution</application>, and pointers to the - sections of the book where you'll find more in-depth - description of those tasks. - </para> - <sect2 id="quickref-newthings"> - <title>Opening or Creating Anything</title> - <para> - Here are the keyboard shortcuts and menu items you're most - likely to use: - - <variablelist> - - <varlistentry> - <term>Create a new folder</term> - <listitem>` - <para> - <menuchoice><guimenu>File</guimenu><guisubmenu>New</guisubmenu> - <guimenuitem>Folder</guimenuitem></menuchoice> or - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>Shift </keycap> - <keycap>F</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Create a new Shortcut in the Evolution Bar</term> - <listitem> - <para> - <menuchoice><guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> - <guimenuitem>Evolution Bar Shortcut</guimenuitem> </menuchoice> or - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>Shift</keycap> - <keycap>S</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Create a new email message:</term> - <listitem> - <para> - Use - <menuchoice><guimenu>File</guimenu><guisubmenu>New</guisubmenu><guimenuitem>Mail - Message</guimenuitem> </menuchoice> or - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>Shift </keycap> - <keycap>M</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Create a new Appointment</term> - <listitem> - <para> - <menuchoice><guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> - <guimenuitem>Appointment</guimenuitem> </menuchoice> or - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>Shift</keycap> - <keycap>A</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>Enter a new Contact</term> - <listitem> - <para> - <menuchoice><guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> - <guimenuitem>Contact</guimenuitem> </menuchoice> or - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>Shift</keycap> - <keycap>C</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term>Create a new Task</term> - <listitem> - <para> - <menuchoice><guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> - <guimenuitem>Task</guimenuitem> </menuchoice> or - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>Shift</keycap> - <keycap>T</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - </variablelist> - </para> - </sect2> - <sect2 id="quickref-mail"> - <title>Mail Tasks</title> - <para> - Here are the most frequent email tasks, and shortcuts for - navigating your mailbox with the keyboard instead of the - mouse: - <variablelist> - <varlistentry> - <term>Check Mail</term> - <listitem> - <para> - Click <guibutton>Get Mail</guibutton> in the - toolbar. There is no keyboard shortcut for this task, - but you can ask <application>Evolution</application> - to check for new mail periodically. To do so, FIXME. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Reply to a Message</term> - <listitem> - <para> - To reply to the sender of the message only: - click <guibutton>Reply</guibutton> in the - toolbar, or press - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>R</keycap> - </keycombo> - </para> - <para> - To reply to the sender and all the other visible - recipients of the message, click <guibutton>Reply to - All</guibutton> or select the message and press - <keycombo action="simul"> - <keycap>Shift</keycap> - <keycap>Ctrl</keycap> - <keycap>R</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Forward a Message</term> - <listitem> - <para> - Select the message or messages you want to forward, - and click <guibutton>Forward</guibutton> in the - toolbar, or press - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>J</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Open a Message in a New Window</term> - <listitem> - <para> - Double-click the message you want to view, or select - it and press - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>O</keycap> - </keycombo> - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Create Filters and Virtual Folders</term> - <listitem> - <para> - You can create filters and Virtual Folders based on - specific message attributes from the message's - right-click menu. Alternately, select a message, and - then choose <menuchoice> <guimenu>Settings</guimenu> - <guimenuitem>Mail Filters</guimenuitem> </menuchoice> - or <menuchoice> <guimenu>Settings</guimenu> - <guimenuitem>Virtual Folder Editor</guimenuitem> - </menuchoice>. Filters are discussed in <xref - linkend="usage-mail-organize-filters">, and Virtual - Folders in <xref - linkend="usage-mail-organize-vfolders">. - </para> - </listitem> - </varlistentry> - </variablelist> - - </para> - </sect2> - <sect2 id="quickref-cal"> - <title>Calendar</title> - <para> - <variablelist> - <varlistentry> - <term></term> - <listitem> - <para> - </para> - </listitem> - </varlistentry> - </variablelist> - - </para> - </sect2> - <sect2 id="quickref-contact"> - <title>Contact Manager</title> - <para> - - - <variablelist> - <varlistentry> - <term></term> - <listitem> - <para> - </para> - </listitem> - </varlistentry> - </variablelist> - - - </para> - </sect2> - </sect1> - </preface> - - - - - - - - - - - - diff --git a/help/C/usage-calendar.sgml b/help/C/usage-calendar.sgml deleted file mode 100644 index a2c14e99a6..0000000000 --- a/help/C/usage-calendar.sgml +++ /dev/null @@ -1,371 +0,0 @@ -<!-- -<!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> - -<chapter id="usage-calendar"> - <title>The Evolution Calendar</title> - <para> - To begin using the calendar, select - <guibutton>Calendar</guibutton> from the <interface>shortcut - bar</interface>. By default, the calendar starts showing today's - schedule on a ruled background. At the upper right, there's a - monthly calendar you can use to switch days. Below that, there's - a <guilabel>TaskPad</guilabel>, where you can keep a list of tasks - seperate from your calendar appointments. The calendar's daily - view is shown in <xref linkend="usage-calendar-fig">. - - <!-- ============== Figure ============================= --> - <figure id="usage-calendar-fig"> - <title>Evolution Calendar View</title> - <screenshot> - <screeninfo>Evolution Contact Manager Window</screeninfo> - <graphic fileref="fig/calendar" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - <!-- ============== End of Figure ============================= --> - - </para> - <sect1 id ="usage-calendar-view"> - <title>Ways of Looking at your Calendar</title> - - <para> - The toolbar offers you four different views of your calendar: - one day, five days, a week, or a month at once. Press the - calendar-shaped buttons on the right side of the toolbar to - switch between views. You can also select a range of - days— three days, ten days, a fortnight if you want - — in the small calendar at the upper right. - </para> - <para> - The <guibutton>Prev</guibutton> and <guibutton>Next</guibutton> - buttons will move you forward and back in your calendar pages. - If you're looking at only one day, you'll see tomorrow's page, - or yesterday's. If you're looking at your calendar by week, - month, fortnight, or anything else, you'll move around by just - that much. To come back to today's listing, click - <guibutton>Today</guibutton>. - </para> - <para> - To visit a specific date's calendar entries, click - <guibutton>Go To</guibutton> and select the date in the dialog - box that appears. - </para> - - -<!-- ############### FIXME FIXME FIXME ############ -Feature not yet implemented, and may not be implemented due to -lack of time, resources, and interest. - <para> - In addition, <application>Evolution</application> supports - Hebrew, Muslim, and other calendar formats. To switch to a - different calendar format, choose - <guimenuitem>GUIMENUITEM</guimenuitem> from the - <guimenu>GUIMENU</guimenu>. - </para> -################ END FIXME AREA ################## --> - - </sect1> - <sect1 id="usage-calendar-apts"> - <title>Scheduling With the Evolution Calendar</title> - <para> - Of course, you'll want to use the calendar to do more than find - out what day it is. This section will tell you how to schedule - events, set alarms, and determine event recurrence. - </para> - <sect2 id="usage-calendar-apts-basic"> - <title>Creating events</title> - <para> - To create a new calendar event, select - <menuchoice> - <guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> - <guimenuitem>Appointment</guimenuitem> - </menuchoice> - or click the <guibutton>New</guibutton> button on the left end - of the toolbar. The <interface>New Appointment</interface> - dialog will pop up with the usual menu bar, tool bar, and - window full of choices for you. - </para> - <tip id="new-appointment-shortcut"> - <title>Shortcut</title> - <para> - If you don't need to enter more information than the date - and time of the appointment, you just click in any blank - space in the calendar and start typing. You can enter other - information later with the appointment editor. - </para> - </tip> - - <para> - Your event must have a starting and ending date — by - default, today — but you can choose whether to give it - starting and ending times or to mark it as an <guilabel>All - day event</guilabel>. An <guilabel>All day event</guilabel> - appears at the top of a day's event list rather than inside - it. That makes it easy to have events that overlap and fit - inside each other. For example, a conference might be an all - day event, and the meetings at the conference would be timed - events. Of course, events with specific starting and ending - times can also overlap. When they do they're displayed as - multiple columns in the day view of the calendar. - </para> - <note> - <title>Doing Two Things At Once</title> - <para> - If you create calendar events that overlap, - <application>Evolution</application> will display them side - by side in your calendar. However, - <application>Evolution</application> cannot help you do - multiple things at once. - </para> - </note> - <para> - You can have as many as four different - <guilabel>Alarms</guilabel>, any time prior to the event - you've scheduled. You can have one alarm of each type: - <variablelist> - <varlistentry> - <term><guilabel>Display</guilabel></term> - <listitem> - <para> - A window will pop up on your screen to remind you of - your event. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Audio</guilabel></term> - <listitem> - <para> - Choose this to have your computer deliver a sound - alarm. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Program</guilabel></term> - <listitem> - <para> - Select this if you would like to run a program as a - reminder. You can enter its name in the text field, - or find it with the <guibutton>Browse</guibutton> - button. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Mail</guilabel></term> - <listitem> - <para> - <application>Evolution</application> will send an - email reminder to the address you enter into the text - field. - </para> - </listitem> - </varlistentry> - </variablelist> - - </para> - <para> - <guilabel>Classification</guilabel> is a little more - complicated, and only applies to calendars on a - network. <guilabel>Public</guilabel> is the default category, - and a public event can be viewed by anyone on the calendar - sharing network. <guilabel>Private</guilabel> denotes one - level of security, and <guilabel>Confidential</guilabel> a - higher level. <!-- FIXME --> Exact determinations and - implementations of this feature have yet to be - determined. <!-- FIXME --> - </para> - <para> - The <guilabel>Recurrence</guilabel> tab lets you describe - repetition in events ranging from once every day up to once - every 100 years. You can then choose a time and date when the - event will stop recurring, and, under - <guilabel>Exceptions</guilabel>, pick individual days when the - event will <emphasis>not</emphasis> recur. Make your - selections from left to right, and you'll form a sentence: - "Every two weeks on Monday and Friday until January 3, 2003" - or "Every month on the first Friday for 12 occurrences." - </para> - - <para> - Once you're done with all those settings, click on the disk - icon in the toolbar. That will save the event and close the - event editor window. If you want, you can alter an event - summary in the calendar view by clicking on it and typing. You - can change other settings by right-clicking on the event then - choosing <guimenuitem>Edit this Appointment</guimenuitem>. - </para> - </sect2> - -<!-- ############UNIMPLEMENTED FEATURES ################### - - <sect2 id="usage-calendar-apts-group"> - <title>Appointments for Groups</title> - <para> - 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. - </para> - <note> - <title>Unimplemented Feature</title> - <para>This feature is not yet implemented.</para> - </note> - - <para> - In addition, you can use <application>Evolution</application> - to mark a meeting request on another person's calendar. To do - it, click <guibutton>New</guibutton> in the calendar toolbar, - or select <menuchoice> <guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> - <guimenuitem>Appointment</guimenuitem> </menuchoice> to bring - up the <interface>new event</interface> window. Then describe - the event as you would any other. Before you click - <guibutton>OK</guibutton>, (INSERT DESCRIPTION HERE...). - <application>Evolution</application> 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. - </para> - <para> - To mark a tentative event as confirmed, click once on the - event in the <interface>calendar view</interface> to select - it, and then choose <guimenuitem>Event - Properties</guimenuitem> from the <guimenu>Settings</guimenu> - menu. In the <interface>Event Properties</interface> dialog - window, click the "tentative" button to De-select the - event. - </para> - </sect2> - - - <sect2 id="usage-calendar-apts-privs"> - <title>Scheduling privileges</title> - <para> - 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. - </para> - </sect2> - ########## END UNIMPLEMENTED FEATURESET ############ --> - - </sect1> - - <sect1 id="usage-calendar-todo"> - <title>The Task Pad</title> - <para> - The Task Pad, located in the lower right corner of the - calendar, lets you keep a list of tasks separate from your - calendar events. Tasks are colored and sorted by priority and - due-date (see <xref linkend="config-prefs"> for more - information), and are included with calendar data during - synchronization with a hand-held device. You can use the list - in a larger format by choosing the <guibutton>Tasks</guibutton> - button in the shortcut bar or in the folder tree. - </para> - <para> - To record a new task, click the <guibutton>Add</guibutton> - button below the list. <application>Evolution</application> - will pop up a small window with five items in it: - - <variablelist> - <varlistentry> - <term> <guilabel>Summary:</guilabel></term> - <listitem> - <para> - The description you enter here will appear in the To Do - list itself. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term> <guilabel>Due Date:</guilabel></term> - <listitem> - <para> - Decide when this item is - due. You can either type in a date and time, or select one from - the <guibutton>Calendar</guibutton> and time drop-down menus. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Priority:</guilabel></term> - <listitem> - <para> - Select a level of importance from 1 (most important) to 9 - (least important). - </para> - </listitem> - </varlistentry> - <varlistentry> - <term> <guilabel>Item Comments:</guilabel></term> - <listitem> - <para> - If you wish, you can keep a more detailed description of - the item here. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - <para> - Once you've added a task to your to-do list, its summary - appears in the <guilabel>Summary</guilabel> section of task - list. To view or edit a detailed description of an item, - double-click on it, or select it and click - <guibutton>Edit</guibutton>. You can delete items by selecting - them and clicking on the <guibutton>Delete</guibutton> button. - </para> - </sect1> - - <sect1 id="usage-calendar-multiple"> - <title>Multiple Calendars</title> - <para> - <application>Evolution</application> permits you to have and - maintain multiple calendars. This is useful if you maintain - schedules for other people, if you are responsible for resource - or room allocation, or if you have multiple personalities. - </para> - - <example> - <title>Keeping Multiple Calendars</title> - <para> - Keelyn, the office manager for a small company, has one - calendar for her own schedule. On the local network, she - maintains one for the conference room, so people know when - they can schedule meetings. Next to that, she maintains a - calendar that reflects when consultants are going to be on - site, and another that keeps track of when the Red Sox are - playing. - </para> - </example> - <para> - To create a new calendar, select - <menuchoice> - <guimenu>File</guimenu> <guisubmenu>New</guisubmenu> - <guimenuitem>Calendar</guimenuitem> - </menuchoice>. - You can place the calendar in any calendar folder and access it - from the folder view. Alarms, configuration, and display for - each calendar are separate from each other. - </para> - - </sect1> -</chapter> - - - - - - - - - - diff --git a/help/C/usage-contact.sgml b/help/C/usage-contact.sgml deleted file mode 100644 index 0c6b976e4d..0000000000 --- a/help/C/usage-contact.sgml +++ /dev/null @@ -1,617 +0,0 @@ -<!-- -<!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> - -<chapter id="usage-contact"> - <title>The Evolution Address Book</title> - <abstract> - <para> - The <application>Evolution</application> address book can - handle all of the functions of an address book, phone book, or - Rolodex. Of course, it's a lot easier to update - <application>Evolution</application> than it is to change an - actual paper book. <application>Evolution</application> also - allows easy synchronization with hand-held devices. Since - <application>Evolution</application> supports the <glossterm - linkend="ldap">LDAP</glossterm> directory protocol, you can use - it with almost any type of existing directory server on your - network. - </para> - <para> - Another advantage of the <application>Evolution</application> - address book is its integration with the rest of the - application. When you look for someone's address, you can also - see a history of appointments with that person. Or, you can - create address cards from emails with just a few clicks. In - addition, searches and folders work in the same way they do in - the rest of Evolution. - </para> - <para> - This chapter will show you how to use the - <application>Evolution</application> address book to organize - any amount of contact information, share addresses over a - network, and several ways to save time with everyday tasks. To - learn about configuring the address book, see <xref - linkend="config-prefs-contact">. - </para> - </abstract> - <sect1 id="usage-contact-basic"> - <title>Getting Started With the Address Book</title> - - <para> - To open up your address book, click on - <guibutton>Contacts</guibutton> in the shortcut bar, or select - one of your contacts folders from the folder bar. <xref - linkend="usage-contact-fig"> shows the address book in all - its organizational glory. By default, the address book - shows all your cards in alphabetical order, in a <glossterm - linkend="minicard">minicard</glossterm> format. You can select - other views from the <guimenu>View</guimenu> menu, and adjust - the width of the columns by clicking and dragging the grey - column dividers. - </para> - - - <figure id="usage-contact-fig"> - <title>Evolution Address Book</title> - <screenshot> - <screeninfo>Evolution Address Book Window</screeninfo> - <graphic fileref="fig/contact" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - - <para> - The toolbar for the address book is quite simple: - <itemizedlist> - <listitem><para> - <guibutton>New</guibutton> creates a new card. - </para></listitem> - - <listitem><para> - <guibutton>Find</guibutton> brings up an in-depth search window. - </para></listitem> - - <listitem><para> - <guibutton>Print</guibutton> sends one or more of your cards to the printer. - </para></listitem> - <listitem><para> - <guibutton>Delete</guibutton> deletes a selected card. - </para></listitem> - - <listitem><para> <guibutton>View All</guibutton> displays all - the address information in the folder. Use this button to - refresh the display for a network folder, or to switch from - viewing the results of a search and see the whole contents. - </para></listitem> - - <listitem><para> <guibutton>Stop</guibutton> stops loading - contact data from the network. This button is only - relevant if you are looking at contact information on a - network. </para></listitem> - </itemizedlist> - </para> - - <para> - Your contact information fills the rest of the display. Move - through the cards alphabetically with the buttons and the - scrollbar at the right of the window. Of course, if you have - more than a few people listed, you'll want some way of finding - them more quickly, which is why there's a search feature. - </para> - - <sect2 id="contact-search"> - <title>Searching for Contacts</title> - <para> - Between <guilabel>Delete</guilabel> and <guilabel>View - All</guilabel> is a quick search field. To use it, select - from the drop-down list which sort of search you'd like to - perform (the whole card, just the name, or just the email - address), then enter one or more words in the text entry - box, and press <keycap>Enter</keycap>. - <application>Evolution</application> will search through - the contents of every displayed card to find one that - matches. You can refine searches by doing several in - succession, or start over by pressing the <guibutton>View - All</guibutton> button. - </para> - <para> - If there are no matches, the card display will be - blank. When you'd like to see all the cards again, press - <guilabel>Show All</guilabel>. - </para> - <example id="contact-quicksearch-ex"> - <title>Refining a Quick Search</title> - <para> - Tom comes back from lunch and finds a note on his - keyboard: "Curtis in sales called for you, but he didn't - leave a number, and I forgot to write down the name of the - company he works for. He said it was important, though." - Tom is not at all annoyed. - </para> - <para> - He opens his contacts folder, and runs a quick search for - "Curtis." There are eighteen different people with that name - in the file. He then enters "Sales," and - <application>Evolution</application> narrows it down to the - right Curtis. He only becomes annoyed when he discovers that - the call was not actually important. - </para> - </example> - - <para> - If you prefer to perform a more complex search, press - <guibutton>Find</guibutton> or choose - <menuchoice><guimenu>Tools</guimenu><guimenuitem>Search for - Contact</guimenuitem></menuchoice>. This will open the - in-depth search window, which lets you use multiple search - criteria in the same way that email filters and <glossterm - linkend="vfolder">virtual folders</glossterm> do.. </para> - <para> - Click <guibutton>Add Criterion</guibutton> to increase the - number of criteria you'd like to use in the search, and - <guibutton>Remove Criterion</guibutton> to remove one from the - bottom of the list. Your criteria may be a search within the - <guilabel>Name</guilabel> or <guilabel>Email</guilabel> - fields; alternately you can choose to search through all the - fields with a regular expression. Then, you can select from - all the familiar requirements like <guilabel>Begins - With</guilabel> and <guilabel>Does Not Contain</guilabel>, - decide whether to match <guilabel>All</guilabel> or - <guilabel>Any</guilabel> of your criteria, and press - <guibutton>Search</guibutton> to set it all off. - </para> - - </sect2> - - </sect1> - <sect1 id="usage-contact-cards"> - <title>Destroy, Create, and Change: The Contact Editor</title> - <para> - To delete a card, click on it once to select it, then press the - <guibutton>Delete</guibutton> button. If you have multiple - cards selected, you'll delete multiple cards. - </para> - <para> - If you want to add or change cards, you'll use the contact - editor. To change a card that already exists, double click on - it to open the contact editor window with all the current - information already filled in. If you want to create a new - one, clicking the <guibutton>New</guibutton> button in the - toolbar will open the same window, with blank entry boxes for - you to fill in. - </para> - - <para> - The contact editor window has two tabs, - <guilabel>General</guilabel>, for basic contact information, - and <guilabel>Details</guilabel>, for a more specific - description of the person. In addition, it contains a - <guimenu>File</guimenu> menu, (see <xref - linkend="menuref-contact-editor">) and a toolbar with three - items: <guilabel>Save and Close</guilabel>, - <guilabel>Print</guilabel>, and <guilabel>Delete</guilabel>. - </para> - - <figure id="usage-contact-editor-fig"> - <title>Evolution Contact Editor</title> - <screenshot> - <screeninfo>Evolution Contact Editor</screeninfo> - <graphic fileref="fig/contact-editor.png" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - - <para> The <guilabel>General</guilabel> tab has seven sections, - each with an icon: a face, for name and company; a telephone - for phone numbers; an envelope for email address; a globe for - web page address; a house for postal address; a file folder - for contacts, and a briefcase for categories. - </para> - <para> - <variablelist> - - <varlistentry> - <term>Full Name</term> - <listitem> - <para> - The <guilabel>Full Name</guilabel> field has two - major features: - <itemizedlist> - <listitem> - <para> - You can enter a name into the <guibutton>Full - Name</guibutton> field, but you can also click the - <guibutton>Full Name</guibutton> button to bring - up a small dialog box with a few text boxes - <variablelist> - <varlistentry> - <term><guilabel>Title: </guilabel></term> - <listitem> <para> - Enter an honorific or select one from the menu. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guilabel>First: </guilabel></term> - <listitem> <para> - Enter the first, or given, name. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Middle: </guilabel></term> - <listitem> <para> - Enter the middle name or initial, if any. - </para></listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Last: </guilabel></term> - <listitem> <para> - Enter the last name (surname). - </para></listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Suffix: </guilabel></term> - <listitem> <para> - Enter suffixes such as "Jr." or "III." - </para></listitem> - </varlistentry> - </variablelist> - </para> - </listitem> - <listitem> - <para> - The <guilabel>Full Name</guilabel> field also - interacts with the <guilabel>File As</guilabel> - box to help you organize your contacts. - </para> - <para> - To see how it works, type a name in the - <guilabel>Full Name</guilabel> field: - <userinput>Rupert T. Monkey</userinput>. You'll - notice that the <guilabel>File As</guilabel> field - also fills up, but in reverse: - <computeroutput>Monkey, Rupert</computeroutput>. - You can pick <computeroutput>Rupert Monkey - </computeroutput> from the drop-down, or type in - your own, such as <userinput> T. Rupert Monkey - </userinput>. - </para> - <tip> - <title>Filing Suggestion</title> - - <para> - Don't enter something entirely different from - the actual name, since you might forget that - you've filed Rupert's information under "F" for - "Fictitious Ximian Employee." - </para> - </tip> - </listitem> - </itemizedlist> - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Multiple Values for Fields</term> - <listitem> - <para> - If you click on the small arrow buttons next to the - <guilabel>Primary Email</guilabel> field, you can also - choose <guilabel>Email 2</guilabel> and - <guilabel>Email 3</guilabel>. Although the contact - editor will only display one of those at any given - time, <application>Evolution</application> will - store them all. The arrow buttons next to the - telephone and postal address fields work in the same - way. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - <para> - The last item in the <guilabel>General</guilabel> tab is the - <guilabel>Categories</guilabel> organization tool; for - information on that, read <xref - linkend="usage-contact-organize">. - </para> - <para> - The <guilabel>Details</guilabel> tab is, fortunately, much more - simple: three sections, all of which are more or less obvious: - the briefcase next to the details about the contact's - professional life; the face next to the details about their - personal life; the globe next to a big blank space you can use - for anything and everything else you'd like to note about them. - If you ever wanted to have that uncanny knack for remembering - obscure details like the date of someone's anniversary (perhaps - your own) this is the way to develop it. - </para> - - - - -<!--- ############# This section isn't implemented yet either: - <sect2> - <title></title> - <para> - <tip> - <title>Contact Shortcuts</title> - <para> - 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 - <guimenuitem>Create Card for this Address</guimenuitem> or - <guimenuitem>Create Card for this Sender</guimenuitem> - from the menu. While looking at a calendar appointment, - right-click any email address, and choose - <guimenuitem>Create Card for this Address</guimenuitem>. - (NOTE that feature may change! unimplemented!) - </para> - </tip> - </para> - <para> - You can move cards around just as you would move email - messages: dragging and dropping works, as does right-clicking - and choosing <guimenuitem>Move</guimenuitem> from the menu - that appears. - </para> - </sect2> -############### SHORTCUT SECTION COMMENTED OUT FOR NOW --> - - </sect1> - - <sect1 id="usage-contact-organize"> - <title>Organizing your Address Book</title> - <para> - Organizing your address book is a lot like organizing your - mail. You can have folders and searches the same way you can - with mail, but the address book does not allow vFolders. It - does, however, allow each card to fall under several - categories, and allow you to create your own categories. To - learn about categories, read <xref - linkend="usage-contact-organize-group-category">. - </para> - -<!-- - <para> - Another useful <application>Evolution</application> feature is - its ability to recognize when people live or work together. If - several people in your address book share an address, and you - change the address for one of them, - <application>Evolution</application> will ask you if you wish to - change the address for all of them, or just for one. - </para> ---> - - <sect2 id="usage-contact-organize-group"> - <title>Groups of contacts</title> - <para> - <application>Evolution</application> offers two ways for you - to organize your cards. The first way is to use folders; - this works the same way that mail folders do. For more - flexibility, you can also mark contacts as members of - different categories. - </para> - - <sect3 id="usage-contact-organize-group-folder"> - <title>Grouping with Folders</title> - <para> - The simplest way to group address cards is to use folders. - By default, cards start in the - <guilabel>Contacts</guilabel> folder. If you've read <xref - linkend="usage-mainwindow"> then you already know that you - can create a new folder by selecting - <menuchoice> - <guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> - <guimenuitem>Folder</guimenuitem> - </menuchoice> - and that you can put new folders anywhere you like. Just - like with mail, cards must be in a card folder, and no card - can be in two places at once. If you want more - flexibility, try <xref - linkend="usage-contact-organize-group-category">. - </para> - <para> - To put a card into a folder, just drag it there from the - folder view. Remember that contact cards can only go in - contact folders, just like mail can only go in mail folders, - and calendars in calendar folders. - </para> - </sect3> - - <sect3 id="usage-contact-organize-group-category"> - <title>Grouping with Categories</title> - <para> - 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. - </para> - <para> - To mark a card as belonging to a category, click the - <guibutton>Categories</guibutton> button at the lower - right. From the dialog box that appears, you can check as - many or as few categories as you like. - </para> - <para> - Then, you can refer to all the cards in that category by: - <!-- FIXME --> Waiting for Evolution to support the - operation. - </para> - - <!-- FIXME: Feature Not Implemented - <para> - - If the master list of categories doesn't suit you, you can - add your own. Just enter the new category's name in the - text box, then click <guibutton>Categories</guibutton> and - choose <guilabel>Add to Master List</guilabel> in the - window that appears. - </para> - --> - - </sect3> - </sect2> - </sect1> - - <sect1 id="usage-contact-sharing"> - <title>Sharing your Cards</title> - <para> - If you keep your cards on a network using an <glossterm - linkend="ldap">LDAP</glossterm> server, you can share access to - them, browse other address books, or maintain a shared set of - contact information for your company or your department. 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 - share calendars as well as address books, people can avoid - duplicating work and keep up to date on developments within - their work-group or across the entire company. - </para> - - <example id="usage-contact-sharing-ex"> - <title>Sharing Address Cards and Calendar Data</title> - <para> - Ray wants to schedule a meeting with Company X, so he - checks the network for the Company X address card so he - knows whom to call there. Since his company also shares - calendars, he then learns that his co-worker Deanna has - already scheduled a meeting with Company X next Thursday. - He can either go to the meeting himself or ask Deanna to - discuss his concerns for him. Either way, he avoids - scheduling an extra meeting with Company X. - </para> - </example> - <para> - Of course, you don't want to share all of your cards— why - overload the network with a list of babysitters or tell - everyone in the office you're talking to new job prospects? If - you keep cards on your own computer, you can decide which items - you want to make accessible to others. - </para> - <para> - To learn how to add a remote directory to your available - contact folders, see <xref linkend="config-prefs-contact">. - Once you have a connection, the network contacts folder or - folders will appear inside the <guilabel>External - Directories</guilabel> folder in the folder bar. It will work - exactly like a local folder of cards, with the following - exceptions: - <itemizedlist> - - <listitem> - <para> - Network folders are only available when you are - connected to the network. If you use a laptop or have a - modem connection, you may wish to copy or cache the - network directory and then synchronize your copy with - the networked version periodically. <!-- FIXME: HOW? --> - </para> - </listitem> - - <listitem> - <para> - To prevent excess network traffic, - <application>Evolution</application> will not normally - load the contents of LDAP folders immediately upon - opening. You must click <guilabel>Display - All</guilabel> before LDAP folder cards will be loaded - from the network. You can change this behavior in the - <interface>Contact Preferences</interface> window. - </para> - </listitem> - <listitem> - <para> - Your ability to view, change, add, and delete contacts - depends on the settings of the LDAP server. - </para> - </listitem> - </itemizedlist> - </para> - </sect1> - - <sect1 id="usage-contact-automate"> - <title>Address Book Tools</title> - <para> - The address book works closely with - <application>Evolution</application>'s mail and calendar tools. - For example, you can use the address book to help you manage - mailing lists, and send or recieve address cards over email. - More tools are on the way, and when they arrive, <!-- FIXME --> - they will be described in this section. - </para> - - <sect2 id="contact-automation-basic"> - <title>Send me a Card: Adding New Cards Quickly</title> - <para> - As noted before, when you get information about a person in - the mail or in a calendar entry, you can add it to an address - card. To do so, right click on any email address or email - message, and select <guimenuitem>Add Address - Card</guimenuitem> from the menu that appears. Of course, - <application> Evolution</application> also adds cards from a - hand-held device during HotSync operation. For more - information about that, see <xref linkend="usage-sync">. - </para> - </sect2> - - <sect2 id="contact-automation-lists"> - <title>Managing a Mailing list</title> - <para> - You already know that when you are writing an email, you can - address it to one or more people, and that - <application>Evolution</application> will fill in addresses - from your address book's address cards if you let it. In - addition to that, you can send email to everyone in a - particular group if you choose. - </para> - -<!-- FIXME this feature not yet implemented - - <para> - You can also use the address book to print postal addresses - on mailing labels. Future versions of - <application>Evolution</application> 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 - mailings. - </para> - --> - - </sect2> -<!--- FIXME this feature not yet implemented - <sect2 id="usage-contact-automation-extra"> - <title>Map It!</title> - <para> - Need a map or directions? Click - <guibutton>MapIt</guibutton> from within the contact - manager, and <application>Evolution</application> will - map the address for you online. - </para> - </sect2> ---> - - - </sect1> - -</chapter> - - - - - - - - - - - - - - diff --git a/help/C/usage-exec-summary.sgml b/help/C/usage-exec-summary.sgml deleted file mode 100644 index 5ff67029d7..0000000000 --- a/help/C/usage-exec-summary.sgml +++ /dev/null @@ -1,91 +0,0 @@ -<chapter id="usage-exec-summary"> - <title>The Executive Summary</title> - <para> - The Evolution Executive Summary is designed to show you a - summary of important information: the appointments for a given - day, important email, and so forth. To see your executive - summary, click on the <guibutton>Executive Summary</guibutton> - button in the shortcut bar, or select the - <guilabel>executive-summary</guilabel> folder in the folder - bar. - </para> - - <sect1 id="exec-intro"> - <title>Introducing the Executive Summary</title> - <para> - The first thing you'll want to do with the executive summary - is add a service. Click the <guibutton>Add Service</guibutton> - button in the toolbar, then select one of the available - services. Services may vary depending upon your system, but - most installations will have at least the following options: - - <variablelist> - - <varlistentry> - <term>Calendar</term> - <listitem> - <para> - Pending appointments and other events. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Inbox</term> - <listitem> - <para> - Information about your mail, such as the number of - new messages you have waiting. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>To Do</term> - <listitem> - <para> - A short summary of your task pad. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>RDF Summary</term> - <listitem> - <para> - News headlines for any valid RDF file. The default - is news about the GNOME project from <ulink - url="www.gnome.org/gnome-news/">gnotices</ulink>. - </para> - </listitem> - </varlistentry> - - </variablelist> - - </para> - - <para> - Each service appears in a small box on the screen; you can - remove the service by clicking the <guibutton>x</guibutton> - button in the upper right, or bring up a settings dialog by - clicking the little wrench icon below that. - </para> - </sect1> - <sect1 id="exec-services-detail"> - <title>Services in Detail</title> - <para> - This section will show you how to use several - <application>Evolution</application> services. - - </para> - - </sect1> - -</chapter> - - - - - - - diff --git a/help/C/usage-mail.sgml b/help/C/usage-mail.sgml deleted file mode 100644 index 9ec12d9e5b..0000000000 --- a/help/C/usage-mail.sgml +++ /dev/null @@ -1,1539 +0,0 @@ -<!-- -<!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> - -<chapter id="usage-mail"> - <title>Evolution Mail</title> - <abstract> - <title> An Overview of the Evolution Mailer</title> - <para> - <application>Evolution</application> email is like other email - programs in all the ways you would hope: - <itemizedlist> - <listitem> - <para> - It can sort and organize your mail in a wide variety of ways with - folders, searches, and filters. - </para> - </listitem> - <listitem> - <para> - It can send and receive mail in HTML or as plain text, and - permits multiple file attachments. - </para> - </listitem> - <listitem> - <para> - It supports multiple mail sources, including <glossterm - linkend="imap">IMAP</glossterm>, <glossterm - linkend="pop">POP3</glossterm>, local - <systemitem><filename>mbox</filename></systemitem> and - <systemitem><filename>mh</filename></systemitem> files, and - even NNTP messages (newsgroups), which aren't technically - email. - </para> - </listitem> - </itemizedlist> - </para> - <para> - However, <application>Evolution</application> has some important - differences. First, it's built to handle very large amounts of - mail without slowing down or crashing. Both the <link - linkend="usage-mail-organize-filters">filtering</link> and <link - linkend="usage-mail-organize-search">searching</link> functions - were built for speed and efficiency on gargantuan volumes of - mail. There's also the <application>Evolution</application> - <link linkend="usage-mail-organize-vFolders">Virtual - Folder</link>, 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 this feature especially useful. - </para> - </abstract> - - <sect1 id="usage-mail-getnsend"> - <title>Reading, Getting and Sending Mail</title> - - <sect2 id="usage-mail-getnsend-read"> - <title>Reading Mail</title> - <para> - You can start reading email by clicking - <guibutton>Inbox</guibutton> in the shortcut bar. The first - time you use <application>Evolution</application>, it will - start with the <interface>Inbox</interface> open and show you a - message from Ximian welcoming you to the application. - </para> - <para> - Your <application>Evolution</application> - <guilabel>Inbox</guilabel> will look something like the one in - <xref linkend="usage-mail-intro-fig">. Just below the toolbar - is the <interface>message list</interface>, showing message - header information like <guilabel>Subject</guilabel> and - <guilabel>Date</guilabel>. The message itself appears below - that, in the <interface>view pane</interface>. If you find - the <interface>view pane</interface> too small, you can resize - the pane, enlarge the whole window, or double-click on the - message in the <interface>message list</interface> to have it - open in a new window. Just like with folders, you can - right-click on messages in the message list and get a menu of - possible actions. - </para> - - <!-- ==============Figure=================================== --> - - <figure id="usage-mail-intro-fig"> - <title>Evolution Mail</title> - <screenshot> - <screeninfo>Inbox</screeninfo> - <graphic fileref="fig/mail-pic" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure============================== --> - - <para> - Most of the mail-related actions you'll want to perform are - listed in the <guimenu>Message</guimenu> menu in the menu - bar. The most frequently used ones, like - <guimenuitem>Reply</guimenuitem> and - <guimenuitem>Forward</guimenuitem>, also appear as buttons in - the toolbar, and almost all of them are duplicated in the - right-click menu and as keyboard shortcuts, which tend to be - faster once you get the hang of them. You can choose - whichever way you like best; the idea is that the software - should work the way you want, rather than making you work the - way the it does. - <tip id="view-headers"> - <title>Take a look at the headers</title> - <para> - To look at the entire source of your email message, including - all the header information, select - <menuchoice><guimenu>View</guimenu><guimenuitem>Source</guimenuitem></menuchoice> - </para> - </tip> - </para> - - <sect3 id="usage-mail-listorder"> - <title>Sorting the message list</title> - <para> - One of the ways <application>Evolution</application> lets - you choose the way you work is the way it lets you sort your - message lists. To sort by sender, subject, or date, click - on the bars with those labels at the top of the message - list. The direction of the arrow next to the label indicates - the direction of the sort, and if you click again, you'll - sort them in reverse order. For example, click once on - <guilabel>Date</guilabel> to sort messages by date from - oldest to newest. Click again, and - <application>Evolution</application> sorts the list from - newest to oldest. You can also right-click on the message - header bars to get a set of sorting options, and add or - remove columns from the message list. You can find detailed - instructions on how to customize your message display - columns in <xref linkend="usage-mail-organize-columns">. - </para> - <para> - You can also choose a threaded message view. Select - <menuchoice> <guimenu>View</guimenu> - <guimenuitem>Threaded</guimenuitem> </menuchoice> to turn - the threaded view on or off. When you select this option, - <application>Evolution</application> groups the replies to a - message with the original, so you can follow the thread of a - conversation from one message to the next. - </para> - </sect3> - <sect3 id="usage-mail-getnsend-delete"> - <title>Deleting Mail</title> - <para> - Once you've read your mail, you may want to get rid of - it. To mark a message for deletion, select it in the the - <interface>message list</interface> by clicking on it once. - Then click on the <guibutton>Delete</guibutton> button in - the tool bar. Or, right-click on a message and choose - <guimenuitem>Delete</guimenuitem> from the right-click - menu. The message will appear with a line through it, to - show that you've marked it for deletion. - </para> - <para> - If you change your mind and decide you want to keep it, - select <menuchoice> <guimenu>Message</guimenu> - <guimenuitem>Undelete</guimenuitem></menuchoice>. If you - really want to get rid of it, choose - <guimenuitem>Expunge</guimenuitem> from the - <guimenu>Folder</guimenu> menu. That will delete it - permanently. - </para> - </sect3> - </sect2> - - <sect2 id="usage-mail-getnsend-get"> - <title>Checking Mail</title> - <para> - Now that you've had a look around the - <interface>Inbox</interface>, it's time to check for new mail. - Click <guibutton>Get mail</guibutton> in the toolbar to check - your mail. If it's the first time you've done so, the - <interface>mail setup assistant</interface> will ask you for - the information it needs to check your mail (see <xref - linkend="config-setupassist"> for more information). - </para> - <para> - Then, you need to enter your email - password. <application>Evolution</application> will remember - your password until until you select <menuchoice> - <guimenu>Settings</guimenu> <guimenuitem>Forget - Passwords</guimenuitem> </menuchoice>. - </para> - <para> - Once it's validated the password, - <application>Evolution</application> will check your mail. - New mail will appear in the local <interface>Inbox</interface> - if you're using a <glossterm>POP</glossterm> account, and in - your <glossterm>IMAP</glossterm> folders if you use IMAP. If - you have chosen to use IMAP, and you have multiple folders on - your IMAP server, you may need to subscribe to them. To learn - how to use the subscription manager, read <xref - linkend="usage-mail-subscriptions">. - </para> - - <note id="badmailsettings"> - <title>Can't Check Mail?</title> - <para> - If you get an error message instead of mail, you probably need - to change your network settings. To learn how to do that, - have a look at <xref linkend="config-prefs-mail-network">, or - ask your system administrator. - </para> - </note> - - <sect3 id="usage-mail-getnsend-get-news"> - <title>Using Evolution for News </title> - <para> - Newsgroups are so similar to email that there's no reason not - to read them side by side. If you want to do that, add a - news source to your configuration (see <xref - linkend="config-prefs-network-news">). The news server will - appear as a remote server, and will look quite similar to an - IMAP folder. When you click <guibutton>Get Mail</guibutton>, - <application>Evolution</application> will also check for news - messages. - </para> - </sect3> - - <sect3 id="usage-mail-getnsend-get-attach"> - <title>Attachments and HTML Mail</title> - <para> - If someone sends you an <glossterm>attachment</glossterm>, a - file attached to an email, - <application>Evolution</application> will display the file - at the bottom of the message to which it's attached. Text, - HTML, and most images will be displayed within the message - itself. For other files, - <application>Evolution</application> will show an icon at - the end of the message. Right-click on the icon to get a - list of options which will vary depending on the type of - attachment. You will have the option to display most files - as part of the message, export them to a different - application (images to Eye of GNOME, spreadsheets to - Gnumeric, and so forth), or save them to disk. - </para> - - <para> - <application>Evolution</application> can also display - HTML-formatted mail, complete with graphics. HTML - formatting will display automatically, although you can - turn it off if you prefer. - </para> - </sect3> - </sect2> - - <sect2 id="usage-mail-getnsend-send"> - <title>Writing and Sending Mail</title> - <para> - You can start writing a new email message by selecting - <menuchoice> <guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> <guimenuitem> - Mail Message</guimenuitem></menuchoice>, or by pressing the - <guibutton>Compose</guibutton> button in the Inbox toolbar. - When you do so, the <interface>New Message</interface> window - will open, as shown in <xref - linkend="usage-mail-newmsg-fig">. - </para> - -<!-- ==============Figure=================================== --> - <figure id="usage-mail-newmsg-fig"> - <title>New Message Window</title> - <screenshot> - <screeninfo>Evolution Main Window</screeninfo> - <graphic fileref="fig/newmsg-pic" format="png" srccredit="Kevin Breit"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> - - <!-- Check the alignment of the following paragraph in the PS and - HTML output: it's indented for no good reason --> - <para> - Enter an address in the <guilabel>To:</guilabel> field, a - subject in the <guilabel>Subject:</guilabel> and a message in - the big empty box at the bottom of the window, and press - <guibutton>Send</guibutton>. - </para> - - <sect3 id="usage-mail-getnsend-send-delay"> - <title>Saving Messages for Later</title> - <para> - Evolution will send mail immediately unless you tell it to - do otherwise by selecting <menuchoice> - <guimenu>File</guimenu> <guimenuitem>Send - Later</guimenuitem></menuchoice>. This will add your - messages to the <guilabel>Outbox</guilabel> queue. Then, - when you press <guibutton>Send</guibutton> in another - message, or <guibutton>Get Mail</guibutton> in the main - mail window, 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. - </para> - <para> - To learn more about how you can specify message queue and - filter behavior, see <xref linkend="config-prefs-mail">. - </para> - - <para> - You can also choose to save messages as drafts or as text - files. Choose - <menuchoice> - <guimenu>File</guimenu> - <guimenuitem>Save</guimenuitem> - </menuchoice> - or <guimenuitem>Save As</guimenuitem> to save your message - as a text file. If you prefer to keep your message in a - folder (the <guilabel>Drafts</guilabel> folder would be the - obvious place), you can select <menuchoice> - <guimenu>File</guimenu> <guimenuitem>Save In - Folder</guimenuitem> </menuchoice>. - </para> - </sect3> - <sect3 id="usage-mail-getnsend-send-compose"> - <title>Advanced Mail Composition</title> - <para> - You can probably guess the purpose of the buttons labelled - <guibutton>Cut</guibutton>, <guibutton>Copy</guibutton>, - <guibutton>Paste</guibutton>, <guibutton>Undo</guibutton> - and <guibutton>Redo</guibutton>, but there's a bit more to - sending mail that's less obvious. In the next few sections, - you'll see how <application>Evolution</application> handles - additional features, including large recipient lists, - attachments, and forwarding. - </para> - <sect4 id="usage-mail-getnsend-send-attach"> - <title>Attachments</title> - <para> - If you want to attach a file to your email message, you - can drag it from your desktop into the message window, or - click the button in the toolbar with a paper clip on it, - labelled <guibutton>Attach</guibutton>. If you click the - <guibutton>Attach</guibutton> button, - <application>Evolution</application> will open a file - selection dialog box to ask you which file you want to - send. Select the file and click <guilabel>OK</guilabel>. - </para> - <para> - To hide the display of files you've attached to the - message, select <menuchoice> - <guimenu>View</guimenu> <guimenuitem>Hide - Attachments</guimenuitem> </menuchoice>; to show them - again, choose <guimenuitem>Show Attachments</guimenuitem>. - </para> - <para> - When you send the message, a copy of the attached file - will go with it. Be aware that big attachments can take a - long time to download. - </para> - </sect4> - <sect4 id="usage-mail-getnsend-send-to-types"> - <title>Types of Recipients</title> - <para> - <application>Evolution</application>, like most email - programs recognizes three types of addressee: primary - recipients, secondary recipients, and hidden ("blind") - recipients. - </para> - <para> - The simplest way to direct a message is to put the email - address or addresses in the <guilabel>To:</guilabel> - field, which denotes primary recipients. To send mail to - more than one or two people, you can use the the - <guilabel>Cc:</guilabel> field. - </para> - <para> - 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. - <example id="ex-mail-cc"> - <title>Using the Cc: field</title> - <para> - When Susan sends an email to a client, she puts her - co-worker, Tim, in the in the - <guilabel>Cc:</guilabel> field, so that he know - what's going on. The client can see that Tim also - received the message, and knows that he can talk to - Tim about the message as well. - </para> - </example> - </para> - <para> - 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 - <guilabel>Bcc:</guilabel>. "Bcc" stands for "Blind Carbon - Copy", and it sends messages discreetly. In other words, - the people in the <guilabel>Bcc:</guilabel> field get the - message, but nobody sees that they got it. Note that the - contents of the <guilabel>To:</guilabel> and - <guilabel>Cc:</guilabel> fields are visible to all - recipients, even to people on the - <guilabel>Bcc:</guilabel> list. - - <example id="ex-mail-bcc"> - <title>Using the Bcc: field</title> - <para> - Tim is sending an email announcement to all of his - company's clients, some of whom are in competition - with each other, and all of whom value their - privacy. He needs to use the - <guilabel>Bcc:</guilabel> field here. If he puts - every address from his address book's "Clients" - category into the <guilabel>To:</guilabel> or - <guilabel>Cc:</guilabel> fields, he'll make the - company's <emphasis>entire</emphasis> client list - public. It seems like a small difference, but it can - make a huge difference in some situations. - </para> - </example> - </para> - </sect4> - - <sect4 id="usage-mail-getnsend-send-to"> - <title>Choosing Recipients Quickly</title> - <para> - If you have created address cards in the contact manager, - you can also enter nicknames or other portions of address - data, and <application>Evolution</application> 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. - <!-- (NOT YET) Also, <application>Evolution</application> - will add a domain to any unqualified addresses. By default, - this is your domain, but you can choose which one mail - preferences dialog. --> - </para> - <para> - Alternately, you can click on the - <guibutton>To:</guibutton>, <guibutton>Cc:</guibutton>, or - <guibutton>Bcc:</guibutton> buttons to get a list — - potentially a very long one — of the email addresses - in your contact manager. Select addresses and click on - the arrows to move them into the appropriate address - columns. - </para> - <para> - For more information about using email together with the - contact manager and the calendar, see <xref - linkend="usage-contact-automate"> and <xref - linkend="usage-calendar-apts">. - </para> - </sect4> - </sect3> - - <sect3 id="usage-mail-getnsend-send-reply"> - <title>Replying to Messages</title> - <para> - To reply to a message, press the - <guibutton>Reply</guibutton> button while it is selected, - or choose <guimenuitem>Reply to Sender</guimenuitem> from - the message's right-click menu. That will open the - <interface>message composer</interface>. The - <guilabel>To:</guilabel> and <guilabel>Subject</guilabel> - fields will already be filled, although you can alter them - if you wish. In addition, the full text of the old message - is inserted into the new message, either in italics (for - HTML display) or with the > character before each line - (in plain text mode), to indicate that it's part of the - previous message. People often intersperse their message - with the quoted material as shown in <xref - linkend="usage-mail-getnsend-reply-fig">. - -<!-- note that this figure should have a reply message ready to send, -with quoted materials and the relevant replies interspersed--> - <!-- ==============Figure=================================== --> - <figure id="usage-mail-getnsend-reply-fig"> - <title>Reply Message Window</title> - <screenshot> - <screeninfo>Evolution Main Window</screeninfo> - <graphic fileref="fig/replymsg" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> - </para> - - <para> - If you're reading a message with several recipients, you may - wish to use <guibutton>Reply to All</guibutton> instead of - <guibutton>Reply</guibutton>. If there are large numbers - of people in the <guilabel>Cc:</guilabel> or - <guilabel>To:</guilabel> fields, this can save substantial - amounts of time. - <example> - <title>Using the Reply to All feature</title> - <para> - Susan sends an email to a client and sends copies to Tim - and to an internal company mailing list of co-workers. - If Tim wants to make a comment for all of them to read, - he uses <guibutton>Reply to All</guibutton>, but if he - just wants to tell Susan that he agrees with her, he - uses <guibutton>Reply</guibutton>. Note that his reply - will not reach anyone that Susan put on her - <guilabel>Bcc</guilabel> list, since that list is not - shared with anyone. - </para> - </example> - </para> - </sect3> - <sect3 id="usage-mail-getnsend-send-find"> - <title>Searching and Replacing with the Composer</title> - <para> - You're probably familiar with search and replace features, - and if you come from a Linux or Unix background, you - probably know what <guimenuitem>Find Regex</guimenuitem> - does. If you aren't among the lucky who already know, - here's a quick rundown of an important section of the - <guimenu>Edit</guimenu> menu. - </para> - <para> - <variablelist> - <varlistentry> - <term><guimenuitem>Find</guimenuitem></term> - <listitem><para> Enter a word or phrase, and - <application>Evolution</application> will find it - in your message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Find Regex</guimenuitem></term> - <listitem> - <para> - Find a regex, also called a - <glossterm linkend="regular-expression">regular - expression</glossterm>, in your composer window. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Find Again</guimenuitem></term> - <listitem><para> - Select this item to repeat the last search you performed. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Replace</guimenuitem></term> - <listitem><para> - Find a word or phrase, and replace it with - something else. - </para></listitem> - </varlistentry> - - </variablelist> - </para> - <para> - For all of these menu items, you can choose whether or not - to <guilabel>Search Backwards</guilabel> in the document - from the point where your cursor is. For all but the - regular expression search (which doesn't need it), you are - offered a check box to determine whether the search is to - be <guilabel>Case Sensitive</guilabel> when it determines - a match. - </para> - </sect3> - <sect3 id="usage-mail-getnsend-send-html"> - <title>Embellish your email with HTML</title> - <para> - Normally, you can't set text styles or insert pictures in - emails, which is why you've probably seen people use far - too many exclamation points for emphasis, or use - <glossterm linkend="emoticon">emoticons</glossterm> to - convey their feelings. However, most newer email programs - can display images and text styles as well as basic - alignment and paragraph formatting. They do this with - <glossterm linkend="html">HTML</glossterm>, just like web - pages do. - </para> - <note> - <title>HTML Mail is not a Default Setting</title> - <para> - 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. <emphasis>Some</emphasis> - people refer to HTML mail as "the root of all evil" and - get very angry if you send them HTML mail, which is why - <application>Evolution</application> sends plain text - unless you explicitly ask for HTML. To send HTML mail, - you will need to select <menuchoice> - <guimenu>Format</guimenu> <guimenuitem> - HTML</guimenuitem></menuchoice>. Alternately, you can set - your default mail format preferences in the mail - configuration dialog. See <xref - linkend="config-prefs-mail-other"> for more information. - </para> - </note> - <para> - HTML formatting tools are located in the toolbar just above - the space where you'll actually compose the message, and - they also appear in the <guimenu>Insert</guimenu> and - <guimenu>Format</guimenu> menus. - </para> - <para> - The icons in the toolbar are explained in <glossterm - linkend="tooltip">tool-tips</glossterm>, which appear when - you hold your mouse over the buttons. The buttons fall - into four categories: - <variablelist> - <varlistentry> - <term>Headers and lists</term> - <listitem> - <para> - At the left edge of the toolbar, you can choose - <guilabel>Normal</guilabel> for a default text style - or <guilabel>Header 1</guilabel> through - <guilabel>Header 6</guilabel> for varying sizes of - header from large (1) to tiny (6). Other styles - include <guilabel>pre</guilabel>, to use the HTML - tag for preformatted blocks of text, and three types - of <guilabel>List Item</guilabel> for the highly - organized. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Text style</term> - <listitem> - <para> - Use these buttons to determine the way your letters - look. If you have text selected, the style will - apply to the selected text. If you do not have text - selected, the style will apply to whatever you type - next. The buttons are: - <itemizedlist mark="none"> - <listitem><para>Push <guibutton>B</guibutton> for bold text</para></listitem> - <listitem><para>Push <guibutton>I</guibutton> for italics</para></listitem> - <listitem><para>Push <guibutton>U</guibutton> to underline</para></listitem> - <listitem><para>Push <guibutton>S</guibutton> for a strikethrough.</para></listitem> - </itemizedlist> - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Alignment</term> - <listitem> - <para> - Located next to the text style buttons, these three - paragraph icons should be familiar to users of most - word processing software. The leftmost button will - make your text aligned to the left, the center - button, centered, and the right hand button, - aligned on the right side. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Indentation rules</term> - <listitem> - <para> - The button with the arrow pointing left will reduce - a paragraph's indentation, and the right arrow will - increase its indentation. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term>Color Selection</term> - <listitem> - <para> - At the far right is the color section tool. The - colored box displays the current text color; to - choose a new one, click the arrow button just to the - right. If you have text selected, the color will - apply to the selected text. If you do not have text - selected, the color will apply to whatever you type - next. - </para> - </listitem> - </varlistentry> - - - </variablelist> - </para> - <para> - There are three tools that you can find only in the - <guimenu>Insert</guimenu> menu. - <variablelist> - <varlistentry> - <term><guimenuitem>Insert Link</guimenuitem>:</term> - <listitem> - <para> - Use this tool to put hyperlinks in your HTML - messages. When you select it, - <application>Evolution</application> will prompt you - for the <guilabel>Text</guilabel> that will appear, - and the <guilabel>Link</guilabel>, where you should - enter the actual web address (URL). If you don't - want special link text, you can just enter the address - directly, and <application>Evolution</application> - will recognize it as a link. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term> <guimenuitem>Insert Image</guimenuitem>:</term> - <listitem> - <para> - Select this item to embed an image into your email, as - was done in the welcome message. Images will appear at - the location of the cursor. This is different from - attaching them to a message, but not very different. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guimenuitem>Insert Rule</guimenuitem>:</term> - <listitem><para> - This will insert a horizontal line, or rule, into your document. - You'll be presented with a dialog box which gives you - the choice of size, percentage of screen, shading, and - alignment; if you leave everything at the default - values you'll get a thin black rule all the way across - the screen.</para></listitem> - </varlistentry> - - </variablelist> - </para> - <note> - <title>A Technical note on HTML Tags</title> - <para> - The composer is a WYSIWYG (What You See Is What You Get) - editor for HTML. That means that if you enter HTML - directly into the composer— say, <markup - role="html"><B>Bold Text</B></markup>, the - the composer will assume you meant exactly that string - of characters, and not "make this text bold," as an HTML - composition tool or text editor would. - </para> - </note> - </sect3> - - -<!-- Function not implemented, -possibly never will be due to security evil. --> -<!-- - <sect3 id="usage-mail-getnsend-send-live"> - <title>Live Documents</title> - <para> - Later versions of <application>Evolution</application> - will allow you to enliven your email with almost any - sort of document, and even with entire - applications. At this point, however, this feature has not - yet been implemented. - </para> - </sect3> ---> - - <sect3 id="usage-mail-getnsend-fwd"> - <title>Forwarding Mail</title> - <para> - The post office forwards your mail for you when you change - addresses, and you can forward mail when you get a letter by - mistake. The email <guilabel>Forward</guilabel> button - works in much the same way. It's particularly useful if you - have received a message and you think someone else would - like to see it. You can forward a message as an attachment - to a new message (this is the default) or - you can send it <glossterm linkend="inline">inline</glossterm> as a quoted - portion of the message you are sending. Attachment - forwarding is best if you want to send the full, unaltered - message on to someone else. Inline forwarding is best if - you want to send portions of a message, or if you have a - large number of comments on different sections of the - message you are forwarding. Remember to note from whom the - message came, and where, if at all, you have removed or - altered content. - </para> - <para> - To forward a message you are reading, press - <guibutton>Forward</guibutton> on the toolbar, or select - <menuchoice> <guimenu>Message</guimenu> - <guimenuitem>Forward</guimenuitem> </menuchoice>. If you - prefer to forward the message <glossterm linkend="inline">inline</glossterm> - instead of attached, select <menuchoice> - <guimenu>Message</guimenu> <guimenuitem>Forward - Inline</guimenuitem> </menuchoice> from the menu. Choose an - addressee as you would when sending a new message; the - subject will already be entered, but you can alter it. - Enter your comments on the message in the - <interface>composition frame</interface>, and press - <guibutton>Send</guibutton>. - </para> - </sect3> - <sect3 id="usage-mail-getnsend-ettiquette"> - <title>Seven Tips for Email Courtesy</title> - <para> - I started with ten, but four were "Don't send - <glossterm linkend="spam">spam</glossterm>." - <itemizedlist> - - <listitem> - <para> - Don't send spam or forward chain mail. If you must, - watch out for hoaxes and urban legends, and make sure - the message doesn't have multiple layers of - greater-than signs, (>) indicating multiple layers - of careless in-line forwarding. - </para> - </listitem> - - <listitem> - <para> - 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! - </para> - </listitem> - - <listitem> - <para> - ALL CAPS MEANS YOU'RE SHOUTING! Don't write a whole - message in capital letters. It hurts people's ears. - </para> - </listitem> - - <listitem> - <para> - Never write anything in email you wouldn't say in - public. Old messages have a nasty habit of - resurfacing when you least expect. - </para> - </listitem> - - <listitem> - <para> - Check your spelling and use complete sentences. - </para> - </listitem> - - <listitem> - <para> - Don't send nasty emails (flames). If you get one, - don't write back. - </para> - </listitem> - - <listitem> - <para> - When you reply or forward, include just enough of - the previous message to provide context: not too - much, not too little. - </para> - </listitem> - </itemizedlist> - </para> - <para> Happy mailing! </para> - </sect3> - </sect2> - </sect1> - - <sect1 id="usage-mail-organize"> - <title>Organizing Your Mail</title> - <para> - 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 <emphasis>need</emphasis> to sort and organize them. - Fortunately, <application>Evolution</application> has the tools - to help you do it. - </para> - <sect2 id="usage-mail-organize-columns"> - <title>Sorting Mail with Column Headers</title> - <para> - By default, the message list has columns with the following - headings: an envelope icon indicating whether you have read - or replied to a message (closed for unread, open for read, - and open with an arrow on it to indicate you've sent a - reply), an exclamation point indicating priority, and the - <guilabel>From</guilabel>, <guilabel>Subject</guilabel>, and - <guilabel>Date</guilabel> fields. You can change their order - and remove them by dragging and dropping them. You can add - new ones with the <guimenuitem>Field Chooser</guimenuitem> - item in the right click menu for the column headings. - </para> - <para> - Right-click on one of the column headers to get a list of - options: - <variablelist> - - <varlistentry> - <term><guimenuitem>Sort Ascending</guimenuitem>, - <guimenuitem>Sort Descending</guimenuitem>, and - <guimenuitem>Unsort</guimenuitem></term> - <listitem><para>Which should be pretty obvious. You - can also set these sorts by just clicking on the - column headers.</para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Group By this Field</guimenuitem></term> - <listitem><para> - Groups messages instead of sorting them. (FIXME: Explain further) - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Remove this - Column</guimenuitem></term> <listitem><para> Remove - this column from the display. You can also remove - columns by dragging the header off the list and - letting it drop. </para></listitem> - </varlistentry> - - <varlistentry> - <term><guimenuitem>Field - Chooser</guimenuitem></term> <listitem><para> A list - of column headers; just drag and drop them into - place between two existing headers. A red arrow will - appear to show you where you're about to put the - column. </para></listitem> - </varlistentry> - </variablelist> - </para> - </sect2> - - <sect2 id="usage-mail-organize-folders"> - <title>Getting Organized with Folders</title> - <para> - <application>Evolution</application> keeps mail, as well as - address cards and calendars, in folders. You start out with a - few, like <guilabel>Inbox</guilabel>, - <guilabel>Outbox</guilabel>, and <guilabel>Drafts</guilabel>, - but you can create as many as you like. Create new folders by - selecting <guisubmenu>New</guisubmenu> and then - <guimenuitem>Folder</guimenuitem> from the - <guimenu>File</guimenu> menu. - <application>Evolution</application> will as you for the name - and the type of the folder, and will provide you with a folder - tree so you can pick where it goes. - </para> - <para> - When you click <guibutton>OK</guibutton>, your new folder will - appear in the <interface>folder view</interface>. You can - then put messages in it by dragging and dropping them, or by - using the <guibutton>Move</guibutton> button in the - toolbar. If you want to move several messages at once, click - on the ones you want to move while holding down the - <keycap>CTRL</keycap> key, or use <keycap>Shift</keycap> to - select a range of messages. If you create a filter with the - <interface>filter assistant</interface>, you can have mail - moved to your folder automatically. - </para> - </sect2> - - <sect2 id="usage-mail-organize-search"> - <title>Searching for Messages</title> - <para> - Most mail clients can search through your messages for you, - but <application>Evolution</application> does it faster. You - can search through just the message subjects, just the message - body, or both body and subject. - </para> - <para> - To start searching, enter a word or phrase in the text area - right below the toolbar, and choose a search type: - <variablelist> - <varlistentry> - <term><guilabel>Body or subject contains:</guilabel></term> - <listitem> - <para> - This will search message subjects and the messages - themselves for the word or phrase you've entered in - the search field. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term> <guilabel>Body contains:</guilabel> </term> - <listitem> - <para> - This will search only in message text, not the subject - lines. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Subject contains:</guilabel></term> - <listitem> - <para> - This will show you messages where the search text is - in the subject line. It will not search in the - message body. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Body does not contain:</guilabel></term> - <listitem> - <para> - This finds every email message that does not have the - search text in the message body. It will still show - messages that have the search text in the subject - line, if it is not also in the body. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><guilabel>Subject does not contain:</guilabel></term> - <listitem> - <para> - This finds every mail whose subject does not contain - the search text. - </para> - </listitem> - </varlistentry> - </variablelist> - - When you've entered your search phrase, press - <keycap>Enter</keycap>. <application>Evolution</application> - will show your search results in the message list. - </para> - - <para> - If you think you'll want to return to a search again, you can - save it as a virtual folder by selecting <guilabel>Store - Search as Virtual Folder</guilabel>. - </para> - - <para> - When you're done with the search, go back to seeing all your - messages by choosing <guimenuitem>Show All</guimenuitem> from - the <guilabel>Search</guilabel> drop-down box. If you're - sneaky, just enter a blank search: since every message has at - least one space in it, you'll see every message in the - folder. - </para> - - <para> - If you'd like to perform a more complex search, open the - advanced search dialog by selecting - <guilabel>Advanced...</guilabel> from the - <guilabel>Search</guilabel> drop-down menu. Then, create your - search criteria (each with the same options you saw in the - regular search bar), and decide whether you want to find - messages that match all of them, or messages that match even - one. Then, click <guibutton>Search</guibutton> to go and find - those messages. - </para> - - <para> - You'll see a similar approach to sorting messages when you - create filters and virtual folders in the next few sections. - </para> - - </sect2> - - <sect2 id="usage-mail-organize-filters"> - <title>Staying organized: Mail Filters in Evolution</title> - <para> - I once worked in the mail room of a large company, where my - job was to bundle, sort, and distribute mail to the various - mail boxes and desks throughout the building. Filters do that - same job with email, but they lose much less mail than I did. - In addition, you can have multiple filters performing multiple - actions that may effect the same message in several ways. For - example, your filters could put copies of one message into - multiple folders, or keep a copy and send one to another - person as well, and it can do that in under a second. Which is - to say, it's faster and more flexible than an actual person - with a pile of envelopes. - </para> - <para> - Most often, you'll want to have - <application>Evolution</application> put mail into different - folders, but you can have it do almost anything you like. - People who get lots of mail, or who often need to refer to old - messages, find filters especially helpful, but they're good - for anybody who gets more than a few messages a day. To - create a filter, open the <interface>filter - assistant</interface> by selecting - <menuchoice> - <guimenu>Settings</guimenu> - <guimenuitem>Mail Filters</guimenuitem> - </menuchoice>. - </para> - - <figure id="usage-mail-filters-fig-assist"> - <title>The Filter Assistant</title> - <screenshot> - <screeninfo>The Filter Assistant</screeninfo> - <graphic fileref="fig/filter-assist-fig" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - - <para> - The <interface>filter assistant</interface> window contains a - list of your current filters, sorted by the order in which - they are used. From the drop-down box at the top of the - window, choose <guilabel>Incoming</guilabel> to display - filters for incoming mail, and <guilabel>Outgoing</guilabel> - for those which sort only outgoing mail. - </para> - <para> - The <interface>filter assistant</interface> also has a set of - buttons: - <itemizedlist> - - <listitem><para> - <guibutton>Add</guibutton> — Create a new filter. - </para></listitem> - - <listitem><para> - <guibutton>Edit</guibutton> — Edit an existing filter. - </para></listitem> - - <listitem><para> - <guibutton>Delete</guibutton> — Delete the selected filter. - </para></listitem> - - <listitem><para> <guibutton>Up</guibutton> — Move the - selected filter up in the list so it gets applied first. - </para></listitem> - - <listitem><para> - <guibutton>Down</guibutton> — Move the selected filter down - in the list, so it comes into play later. - </para></listitem> - </itemizedlist> - - If you don't have any filters set up, the only one of those - buttons you can click is <guibutton>Add</guibutton>, which - will open a dialog to let you add a filter rule. If you do - have filters, you can either add a new filter rule, or select - one from your list and click <guibutton>Edit</guibutton>. - </para> - <para> - The filter rule editor, shown in <xref - linkend="usage-mail-filters-fig-new">, is where you'll - actually create your filtering rule. - - <figure id="usage-mail-filters-fig-new"> - <title>Creating a new Filter</title> - <screenshot> - <screeninfo>Creating a new Filter</screeninfo> - <graphic fileref="fig/filter-new-fig" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - </para> - <para> - Enter a name for your filter in the <guilabel>Rule - Name</guilabel> field, and then begin choosing the criteria - you'd like to use as you sort your mail. Choose how many - criteria you'd like by pressing <guibutton>Add - Criterion</guibutton> and <guibutton>Remove - Criterion</guibutton>. If you have multiple criteria, you - should then decide whether to have the filter do its job only - <guilabel>if all criteria are met</guilabel>, or <guilabel>if - any criteria are met</guilabel>. - </para> - <para> - For each filter criterion, you must first select what - part of the message you want the filter to examine: - <variablelist> - <varlistentry> - <term><guilabel>Sender</guilabel></term> - <listitem><para> - The sender's address. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Recipients</guilabel></term> - <listitem><para> - The recipients of the message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Subject</guilabel></term> - <listitem><para> - The subject line of the message. - </para></listitem> - </varlistentry> - - - <varlistentry> - <term><guilabel>Specific Header</guilabel></term> - <listitem><para> - The filter can look at any header you - want, even obscure or custom ones. Enter the header name - in the first text box, and put your search text in the - second one. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Message Body</guilabel></term> - <listitem><para> - Search in the actual text of the message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Expression</guilabel></term> - <listitem> - <para> - Enter a <glossterm linkend="regular-expression">regular - expression</glossterm>, and - <application>Evolution</application> will search the - entire message, including headers, to match it for you. - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term><guilabel>Date Sent</guilabel></term> - <listitem><para> Filter messages by when they were sent: - First, choose the conditions you want a message to - meet— <guilabel>before</guilabel> a given time, - <guilabel>after</guilabel> it, and so forth. Then, choose - the time. The filter will compare the message's time-stamp - to the system clock when the filter is run, or to a - specific time and date you choose from a calendar. You - can even have it look for messages within a range of time - relative to the filter&mdash perhaps you're looking for - messages less than two days old. </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Date Recieved</guilabel></term> - <listitem><para> - This works the same way as the <guilabel>Date Sent</guilabel> - option, except that it compares the time you got the message - with the dates you specify. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Priority</guilabel></term> - <listitem><para> - Emails have a standard priority range from -3 (least - important) to 3 (most important). You can have filters set the - priority of messages you recieve, and then have other filters - applied only to those messages which have a certain priority. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Regex Match</guilabel></term> - <listitem> - <para> - If you know your way around a <glossterm - linkend="regular-expression">regex</glossterm>, or - regular expression, put your knowledge to use here. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Source</guilabel></term> - <listitem> - <para> - Filter messages according the server you got them from. - You can enter a URL or choose one from the drop-down - list. This ability is only relevant if you use more - than one mail source. - </para> - </listitem> - </varlistentry> - </variablelist> - </para> - <para> - Now, tell it what to do with those messages. If you want more - actions, click <guibutton>Add Action</guibutton>; if you want - fewer, click <guibutton>Remove Action</guibutton>. And choose - again: - <variablelist> - - <varlistentry> - <term><guilabel>Copy to Folder</guilabel></term> - <listitem><para> - If you select this item, <application>Evolution</application> - will put the messages into a folder you specify. Click the - <guibutton><click here to select a folder></guibutton> button - to select a folder. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Move to Folder</guilabel></term> - <listitem><para> - If you select this item, <application>Evolution</application> - will put the messages into a folder you specify. Click the - <guibutton><click here to select a folder></guibutton> button - to select a folder. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Forward to Address</guilabel></term> - <listitem><para> - Select this, enter an address, and the addressee will - get a copy of the message. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Delete</guilabel></term> - <listitem><para> - Marks the message for deletion. You can still get the message - back, at least until you <guimenuitem>Expunge</guimenuitem> your - mail yourself. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Stop Processing</guilabel></term> - <listitem><para> - Select this if you want to tell all other filters to ignore - this message, because whatever you've done with it so far - is plenty. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Assign Color</guilabel></term> - <listitem><para> - Select this item, and <application>Evolution</application> - will mark the message with whatever color you please. - </para></listitem> - </varlistentry> - - <varlistentry> - <term><guilabel>Assign Score</guilabel></term> - <listitem><para> If you know that all mail with - "important" somewhere in the message body line is - important, you can give it a high priority score. In a subsequent filter you can - then arrange your messages by their priority score. - </para></listitem> - </varlistentry> - - </variablelist> - </para> - <para> - You're done. Click <guibutton>OK</guibutton> to use this - filter, or <guibutton>Cancel</guibutton> to close the window - without saving any changes. - </para> - - - - <!-- FIXME: This needs to be in there. But the feature is temporarily - disabled and I don't know how it will be reimplemented. - - <itemizedlist> - <listitem> - <para> - <guilabel>When mail arrives:</guilabel> Select - this option to have messages filtered as they - arrive. - </para> - </listitem> - <listitem> - <para> - <guilabel>When mail is sent:</guilabel> Select - this option to filter your outgoing mail. You - can use this feature to keep your - <interface>Outbox</interface> as organized as - your <interface>Inbox</interface>. - </para> - </listitem> - </itemizedlist> - </para> - - --> - - <note> - <title>Two Notable Filter Features</title> - <para> - <itemizedlist> - <listitem><para> - Incoming email that your filters don't move goes into the Inbox; - outgoing mail that they don't move ends up in the Sent folder. - </para> - </listitem> - - <listitem><para>If you move a folder, your filters - will follow it. </para></listitem> - </itemizedlist> - </para> - </note> - </sect2> - - - - <sect2 id="usage-mail-organize-vFolders"> - <title>Getting Really Organized with Virtual Folders</title> - <para> - If filters aren't flexible enough for you, or you find - yourself performing the same search again and again, consider - a virtual folder. Virtual folders, or vFolders, are an - advanced way of viewing your email messages within - <application>Evolution</application>. If you get a lot of - mail or often forget where you put messages, virtual folders can help - you stay on top of things. - </para> - <para> - A virtual folder is really a hybrid of all the other organizational - tools: it looks like a folder, it acts like a search, and you - set it up like a filter. In other words, while a conventional - folder actually contains messages, a virtual folder is a view of - messages that may be in several different folders. The - messages it contains are determined on the fly using a set of - criteria you choose in advance. - </para> - - <para> - As messages that meet the virtual folder criteria arrive or are - deleted, <application>Evolution</application> will - automatically place them in and remove them from the - virtual folder contents list. When you delete a message, it gets - erased from the folder in which it actually exists, as well as - any virtual folders which display it. - </para> - - <para> - Imagine a business trying to keep track of mail from hundreds - of vendors and clients, or a university with overlapping and - changing groups of faculty, staff, administrators and - students. The more mail you need to organize, the less you - can afford the sort of confusion that stems from an - organizational system that's not flexible enough. Virtual folders - make for better organization because they can accept - overlapping groups in a way that regular folders and filing - systems can't. - </para> - - <example id="usage-mail-organize-vFolders-ex"> - <title>Using Folders, Searches, and Virtual Folders</title> - <para> - To organize my mail box, I set up a virtual folder for - emails from my friend and co-worker Anna. I have another - one for messages that have "ximian.com" in the address and - "Evolution" in the subject line, so I can keep a record of - what people from work send me about - <application>Evolution</application>. If Anna sends me a - message about anything other than Evolution, it only shows - up in the "Anna" folder. When Anna sends me mail about the - user interface for <application>Evolution</application>, I - can see that message both in the "Anna" virtual folder and - in the "Internal Evolution Discussion" virtual folder. - </para> - </example> - - <!-- (INSERT SCREENSHOT HERE: virtual folders in action) --> - - <para> - To create a virtual folder, select <menuchoice> - <guimenu>Settings</guimenu> <guimenuitem>Virtual Folder - Editor</guimenuitem> </menuchoice>. This will bring up a - dialog box that looks suspiciously like the filter window - (for more information on filters, see <xref - linkend="usage-mail-organize-filters">), and which - presents you with a list of virtual folders you have previously - created. If you have created any virtual folders, they are listed - here, and you can select, edit or remove them if you wish. - If you have not created any, there will be only one available - option: click <guibutton>Add</guibutton> to add a new - Virtual Folder. - </para> - <para> - You can enter a name for your virtual folder in the - <guilabel>Name</guilabel>. Then, tell - <application>Evolution</application> what messages to look - for. This process is exactly like filter creation: decide - between <guilabel>Match all parts</guilabel> and - <guilabel>Match any part</guilabel>, then choose what part of - the message to look in, what sort of matching to perform, and - specify exactly what it is that you want to find, be it a - line of text, a score, a regular expression, or a particular date or - range of dates. - </para> - <para> - The second part, however, is slightly different. In the - section of the window labelled <guilabel>Virtual Folder Sources - </guilabel> is a list of folders in which - <application>Evolution</application> will search for the - contents of your vFolder. Click <guibutton>Add</guibutton> - to add a folder, or <guibutton>Remove</guibutton> to remove - one. That way, you can have your vFolder search in - newsgroups, or just in one of your mailboxes, or just in a - select few folders you've already screened with filters. - </para> - <para> - The vFolder creation window is shown in <xref - linkend="usage-mail-vfolder-fig-createrule"> - - <figure id="usage-mail-vfolder-fig-createrule"> - <title>Selecting a vFolder Rule</title> - <screenshot> - <screeninfo>Creating a vFolder Rule</screeninfo> - <graphic fileref="fig/vfolder-createrule-fig" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> - </para> - </sect2> - <sect2 id="usage-mail-subscriptions"> - <title>Subscription Management</title> - <para> - <application>Evolution</application> lets you handle your - IMAP and newsgroup subscriptions with the same tool: the - subscriptions manager. To start using it, choose - <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Manage - Subscriptions</guimenuitem> </menuchoice>. - </para> - <para> - If you have configured any IMAP (mail) or NNTP (news) - servers, you will see them listed in the left half of the - subscription management window. Click on a server to select - it, and you will see the folders or newsgroups available to - you. You can then select individual folders and subscribe to - them, or remove yourself from the subscription list. - </para> - <para> - Once you have subscribed to a folder or newsgroup, your system - will check for new messages whenever you press the - <guibutton>Get Mail</guibutton> button. - </para> - - </sect2> - </sect1> -</chapter> - - diff --git a/help/C/usage-mainwindow.sgml b/help/C/usage-mainwindow.sgml deleted file mode 100644 index bbcb2b5a39..0000000000 --- a/help/C/usage-mainwindow.sgml +++ /dev/null @@ -1,453 +0,0 @@ -<!-- - <!DOCTYPE Chapter PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> -<chapter id="usage-mainwindow"> - - <title>The Main Window: Evolution Basics</title> - <para> - Start <application>Evolution</application> by selecting - <menuchoice><guimenu>Main Panel Menu</guimenu> - <guisubmenu>Applications</guisubmenu> - <guimenuitem>Evolution</guimenuitem></menuchoice> or by typing - <command>evolution</command> at the command line. The first time - you run the program, it will create a directory called - <filename>evolution</filename> in your home directory, where it - will keep all your <application>Evolution</application>-related - files. - </para> - <para> - After <application>Evolution</application> starts - up, you will see the <interface>main window</interface>, with the - <interface>Inbox</interface> open. It should look a lot like the - picture in <xref linkend="usage-mainwindow-fig">. On the left of - the <interface>main window</interface> is the <interface>shortcut - bar</interface>, with several buttons in it. Just underneath the - title bar is a series of menus in the <interface>menu - bar</interface>, and below that, the <interface>tool - bar</interface> with buttons for different functions. The largest - part of the <interface>main window</interface> is taken up by the - actual <interface>Inbox</interface>, where messages are listed - and displayed. If you're running the program for the first time, - you'll have just one message: a welcome from Ximian. - - -<!-- ==============Figure=================================== --> - <figure id="usage-mainwindow-fig"> - <title>Evolution Main Window and Inbox</title> - <screenshot> - <screeninfo>Evolution Main Window</screeninfo> - <graphic fileref="fig/mainwindow-pic" format="png" srccredit="Kevin Breit"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure=================================== --> -</para> - - <para> - <note> - <title>The Way Evolution Looks</title> - <para> - The appearance of both <application>Evolution</application> - and <application>GNOME</application> is very easy to - customize, so your screen might not look like this picture. - You might decide to have <application>Evolution</application> - start with the calendar and a folder bar, or with the contact - manager occupying the entire window. - </para> - </note> - </para> - - <sect1 id="usage-mainwindow-shortcutbar"> - <title>The Shortcut Bar</title> - <para> - <application>Evolution</application>'s most important job is - to give you access to your information and help you use it - quickly. One way it does that is through the - <interface>shortcut bar</interface>, the column on the left - hand side of the main window. The large buttons with names - like <guilabel>Inbox</guilabel> and - <guilabel>Contacts</guilabel> are the shortcuts, and you can - select different groups of shortcuts by clicking the - rectangular group buttons. - </para> - <para> - The shortcut group buttons are <guibutton>Evolution - Shortcuts</guibutton> and <guibutton>Internet - Directories</guibutton>. When you click on them, they'll slide - up and down to give you access to different sorts of shortcuts. - When you first start <application>Evolution</application>, you - are looking at the <guilabel>Evolution Shortcuts</guilabel> - category. If you click <guilabel>Internet - Directories</guilabel>, it will slide up and you'll see buttons - for the <guilabel>Bigfoot</guilabel> and - <guilabel>Netcenter</guilabel> directories, as well as any - others you or your system administrator may have added. You can - add more groups by right-clicking on the background of the - shortcut bar and selecting <guimenuitem>Menu - Group</guimenuitem>. Internet directories behave a lot like - the local contact manager, which is covered in <xref - linkend="usage-contact">. - </para> - <para> - Take a look at the <guilabel>Evolution Shortcuts</guilabel> - again. The shortcut buttons in that category are: - - <variablelist> - -<!-- NOT IMPLEMENTED! - <varlistentry> - <term> <guibutton>Today:</guibutton></term> - <listitem> - <para> - This will bring up a summary of any new messages you've - received, along with the tasks and appointments you have - lined up for today. - </para> - </listitem> - </varlistentry> ---> - - - <varlistentry> - <term> <guibutton>Executive Summary:</guibutton></term> - <listitem> - <para> - Start your day here. The Executive summary gives you - lists of new or important messages, daily appointments - and urgent tasks. You can customize its appearance and - content, and use it to access Evolution services. - </para> - </listitem> - </varlistentry> - - - <varlistentry> - <term> <guibutton>Inbox:</guibutton></term> - <listitem> - <para> - Click the <guibutton>Inbox</guibutton> button to start - reading your mail. Your Inbox is also where you can - access Evolution's tools to filter, sort, organize, and - search your mail. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guibutton>Calendar:</guibutton></term> - <listitem> - <para> - The Calendar can store your appointments and To do lists - for you. Connected to a network, you can use it to keep - a group of people on schedule and up to date. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guibutton>Tasks:</guibutton></term> - <listitem> - <para> - A full-size view of your calendar's task pad. - </para> - </listitem> - </varlistentry> - - <varlistentry> - <term><guibutton>Contacts:</guibutton></term> - <listitem> - <para> - The Contact Manager holds your addresses, phone numbers, - and contact information. Like calendar information, - contact data can be synchronized with hand-held devices - and shared over a network. - </para> - </listitem> - </varlistentry> - -<!-- NOT IMPLEMENTED YET - - - <varlistentry> - <term> <guibutton>Notes:</guibutton></term> - <listitem> - <para> The note pad is your catch-all tool: use it to take - messages from phone conversations, keep small things - organized, write <glossterm linkend="haiku">haiku</glossterm>, or whatever - you like. This feature is not yet implemented, but will be - soon. See <xref linkend="usage-notes"> for more - information. - </para> - </listitem> - </varlistentry> ---> - - </variablelist> - </para> - <para> - If you don't like the shortcut bar, you can use the folder bar - or the menu bar to navigate the main window. Press - <keycombo action="simul"> - <keycap>Ctrl</keycap> - <keycap>O</keycap> - </keycombo> - to choose from a list of folders you'd like to visit, or use the - drop-down folder bar. You can hide and show the folder bar and - the shortcut bar by selecting those items in the - <guimenu>View</guimenu> menu. - </para> - - <tip> - <title>Shortcut Bar Tricks</title> - <para> - To remove a shortcut from the shortcut bar, right-click on it - and select <guimenuitem>Remove</guimenuitem>. To add one, - select <menuchoice> <guimenu>File</guimenu> - <guisubmenu>New</guisubmenu> <guimenuitem>Evolution Bar - Shortcut</guimenuitem> </menuchoice>. - </para> - <para> - To change the way the shortcut bar looks, right-click in an - empty space on the shortcut bar. From the menu that appears, - you can select icon sizes. - </para> - </tip> - </sect1> - - <sect1 id="usage-mainwindow-folderbar"> - <title>The Folder Bar</title> - <para> - The <interface>folder bar</interface> is a more comprehensive - way to view the information you've stored with - <application>Evolution</application>. It displays all your - appointments, address cards, and email in a tree that's a lot - like a <glossterm linkend="filetree">file - tree</glossterm>— it starts small at the top, and branches - downwards. On most computers, there will be three or four - folders at the base. First is the <guilabel>Local</guilabel> - folder, which holds all the <application>Evolution</application> - data that's stored on your computer. After that come - <guilabel>Virtual Folders</guilabel>, or virtual folders, discussed in - <xref linkend="usage-mail-organize-vfolders">, followed by any - <glossterm linkend="imap">IMAP</glossterm> mail folders you may - have available to you over your network. Lastly, there are - <guilabel>External Directories</guilabel>, <glossterm - linkend="ldap">LDAP</glossterm> contact directories stored on a - network. - </para> - <para> - - A typical <guilabel>Local</guilabel> folder contains the following folders: - <itemizedlist> - <listitem> - <para> - <guilabel>Calendar</guilabel>, for appointments and - event listings. - </para> - </listitem> - <listitem> - <para> - <guilabel>Contacts</guilabel>, for address cards. - </para> - </listitem> - <listitem> - <para> - <guilabel>Inbox</guilabel>, for incoming mail. - </para> - </listitem> - <listitem> - <para> - <guilabel>Drafts</guilabel>, for messages you started and didn't finish. - </para> - </listitem> - <listitem> - <para> - <guilabel>Sent</guilabel>, for sent mail. - </para> - </listitem> - <listitem> - <para> - <guilabel>Trash</guilabel>, which is used to store - messages you don't want, but keep around just in case you - change your mind. - </para> - </listitem> - <listitem> - <para> - <guilabel>Outbox</guilabel>, for messages you have written - but not yet sent. This will be empty unless you use - <application>Evolution</application> while offline. - </para> - </listitem> - - </itemizedlist> - - </para> - <tip id="foldertips"> - <title>Navigating without the Folder Bar</title> - <para> - You don't need the folder bar or the shortcut bar to move - around the main window. You can use <keycap>Tab</keycap> to - switch from one part of the window to another, and the folder - menu on the right side of the window just below the toolbar - to move about the folder tree. - </para> - </tip> - - <para> - To create a new folder, select <menuchoice> - <guimenu>File</guimenu> <guisubmenu>New</guisubmenu> - <guimenuitem>Folder</guimenuitem></menuchoice>. You'll be asked where you want to - put it, and what kind of folder it should be. You can choose - from three types: <guilabel>Mail</guilabel>, for storing mail, - <guilabel>Calendar</guilabel> for storing calendars, and - <guilabel>Contacts</guilabel> for storing contacts. - </para> - - <note> - <title>Folders Have Limits</title> - <para> - Calendars must go in calendar folders, mail in mail - folders, and contacts in contact folders. - </para> - </note> - - <para> - Right-clicking will bring up a menu for just about anything - in GNOME, and <application>Evolution</application> is no - exception. If you right-click on a folder, you'll have a - menu with the following options: - <itemizedlist> - <listitem><para><guimenuitem>FIXME</guimenuitem>, for another purpose. </para></listitem> - <listitem><para><guimenuitem>Something else</guimenuitem>, for another purpose. </para></listitem> - </itemizedlist>. - </para> - - <tip> - <title>Context-Sensitive Help</title> - <para> - GNOME 2.0 will support context-sensitive help, which means you - can almost always get help on an item by right-clicking it. - If you're not sure what something is, or don't know what you - can do with it, choosing <guimenuitem>Help</guimenuitem> from - the right-click menu is a good way to find out. - </para> - </tip> - - <para> - Any time new information arrives in a folder, that folder label - is displayed in bold text. - </para> - <para> - To delete a folder, right-click it and select - <guimenuitem>Delete</guimenuitem> from the menu that pops up. - To change the order of folders, or put one inside another, use - drag-and-drop. To move individual - messages, appointments, and address cards between folders, you - can do the same thing: drag them where you want them, and - they'll go. - </para> - </sect1> - <sect1 id="usage-mainwindow-menubar"> - <title>The Menu Bar</title> - <para> - The <interface>menu bar</interface>'s contents will always - provide all the possible actions for any given view of your - data. That means that, depending on the context, menu bar items - will change. If you're looking at your Inbox, most of the menu - items will relate to mail; some will relate to other components - of <application>Evolution</application> and some, especially - those in the <guimenu>File Menu</guimenu> will relate to the - application as a whole. The contents of the menu bar are - described in <xref linkend="menuref">. - </para> - <para> - <variablelist> - <varlistentry> - <term> <guimenu>File</guimenu> Menu</term> - - <listitem><para> - Anything even related to a file or to the operations - of the application generally falls under this - menu: creating things, saving them to disk, - printing them, and quitting the program itself. - - </para></listitem> - </varlistentry> - - <varlistentry> - <term> <guimenu>Edit</guimenu> Menu </term> - <listitem><para> - The <guimenu>Edit</guimenu> menu holds - useful tools that help you edit text and move it around. - </para></listitem> - </varlistentry> - - <varlistentry> - <term> <guimenu>View</guimenu> Menu </term> - <listitem><para> - This menu lets you decide how <application>Evolution</application> - should look. Some of the features control the appearance of - <application>Evolution</application> as a whole, and others - the way a particular kind of information appears. - </para></listitem> - </varlistentry> - - <varlistentry> - <term> <guimenu>Settings</guimenu> Menu </term> - <listitem><para> Tools for configuring, changing, and - setting up go here. For mail, that means things like - <guimenuitem>Mail Configuration</guimenuitem> and the - <guimenuitem>Virtual Folder Editor</guimenuitem>. For the - <interface>Calendar</interface> and the <interface>Contact - Manager</interface>, it's color, network, and layout - configuration. </para></listitem> - </varlistentry> - - <varlistentry> - <term> <guimenu>Help</guimenu> Menu</term> - <listitem><para> - Select among these items to open the - <application>Help Browser</application> - and read the <application>Evolution</application> manual. - </para></listitem> - </varlistentry> - </variablelist> - </para> - <para> - Other menus, like <guilabel>Folder</guilabel>, - <guilabel>Message</guilabel>, and <guilabel>Actions</guilabel>, - appear only occasionally. <guilabel>Message</guilabel> and - <guilabel>Folder</guilabel>, for example, have commands that only - relate to email, so they're only available when you're looking at - email. - </para> - <para> - Once you've familiarized yourself with the <interface>main - window</interface> you can start doing things with it. We'll - start with your email inbox, since you've got a letter waiting - for you already. - </para> - </sect1> -</chapter> - - - - - - - - - - - - - - - - - - - - - diff --git a/help/C/usage-notes.sgml b/help/C/usage-notes.sgml deleted file mode 100644 index 1ff2283128..0000000000 --- a/help/C/usage-notes.sgml +++ /dev/null @@ -1,49 +0,0 @@ -<chapter id="usage-notes"> - <title>Evolution Notes</title> - <abstract> - <title> An Overview of the Evolution Notes</title> - <para> - In the dark ages before email was invented, there were little - scraps of people which people used for short-term information - storage. These scraps of paper were called notes. Now, notes - are an almost necessary part of our lives, albeit in electronic - form. It only makes sense, then, that - <application>Evolution</application> will eventually have a - Notes feature. <application>Evolution</application> can help - you take notes in the following ways: - <itemizedlist> - <listitem> - <para> - Take down phone numbers, take school notes, take phone - messages, or even write poetry. - </para> - </listitem> - <listitem> - <para> - Color code notes to organize them, or just to - make them look good. - </para> - </listitem> - <listitem> - <para> - Turn a note into an email or a text file. - </para> - </listitem> - <listitem> - <para> - Write <glossterm>Haiku</glossterm> - </para> - </listitem> - </itemizedlist> - </para> - <para> - You can start writing notes by clicking - <guibutton>Notes</guibutton> in the shortcut bar. Of course, - it's not there yet. But when it is, it'll take you to the - notepad. - </para> - </abstract> -</chapter> - - - diff --git a/help/C/usage-print.sgml b/help/C/usage-print.sgml deleted file mode 100644 index cc1ac16357..0000000000 --- a/help/C/usage-print.sgml +++ /dev/null @@ -1,105 +0,0 @@ -<chapter id="usage-print"> -<title>Printing with Evolution</title> -<para> - This is a very short chapter, because printing with - <application>Evolution</application> is not a complex task. Like - most GNOME applications, <application>Evolution</application> uses - the gnome-print system, so if you've used any other GNOME - application to print, you should be able to print from - <application>Evolution</application> immediately. -</para> -<para> - Whether you're printing a message, a calendar page, or a selection - of address cards, you can choose to print directly to a printer, or - save the print output to a postscript file. You can also use the - preview feature to see how your printed output will look. -</para> - - <sect1 id="printpreview"> - <title>Print Preview</title> - <para> - <guibutton>Print Preview</guibutton> appears both as a button in - the printing dialog and as an item in the - <guimenu>File</guimenu> menu. In both places, it does the same - thing: it opens a new window that shows you what would happen if - you were to print the current message, calendar, appointment, or - address card. - </para> - <para> - That window allows you to select which pages you want to see, - and how close you'd like to look at them. Zoom in or out, fit - the page to the window (the <guibutton>Fit</guibutton> button) - or match the width of the page and the window (the - <guibutton>Fit Width</guibutton> button). None of these buttons - changes the way the page will be printed, but they do let you - get a better look. If you're satisfied with the way the things - look, click <guibutton>Print</guibutton> to send your document - on its way. If you'd like to change it, just close the - <guilabel>Print Preview</guilabel> window and make the changes - you want from the Mail, Calendar, or Contact Manager. - </para> - - - <!-- ==============Figure=================================== --> - - <figure id="print-preview"> - <title>Print Preview</title> - <screenshot> - <screeninfo>Print Preview</screeninfo> - <graphic fileref="fig/print-preview" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure============================== --> - - </sect1> - - <sect1 id="print-destination"> - <title>File or Printer?</title> - <para> - The printer selection window, shown in <xref - linkend="print-dest">, lets you choose the format for - printing— at this time, only <guilabel>Generic - Postscript</guilabel> is available— and whether to print - to a file or to an actual printer. If you choose a printer, - you'll be asked for the printer command (probably - <guilabel>lpr</guilabel>) which your system uses. If you - choose to print to a file, you'll need to decide upon a - filename. And of course, you'll want to choose a number of - copies, and whether to collate them. - </para> - - <!-- ==============Figure=================================== --> - - <figure id="print-dest"> - <title>Choosing a Printer</title> - <screenshot> - <screeninfo>Choosing a Printer</screeninfo> - <graphic fileref="fig/print-dest" format="png" srccredit="Aaron Weber"> - </graphic> - </screenshot> - </figure> -<!-- ==============End of Figure============================== --> - - <para> - If you're printing a message that's more than one page, you'll - have the option of choosing which pages to print. If you're - printing a calendar entry, you can decide what range of dates to - print. And, if you're printing contact cards, you can decide - whether to print only the selected cards, or all of them. - </para> - <para> - When you're ready, click <guibutton>Print</guibutton> to print, - <guibutton>Preview</guibutton> to have a look (or another look) - at the preview, or <guibutton>Cancel</guibutton> to cancel the - whole deal. - </para> - </sect1> -</chapter> - - - - - - - diff --git a/help/C/usage-sync.sgml b/help/C/usage-sync.sgml deleted file mode 100644 index a6b53e9526..0000000000 --- a/help/C/usage-sync.sgml +++ /dev/null @@ -1,20 +0,0 @@ - - <chapter id="usage-sync"> - <title>Synchronizing with a Hand-held Device</title> - <para> - This chapter covers is how to synchronize data - installed and configured. If you need information on how to - set up a synchronization system, consult <xref - linkend="config-sync">. - </para> - <sect1 id="hotsync"> - <title>Using HotSync</title> - <para> - Put your hand-held device on its cradle and press the - HotSync button. - </para> - <para> - No, really. That's all there is to it. - </para> - </sect1> - </chapter>
\ No newline at end of file diff --git a/help/COPYING-DOCS b/help/COPYING-DOCS deleted file mode 100644 index b42936beb3..0000000000 --- a/help/COPYING-DOCS +++ /dev/null @@ -1,355 +0,0 @@ - GNU Free Documentation License - Version 1.1, March 2000 - - Copyright (C) 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: How to use this License for your documents - -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 (c) 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. diff --git a/help/Camel-Classes b/help/Camel-Classes deleted file mode 100644 index 93aec087dd..0000000000 --- a/help/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/help/ChangeLog b/help/ChangeLog deleted file mode 100644 index 407bbbdde6..0000000000 --- a/help/ChangeLog +++ /dev/null @@ -1,694 +0,0 @@ -2001-02-23 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: IMAP subscriptions stuff. - -2001-02-21 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: Advanced search/show all/save search stuff. - - * C/evolution.sgml: This file replaces evolution-guide.sgml, for Nautilus Readiness. - - * C/apx-gloss.sgml: glossterm conduit. - - * C/config-sync.sgml: Glossterm conduit. - - * C/preface.sgml: Checked over for Keyboard-Shortcut and other truthfulness. - -2001-02-15 Aaron Weber <aaron@helixcode.com> - - * C/evolution-guide.sgml: Validated. Verified. Markup fixed in - several individual files. - - * C/apx-gpl.sgml: cvs-removed for GNOME 1.4 compliance. - - * C/apx-fdl.sgml: cvs-removed for GNOME 1.4 compliance. - -2001-02-09 Aaron Weber <aaron@helixcode.com> - - * C/config-sync.sgml: Overhaul. Now accurate and truthful and clear. - - * C/usage-calendar.sgml: Minor Changes. - -2001-02-08 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Minor Changes. - - * C/usage-mail.sgml: Minor Changes. - -2001-02-07 Aaron Weber <aaron@helixcode.com> - - * C/menuref.sgml: Added section, but left blank til UI stabilizes. - - * C/usage-exec-summary.sgml: A little functionality described. - - * C/usage-mainwindow.sgml: Added tasks and Exec-summary. - - * C/usage-calendar.sgml: Describe semi-autonomy of task pad. - -2001-02-06 Aaron Weber <aaron@ximian.com> - - * C/usage-contact.sgml: s/contact manager/address book/ and - revised text. - - * C/usage-exec-summary.sgml: New file. Describes Executive Summary. - -2001-01-19 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: More of Megan's revisions, and Field Chooser - functions in the Sort section. - - * C/apx-gloss.sgml: added "ToolTip" - -2001-01-18 Aaron Weber <aaron@helixcode.com> - - * C/preface.sgml: s/Helix Code/Ximian, and Megan's comments. - - * C/usage-mainwindow.sgml: s/Helix Code/Ximian/, and Megan's - comments. - - * C/evolution-guide.sgml: s/Helix Code/Ximian/ - -2000-12-13 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: Revisions as suggested by Dan. Especially to - filter dialogs... which still need some renaming, IMHO. - - * C/usage-mainwindow.sgml: Revisions as suggested by - Dan. Especially to the Folder Limits thing, which still upsets me - somehow. - - * C/preface.sgml: Revisions as suggested by Dan. - -2000-11-29 Aaron Weber <aaron@helixcode.com> - - * C/config-setupassist.sgml: added some <glossterms>, added linkends to existing glossterms. - -2000-11-28 Aaron Weber <aaron@helixcode.com> - - * C/evolution-guide.sgml: Changed intro to Config section. Now - defines what, exactly, "configurable" means. - - * C/usage-print.sgml: Stylistic revisions. - - * C/usage-calendar.sgml: Stylistic revisions. - - * C/usage-contact.sgml: Stylistic revisions. - -2000-11-09 Aaron Weber <aaron@helixcode.com> - - * C/menuref.sgml: Message heading Right-Click Menu. - -2000-11-03 Aaron Weber <aaron@helixcode.com> - - * C/apx-gloss.sgml: The regexp example was quite wrong. Props to Sasha. - -2000-11-02 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Style and spelling. - -2000-11-01 Aaron Weber <aaron@helixcode.com> - - * C/config-prefs.sgml: Fixed validation errors. - - * C/apx-gloss.sgml: Fixed HTML, style stuff. - - * C/usage-mail.sgml: Stylistic overhaul. - - * C/usage-mainwindow.sgml: Fixed groups in shortcut bar, fixed - folder navigation tips. - -2000-10-31 Aaron Weber <aaron@helixcode.com> - - * C/preface.sgml: Minor stylistic revisions. - -2000-10-30 Aaron Weber <aaron@helixcode.com> - - * COPYING-DOCS: New file. This is the official place to put the - FDL now. - - -2000-11-01 Radek Doulik <rodo@helixcode.com> - - * Keybindings: added composer keybindings description - -2000-10-25 Aaron Weber <aaron@helixcode.com> - - * C/menuref.sgml: Actions -> New Directory Server added. - - * C/config-prefs.sgml: Actions -> New Directory Server added. - - * C/usage-contact.sgml: Actions -> New Directory Server added. - - * C/menuref.sgml: Added mail Settings->Manage Subscriptions menu. - - * C/usage-mail.sgml: Subscriptions section added. Quite - incomplete, though. - -2000-10-11 Aaron Weber <aaron@helixcode.com> - - * C/evolution-guide.sgml: Re-checked validity of all files. Made - minor changes to menuref.sgml, usage-mail.sgml, usage-print.sgml to - bring up to spec. - - * C/usage-mail.sgml: Redid Filter & Vfolder to match the new & - improved functionality. - - * C/fig/*: Re-did remaining screenshots. - -2000-10-10 Aaron Weber <aaron@helixcode.com> - - * C/usage-print.sgml: New file, describing printing and print-preview. - - * C/fig/print-preview.png: New file. - - * C/fig/print-dest.png: New file. - - * C/evolution-guide.sgml: Added usage-print entity. - - * C/menuref.sgml: Fixed calendar menu stuff. - - * C/usage-mail.sgml: No more "Actions" menu, other assorted - menu-related changes. - -2000-10-06 Aaron Weber <aaron@helixcode.com> - - * C/fig/ * replaced a whole bunch of screenshots. - -2000-10-05 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Described Search features. - - * C/menuref.sgml: Contact Manager menus fixed. - -2000-10-04 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Fixed glossterms. - - * C/usage-mail.sgml: Fixed glossterms, filenames, spellchecked. - - * C/apx-gloss.sgml: Added "Inline," "VCard". - - * C/usage-mainwindow.sgml: Fixed glossterms, filenames. Spellchecked. - - * C/usage-mail.sgml: Fixed glossterms, filenames. Spellchecked. - - * C/evolution-guide.sgml: New Legalnotice. Removed FDL and GPL, - which are now included as part of the gnome-help package. - - * C/usage-contact.sgml: Spellcheck. Fixed some wording, and - responded to clahey's suggestions-- notably, commented out the - "add to master list" category feature. - - * C/usage-calendar.sgml: Spellcheck. Fixed wording, event overlap - description. - - * C/evolution-guide.sgml: Spellcheck. Commented out Notes - entities. - - * C/usage-notes.sgml: Spellchecked, then decided to comment out - this file/chapter and all references to it, since it's unlikely to - be implemented any time soon. - - * C/config-setupassist.sgml: Spellcheck. Other minor updates. May - need more work in the near future. - - * C/usage-sync.sgml: Now it's really short. And spelled correctly. - -2000-10-03 Aaron Weber <aaron@helixcode.com> - - * C/config-prefs.sgml: Mostly spelling. Still needs major - alteration. - - * C/menuref.sgml: s/Appintment/Appointment, fixed small errors, - ran spellcheck. Still needs lots of work, since many menus have - changed. - - * C/apx-gloss.sgml: Added Virus, Protocol, fixed vFolder, - spellchecked. - -2000-09-26 Aaron Weber <aaron@helixcode.com> - - * C/apx-gloss.sgml: Added sendmail and SMTP. - -2000-09-22 Aaron Weber <aaron@helixcode.com> - - * C/menuref.sgml: Changed to reflect new menu layout. - - * C/usage-mainwindow.sgml: Changed to reflect new menu layout. Again. - - * C/usage-contact.sgml: Stop and Display All features. - -2000-09-21 Aaron Weber <aaron@helixcode.com> - - * C/evolution-guide.sgml: Switched to the "official" FSF markup. - I will have to make changes to the markup-- adding ids, etc, or - switch to another version of the markup. Pending discussion by - GDP. - - * C/apx-authors.sgml: Changed Matt Loper's email address to - loper.org; added Jeff Stedfast and Peter Williams to authors list, - realphebetized. - - * C/config-prefs.sgml: Revision to reflect current options labelling. - - * C/evolution-guide.sgml: Changes to part intros. - - * C/preface.sgml: Spelling and menu fixes. Will need more work tomorrow. - -2000-09-20 Aaron Weber <aaron@helixcode.com> - - * C/config-prefs.sgml: Fixed sig stuff here and in setupassist. - - * C/config-sync.sgml: Fixed description of conduit usage. - -2000-09-18 Aaron Weber <aaron@helixcode.com> - - * C/preface.sgml: Spelling fixes, etc. - -======= -2000-09-19 Federico Mena Quintero <federico@helixcode.com> - - * C/Makefile.am: Fixed to install the stylesheet-images as well. - ->>>>>>> 1.26 -2000-09-07 Aaron Weber <aaron@helixcode.com> - - * C/fig/ New files: contact-editor.png, mail-composer.png, - filter-assist-fig.png, mail-inbox.png - -2000-09-07 Aaron Weber <aaron@helixcode.com> - - * C/preface.sgml: Redid "soft" intro stuff. - - * C/evolution-guide.sgml: Accidentally broke docs, now valid. - -2000-09-06 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Editing, proofing. - -2000-09-05 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Grammar, links, screenshots. - - * fig/* Re-took most screenshots. - - * C/usage-mail.sgml: Filters, proofing. - -2000-09-01 Aaron Weber <aaron@helixcode.com> - - * C/config-prefs.sgml: Added coverage of news, clarified POP/IMAP - distinction (there's a theme to these four log entries here). - - * C/usage-mail.sgml: Added coverage of news. - - * C/config-setupassist.sgml: Revised mail sources content for - IMAP/POP stuff. - - * C/apx-gloss.sgml: Added IMAP and POP. - -2000-08-31 Aaron Weber <aaron@helixcode.com> - - * C/apx-gloss.sgml: Added regular expressions to glossary. - Explanation should be removed from other portions of the book now. - - * C/usage-mainwindow.sgml: Revisions, minor. - - * C/apx-menuref.sgml: Now named menuref.sgml, to reflect its new - status as a part. - - * C/evolution-guide.sgml: Structural alterations: Menuref is now a - part, not an appendix. - - * C/apx-menuref.sgml: Added contextual menus for mail. - - * C/preface.sgml: Added "quickref and pointers" sections. Props to - O'Reilly for the copy of Outlook in a Nutshell which gave me the - idea. - -2000-08-30 Aaron Weber <aaron@helixcode.com> - - * C/usage-mainwindow.sgml: Minor fixes. - - * C/preface.sgml: Corrected grammar, added glossterms, described - menuref. - -2000-08-25 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: Redid filter and vFolder assistant - descriptions. - - * C/fig/filter-new-fig.png: Replaced with new assistant pic. - - * C/fig/filter-assist-fig.png: New file, showing only assistant. - - - * C/apx-menuref.sgml: Finished message composer and calendar - editor menus. Looked at Contact Editor menus and decided to - document those features after implementation. - -2000-08-24 Aaron Weber <aaron@helixcode.com> - - * C/apx-menuref.sgml: Message Composer File and Edit menus. - -2000-08-23 Aaron Weber <aaron@helixcode.com> - - * C/apx-menuref.sgml: Added editor sections. - - * C/evolution-guide.sgml: Included Menu Reference Appendix. - -2000-08-22 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: Minor markup changes. - - * C/apx-menuref.sgml: New File. Menu Reference. Still needs much - work, but not bad for an evening. - -2000-08-21 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: Kevin's diff applied, with minor changes. - -2000-08-09 Aaron Weber <aaron@helixcode.com> - - * C/evolution-guide.sgml: Fixed bugs in validation. Went home to - sleep. - - * C/usage-mainwindow.sgml: Redid menubar description. - - - * C/config-prefs.sgml: Added coverage of folder config, requested - that feature be transferred to config section. Switched to - variablelist in "Other" config section. - - * C/usage-mail.sgml: Added coverage of right-click on messages, - threaded-view. - - * C/usage-mainwindow.sgml: Right-click on folder menu reinstated. - -2000-08-07 Aaron Weber <aaron@helixcode.com> - - * C/config-prefs.sgml: Added news server coverage. Other config - proofing changes. - - -2000-08-05 Aaron Weber <aaron@helixcode.com> - - * C/apx-gpl.sgml: New file. Contains contents of "COPYING", - but marked up (probably not very well, but valid) as docbook - (SGML). - - * C/evolution-guide.sgml: Subtle change to the legal notice: - distinguished manual license from software license. Linked to - apx-gpl.sgml above. - - * C/usage-calendar.sgml: I redid all the usage files. - -2000-07-21 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: Added password remembering/forgetting feature. - - * C/config-prefs.sgml: Mostly moved to variablelists, a few - language changes. - - * C/config-setupassist.sgml: Minor changes to formatting, wording. - - * C/usage-notes.sgml: Changed trademark references, other minor - changes. - - * C/usage-calendar.sgml: Minor fixes, added additional calendar - section, removed references to unimplemented features. Spellcheck, - prep for 0.3 release. - -2000-07-19 Aaron Weber <aaron@helixcode.com> - - * C/usage-mail.sgml: lots of minor fixes to language. added - desc. of clahey's cool button-address thing. - - * C/usage-mainwindow.sgml: fixed itemizedlists, ch. to shortcut - bar & folder descs, removed refs to trash. - -2000-07-18 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Altered category addition stuff, plus - suggestions from Kevin. - - * C/apx-gloss.sgml: Added ldap and signature definitions (from - Kevin). - - * C/usage-mail.sgml: Move to variablelists from itemizedlists. - -2000-07-14 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: moved to variablelists from itemizedlists - * C/usage-calendar.sgml: moved to variablelists from itemizedlists - -2000-06-29 Aaron Weber <aaron@helixcode.com> - - * C/preface.sgml: Minor fixes. - - * C/usage-notes.sgml: New File for feature that is yet to come. - * C/evolution-guide.sgml: Added entity for notes chapter. - * C/usage-mainwindow.sgml: Un-commented references to notes section. - - * C/apx-authors.sgml: Removed dcm from author list. - - * C/usage-calendar.sgml: Added to-do list features. - -2000-06-28 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: commented out future features; redid - contact editor stuff. - - * C/apx-gloss.sgml: Removed "live doc" and added "minicard" - -2000-06-27 Aaron Weber <aaron@helixcode.com> - - * C/devel-action.sgml: Removed file. - * C/devel-script.sgml: Same. - * C/devel-component.sgml: Same. - * C/preface.sgml: Removed references to devel section. - * C/evolution-guide.sgml: Removed references to devel section. - -2000-06-23 Aaron Weber <aaron@helixcode.com> - - * C/evolution-guide.sgml: Made moderate to major stylistic updates - to this, apx-gloss.sgml, and to all files beginning with "usage," - especially wrt HTML mail. - - -2000-06-15 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: Category stuff improved. - - * C/usage-calendar.sgml: Now covers how to add an event properly. - -2000-07-17 Federico Mena Quintero <federico@helixcode.com> - - * Makefile.am (SUBDIRS): Added the devel directory. - -2000-06-28 Peter Williams <peterw@curious-george.helixcode.com> - - * C/Makefile.am (SGML_FILES): Don't depend on the newly-removed - devel-*.sgml files. - -2000-06-16 Damon Chaplin <damon@helixcode.com> - - * C/.cvsignore: added evolution-guide and evolution-guide.junk - so we don't get the '? doc/C/evolution-guide' messages each time we - do a cvs update. - -2000-06-14 Aaron Weber <aaron@helixcode.com> - - * C/usage-mainwindow.sgml: added sect on menubar, other minor changes. - - * C/usage-mail.sgml: Improved filter and vfolder - description, and some minor changes from me and Kevin. - -2000-06-07 Aaron Weber <aaron@helixcode.com> - - * C/config-prefs.sgml: finished adding calendar prefs. screenshots. - * C/fig/config-cal.png: new file (screenshot for above) - * C/fig/config-mail.png: same - -2000-06-05 Aaron Weber <aaron@helixcode.com> - - * C/usage-calendar.sgml: Incorporated chgs from Kevin. - - * C/config-prefs.sgml: began total overhaul of structure and added - content reflecting new prefs items. needs LOTS more work. - - * C/usage-mail.sgml: changed some references to id's in the - config-prefs section. - - * C/fig/config-mail.png: changed filename from config-prefs.png - -2000-06-01 Aaron Weber <aaron@helixcode.com> - - * C/config-prefs.sgml: filename was wrong, altered. - - * C/usage-mail.sgml: improved filter instructions, vFolder - instructions. still need work though. - - - * C/usage-contact.sgml: added screenshot. - - * C/usage-calendar.sgml: added screenshot. - - * C/config-prefs.sgml: added screenshots, and now describes the - actual prefs dialogs. - - * C/fig/config-camel.png: new (screenshot) file - * C/fig/filter-druid.png: same - * C/fig/vfolder-druid.png: same - * C/fig/calendar.png: same - * C/fig/contact.png: same - * C/fig/vfolder-createrule-fig.png: same - * C/fig/filter-new-fig.png: same - * C/fig/config-camel.png: same - -2000-06-01 Dan Winship <danw@helixcode.com> - - * Makefile.am: recurse into the C directory - - * C/Makefile.am: Rules to build and install the docs. Mostly - stolen from gnomecal. Only works if you have GDP stuff - (http://www.gnome.org/gdp/) set up on your machine, but won't make - the build fail if you don't. - -2000-05-29 Aaron Weber <aaron@helixcode.com> - - * C/usage-contact.sgml: incorporated kevins notes. - * C/usage-mainwindow.sgml: incorporated kevins notes. - -2000-05-27 Aaron Weber <aaron@helixcode.com> - - * C/evolution-guide.sgml: added Kevin Breit to author and - copyright. - - * C/apx-authors.sgml: Put app authors in a simplelist. - - * C/usage-mail.sgml: Removed USAGE-SETUP insertion, added xref to send - users to config-setupassist chapter. This and the following changes - take setup druid coverage out of usage - section and put it in config section. - * C/config-setupassist.sgml: Added mail druid coverage from - usage-setup.sgml. - * C/usage-setup.sgml: Removed file. contents in - config-setupassist.sgml. - * C/evolution-guide.sgml: Removed - USAGE-SETUP entity (and file usage-setup.sgml.) - - -2000-05-26 Aaron Weber <aaron@helixcode.com> - - * C/fig/mainwindow-pic.png: new file - * C/fig/mail-druid-pic.png: new file - * C/fig: New directory, for figure graphics. - - * C/apx-gloss.sgml: new file. glossary. thx. to kevin from chicago. - - * C/usage-setup.sgml: More accurate description of druid, and - moved to mail section-- see usage-mail.sgml entry. This is a new - location for this entity, and it may move more later. - - - * C/usage-mainwindow.sgml: altered description of starting - evolution. added screenshot for main-window picture. - - * C/usage-mail.sgml: added screenshots, added coverage of setup - druid and put it into get-and-send section, which is probably not - where it should stay. Also started filter druid coverage and - clarified examples, esp. in Bcc: section. - - * C/usage-contact.sgml: Clarified examples. - - * C/preface.sgml: rewording of "what is" and "about book" sections. - - * C/evolution-guide.sgml: added glossary entity APX-GLOSS, altered - phrasing in part intros, changed order of Setup-assistant section. - - * C/config-prefs.sgml: changed wording, removed ref. to re-running - setup assistant. - -2000-05-18 Aaron Weber <aaron@helixcode.com> - - * 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 <danw@helixcode.com> - - * Camel-Classes: sync - -2000-04-16 Aaron Weber <aaron@helixcode.com> - - * C/evo_book_0.1.sgml: new file (doc sgml) - - * C/ : New directory for doc sgml & graphics - -2000-03-05 Christopher James Lahey <clahey@helixcode.com> - - * white-papers/widgets/e-table.sgml: Added Miguel to the author - list for ETable. - -2000-03-03 Christopher James Lahey <clahey@helixcode.com> - - * 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 <danw@helixcode.com> - - * ibex.sgml: Ibex white paper - -2000-02-29 Federico Mena Quintero <federico@helixcode.com> - - * calendar.sgml: Sections for the calendar user agent and the - calendar client library. - -2000-02-29 Dan Winship <danw@helixcode.com> - - * camel.sgml: Reorg a bit more, make the <PRE> 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 <federico@helixcode.com> - - * calendar.sgml: Section for the personal calendar server. - -2000-02-28 Dan Winship <danw@helixcode.com> - - * camel.sgml: add Bertrand to authors, edit his additions - -2000-02-28 bertrand <bertrand@helixcode.com> - - * 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 <danw@helixcode.com> - - * camel.sgml: Beginnings of a Camel white paper - -2000-02-25 Federico Mena Quintero <federico@helixcode.com> - - * calendar.sgml: New file for the Evolution calendaring white paper. diff --git a/help/Design b/help/Design deleted file mode 100644 index 7b7cf6f821..0000000000 --- a/help/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/help/Keybindings b/help/Keybindings deleted file mode 100644 index f232802110..0000000000 --- a/help/Keybindings +++ /dev/null @@ -1,13 +0,0 @@ -* Keybindings for the mailer - - Delete key: Deletes message, moves forward. - -* Keybindings for the composer - - Control-s: Saves message to file. - Control-w: Closes composer window. - Control-Return: Sends message now. - - F6: Opens find dialog. - F7: Opens replace dialog. - diff --git a/help/Makefile.am b/help/Makefile.am deleted file mode 100644 index 7b5420fee8..0000000000 --- a/help/Makefile.am +++ /dev/null @@ -1 +0,0 @@ -SUBDIRS = C devel diff --git a/help/NAMESPACE b/help/NAMESPACE deleted file mode 100644 index 4ca7c454d1..0000000000 --- a/help/NAMESPACE +++ /dev/null @@ -1,65 +0,0 @@ - - Here is how both the Evolution implementation and IDL namespacing -is to be organized, NB. for implementations and oafinfo filenames we replace -'/' with '_' - -Files: - -/GNOME/Evolution/ - - Addressbook/ - Calendar/ - Control - gnomecal - Composer/ - Mail/ - Notes/ - Shell/ - Summary/ - test - rdf - Wombat/ - -Components: - - Shell components end in _ShellComponent, controls in _Control, -executive summary components in _ExecutiveSummaryComponent and -factories append 'Factory'. - -GNOME/ - Evolution/ - - Shell - - Addressbook/ - MiniCard/ - Control, ControlFactory - SelectNames, SelectNamesFactory - Control, ControlFactory - ShellComponent, ShellComponentFactory - Calendar/ - iTip/ - Control, ControlFactory - Control, ControlFactory - ShellComponent, ShellComponentFactory - ExecutiveSummaryComponent, ExecutiveSummaryComponentFactory - Mail/ - Control, ControlFactory - ShellComponent, ShellComponentFactory - ExecutiveSummaryComponent, ExecutiveSummaryComponentFactory - Composer, ComposerFactory - Notes/ - control, controlFactory - shellComponent, shellComponentFactory - Summary/ - rdf/ - SummaryComponent, SummaryComponentFactory - test/ - Component, ComponentFactory - - ShellComponent, ShellComponentFactory - - Wombat/ - ServerFactory - CalendarFactory - diff --git a/help/devel/.cvsignore b/help/devel/.cvsignore deleted file mode 100644 index c24a54fbcc..0000000000 --- a/help/devel/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -Makefile -Makefile.in -html -evolution-devel-guide.html diff --git a/help/devel/ChangeLog b/help/devel/ChangeLog deleted file mode 100644 index d00a1df434..0000000000 --- a/help/devel/ChangeLog +++ /dev/null @@ -1,159 +0,0 @@ -2001-01-26 John R. Sheets <dusk@ravendusk.org> - - * importer/Makefile.am: Change (nonexistant) importer.sgml - references to evolution-importer.sgml to fix dependency problem. - -2001-01-17 Iain Holmes <iain@ximian.com> - - * Makefile.am (local_entities): Added the importer stuff. - - * evolution-devel-guide.sgml: Added entities for the importer documents. - - * reference.sgml: Added the public and private APIs for the importer. - - * importer/*: New directory containing all the documenation for the - importer. - -2001-01-17 Federico Mena Quintero <federico@ximian.com> - - * evolution-devel-guide.sgml: Ximianified. - - * calendar/evolution-calendar.sgml: Ditto. - - * calendar/cal-util/evolution-cal-util-sections.txt: Updated. - - * calendar/cal-client/evolution-cal-client-sections.txt: Updated. - -2001-01-10 Federico Mena Quintero <federico@helixcode.com> - - * Makefile.am: Make it work when gtk-doc is not installed. - - * calendar/cal-client/Makefile.am: Likewise. - - * calendar/cal-util/Makefile.am: Likewise. - -2000-12-19 Federico Mena Quintero <federico@helixcode.com> - - Added proper dependency lists to the gtk-doc mess. - - * calendar/cal-client/Makefile.am (TARGET_DIR): Removed unused - variable. - (SOURCE_FILES): New variable with the list of source files we - depend on. - (IGNORED_SOURCE_HEADERS): New variable with the headers we ignore - for the gtkdoc-scan phase. - (scan_generated): - (tmpl_dependencies): - (tmpl_sources): - (tmpl_generated); - (sgml_dependencies): - (sgml_generated): Lists of stuff that is generated and that other - stuff depends on. - (all): Added the $(sgml_generated) as the final target. - (install-data-local): Added an installation hook; gtk-doc seems to - want some of its generated files to be installed. - - * calendar/cal-client/evolution-cal-client-sections.txt: Updated. - - * calendar/cal-util/Makefile.am: Made the same changes as for - calendar/cal-client/Makefile.am. - - * calendar/cal-util/evolution-cal-util-sections.txt: Updated. - - * Makefile.am (local_entities): Added alarm-generation.sgml. - (all): Made the main target be the html/index.html. - -2000-12-18 Federico Mena Quintero <federico@helixcode.com> - - * calendar/alarm-generation.sgml: New file with a description of - the algorithm used to generate alarm instances. - - * evolution-devel-guide.sgml: Added an entity for the above - chapter. - - * calendar/evolution-calendar.sgml: Reference the entity here. - - * calendar/Makefile.am (EXTRA_DIST): Added alarm-generation.sgml. - -2000-12-13 Larry Ewing <lewing@helixcode.com> - - * calendar/Makefile.am (EXTRA_DIST): make it public-reference.sgml - not referenc.sgml here. - -2000-11-29 Federico Mena Quintero <federico@helixcode.com> - - * calendar/architecture.sgml: Finished the calendar architecture - chapter. - -2000-11-29 Federico Mena Quintero <federico@helixcode.com> - - * evolution-devel-guide.sgml: Added an id for the API reference <part>. - Added the FDL <legalnotice>. - Added the preface and toplevel reference entities. - Added entities for Evolution, Wombat, and Camel. - Added an appendix for the GNU FDL. - - * preface.sgml: New file with the introduction to the Evolution - Developer's Guide. - - * reference.sgml: Split the toplevel reference part into its own - file. - - * fdl.sgml: Added the GNU Free Documentation License. - - * calendar/evolution-calendar.sgml: Added an id for the <part>. - - * calendar/public-reference.sgml: Added an id for the <reference>. - Moved this file over from calendar/reference.sgml. - - * Makefile.am (local_entities): Added a list of the SGML files - that define entities for inclusion in the toplevel document. This - way we can track documentation file dependencies down to all - levels. - (html/index.html): Made the toplevel document depend on - $(local_entities). Also, removed the "html" target and put its - contents directly here; this way we avoid having .PHONY targets. - (EXTRA_DIST): Removed the evolution_devel_guideDATA; it made no - sense. - (content_files): Added preface.sgml and reference.sgml. - -2000-09-15 Federico Mena Quintero <federico@helixcode.com> - - * evolution-devel-guide.sgml: Made the toplevel <book> id be - "index". - -2000-08-14 Federico Mena Quintero <federico@helixcode.com> - - * calendar/cal-util/*: Integrated the cal-util library into the - documentation framework. - - * calendar/Makefile.am (SUBDIRS): Added the cal-util directory. - - * evolution-devel-guide.sgml: Added entities for the cal-util stuff. - Added entity for libical. - - * calendar/reference.sgml: Added the cal-util reference entries. - - * calendar/cal-client/evolution-cal-client-sections.txt: Updated - for new API. - -2000-08-09 Peter Williams <peterw@helixcode.com> - - * Makefile.am (maintainer-clean-local): Don't depend - on 'clean'; this messes up maintainer-clean. - -2000-07-17 Federico Mena Quintero <federico@helixcode.com> - - * calendar/cal-client/tmpl/cal-client.sgml: Populated. - - * evolution-devel-guide.sgml: New <book> toplevel for the - Evolution Developer's Guide. - - * calendar/evolution-calendar.sgml: New <part> for the calendar - developer's documentation. - - * calendar/architecture.sgml: New <chapter> for the calendar - architecture. - - * calendar/reference.sgml: New <reference> for the calendar API - reference. diff --git a/help/devel/Makefile.am b/help/devel/Makefile.am deleted file mode 100644 index c5ee7a8e50..0000000000 --- a/help/devel/Makefile.am +++ /dev/null @@ -1,84 +0,0 @@ -SUBDIRS = calendar importer executive-summary - -# The name of the module. -DOC_MODULE=evolution-devel-guide - -# The top-level SGML file. -DOC_MAIN_SGML_FILE=evolution-devel-guide.sgml - -HTML_DIR=$(datadir)/gnome/html - -TARGET_DIR=$(HTML_DIR)/$(DOC_MODULE) - -# Add your toplevel files here - -content_files = \ - evolution-devel-guide.sgml \ - fdl.sgml \ - preface.sgml \ - reference.sgml - -# Add your module's hand-written and auto-generated files here; these -# are used for dependency tracking. - -local_entities = \ - calendar/alarm-generation.sgml \ - calendar/architecture.sgml \ - calendar/evolution-calendar.sgml \ - calendar/public-reference.sgml \ - \ - calendar/cal-client/sgml/cal-client.sgml \ - \ - calendar/cal-util/sgml/cal-component.sgml \ - calendar/cal-util/sgml/cal-recur.sgml \ - calendar/cal-util/sgml/cal-util.sgml \ - calendar/cal-util/sgml/timeutil.sgml \ - \ - importer/sgml/evolution-importer.sgml \ - importer/sgml/evolution-importer-client.sgml \ - \ - executive-summary/sgml/executive-summary-component.sgml \ - executive-summary/sgml/executive-summary-component-factory.sgml \ - executive-summary/sgml/executive-summary-component-factory-client.sgml \ - executive-summary/sgml/executive-summary-html-view.sgml - -EXTRA_DIST = \ - $(content_files) - -all: html/index.html - -if ENABLE_GTK_DOC -html/index.html: $(content_files) $(local_entities) - test -d $(srcdir)/html || mkdir $(srcdir)/html - -cd $(srcdir)/html && gtkdoc-mkhtml $(DOC_MODULE) ../$(DOC_MAIN_SGML_FILE) -else -html/index.html: -endif - -clean-local: - rm -f *~ *.bak *.signals *-unused.txt - -maintainer-clean-local: - cd $(srcdir) && rm -rf html - -if ENABLE_GTK_DOC -install-data-local: - $(mkinstalldirs) $(DESTDIR)$(TARGET_DIR) - (installfiles=`echo $(srcdir)/html/*.html`; \ - if test "$$installfiles" = '$(srcdir)/html/*.html'; \ - then echo '-- Nothing to install' ; \ - else \ - for i in $$installfiles; do \ - echo '-- Installing '$$i ; \ - $(INSTALL_DATA) $$i $(DESTDIR)$(TARGET_DIR); \ - done; \ - echo '-- Installing $(srcdir)/html/index.sgml' ; \ - $(INSTALL_DATA) $(srcdir)/html/index.sgml $(DESTDIR)$(TARGET_DIR); \ - echo '-- Fixing Crossreferences' ; \ - gtkdoc-fixxref --module=$(DOC_MODULE) --html-dir=$(HTML_DIR)|| true; \ - fi) -endif - -dist-hook: - mkdir $(distdir)/html - -cp $(srcdir)/html/*.html $(srcdir)/html/*.css $(distdir)/html diff --git a/help/devel/calendar/.cvsignore b/help/devel/calendar/.cvsignore deleted file mode 100644 index 282522db03..0000000000 --- a/help/devel/calendar/.cvsignore +++ /dev/null @@ -1,2 +0,0 @@ -Makefile -Makefile.in diff --git a/help/devel/calendar/Makefile.am b/help/devel/calendar/Makefile.am deleted file mode 100644 index 207672f303..0000000000 --- a/help/devel/calendar/Makefile.am +++ /dev/null @@ -1,7 +0,0 @@ -SUBDIRS = cal-client cal-util - -EXTRA_DIST = \ - alarm-generation.sgml \ - architecture.sgml \ - evolution-calendar.sgml \ - public-reference.sgml diff --git a/help/devel/calendar/alarm-generation.sgml b/help/devel/calendar/alarm-generation.sgml deleted file mode 100644 index 77d35258da..0000000000 --- a/help/devel/calendar/alarm-generation.sgml +++ /dev/null @@ -1,139 +0,0 @@ - <chapter id="calendar-alarm-generation"> - <title>How the Wombat generates alarm instances</title> - - <para> - This chapter describes the algorithm that the &Wombat; uses - internally to generate instances of a calendar component's - alarms. You do not need to read this chapter if you are simply - using the client-side functions. - </para> - - <sect1 id="what-makes-up-an-alarm-trigger"> - <title>What makes up an alarm trigger</title> - - <para> - VTODO and VEVENT calendar components can have any number of - alarms defined for them. Each alarm has a trigger - specification, an alarm type (display, audio, email, or - procedure), and data corresponding to the alarm type. The - Wombat side of things is interested only in the trigger - specification, since this is all that the Wombat needs to - produce alarm instances. - </para> - - <para> - An alarm trigger can be relative or absolute. Relative - triggers occur a certain time before or after the start or end - of a calendar component's occurrence. For example, you could - configure a trigger to notify you 15 minutes before an - appointment starts, so that you can get to its location on - time; or another one to notify you 5 minutes after another - person's meeting has ended, so that you can call that person - on the phone after the meeting and not disturb him while - there. Absolute triggers occur at a specific point in time; - you can configure an alarm to trigger exactly at a particular - date and time that has no relation to the component's - occurrences at all. - </para> - </sect1> - - <sect1 id="generating-trigger-instances"> - <title>Generating trigger instances</title> - - <para> - Generating absolute triggers is trivial; you just use the date - and time they specify. However, relative triggers are - associated to recurrence instances, so in order to generate - trigger instances we must generate the corresponding - recurrence instances and compute the trigger times based on - those. - </para> - - <para> - Since relative triggers are specified as occurring a certain - amount of time before or after each of a calendar component's - recurrence instances, we can compute a trigger time by adding - or subtracting that amount of time to the corresponding - recurrence instance's time. - </para> - - <para> - Recurrence instances are generated by specifying a range of - time and asking the Wombat to generate the instances that - occur within that range. We shall see that the range of time - in which instances occur is not necessarily the same range of - time in which those instances' alarm triggers occur. - </para> - - <para> - Consider an alarm that is set to trigger 10 minutes before the - start time of an event's occurrence, that is, the trigger has - an offset of -10 minutes. Say this event recurs every hour at - 5 minutes past the hour: it would occur at 1:05, 2:05, 3:05, - etc.; the corresponding triggers would occur at 12:55, 1:55, - 2:55, etc. If we wish to compute the alarm triggers that - occur between 4:00 and 6:00 (which would be at 4:55 and 5:55), - then we cannot just generate recurrence instances between 4:00 - and 6:00 because we will miss the 6:05 occurrence which - corresponds to the 5:55 trigger. - </para> - - <para> - The solution is to expand the range of time on both sides to - fit the relative triggers that have the largest time periods. - If a trigger's offset is negative, like the -10 minutes in the - example above, then we must expand the - <emphasis>end</emphasis> of the time range: in the case above, - the range's ending time of 6:00 must be grown by 10 minutes to - 6:10 so that the last recurrence instance will be that of - 6:05; computing the trigger's offset we will get the 5:55 - trigger, which is what we wanted. For triggers with positive - offsets, like if an alarm were to trigger 20 minutes after an - event's occurrence, we must expand the - <emphasis>start</emphasis> of the time range in an analogous - way, by subtracting the time offset from it. - </para> - - <para> - Again, absolute triggers need no special computation. We can - just see if the trigger time is within the requested range of - time, and if so, we take that trigger occurrence into account - for the final result. - </para> - </sect1> - - <sect1 id="alarm-trigger-generation-code"> - <title>Alarm trigger generation code</title> - - <para> - The main function to generate alarm trigger instances is - <function>generate_alarms_for_comp()</function> in - <filename>evolution/calendar/pcs/cal-backend-file.c</filename>. - This function calls <function>compute_alarm_range()</function> - to expand the specified range of time in the way described in - the previous section. It then generates the instances for - relative alarm triggers inside the - <function>add_alarm_occurrences_cb()</function> callback, - which is used by - <function>cal_recur_generate_instances()</function> with the - expanded range of time. The callback goes through all of the - calendar component's relative alarm triggers and adds the - trigger offsets to the occurrence's time; the results are - added as <structname>CalAlarmInstance</structname> structures - to the final list of trigger instances. Finally, - <function>generate_alarms_for_comp()</function> calls - <function>generate_absolute_triggers()</function>, which - simply adds the instances for absolute alarm triggers; these - are the absolute times that are within the time range that was - requested originally. In the very end, the list of instances - is sorted to produce nicer results. - </para> - </sect1> - </chapter> - -<!-- -Local variables: -mode: sgml -sgml-parent-document: ("../evolution-devel-guide.sgml" "book" "part" "") -End: ---> diff --git a/help/devel/calendar/architecture.sgml b/help/devel/calendar/architecture.sgml deleted file mode 100644 index d261f0a7f4..0000000000 --- a/help/devel/calendar/architecture.sgml +++ /dev/null @@ -1,162 +0,0 @@ - <chapter id="calendar-architecture"> - <title>Architecture of the Calendar</title> - - <para> - This chapter gives an overview of the &Evolution; Calendar - architecture. It describes the model/view split of the calendar - into a personal calendar server, or &PCS;, and the GUI clients - that appear inside the &Evolution; Shell. - </para> - - <!-- Model/View Separation --> - - <sect1 id="calendar-model-view"> - <title>Model/View Separation</title> - - <para> - Like other base components in &Evolution;, the calendar - separates the data model from the views or clients. This is - done so that multiple clients can access the same calendar - data in an orderly fashion and without clashes. For example, - the user may be running a graphical calendar client. If he - then wants to synchronize his calendar with a handheld device, - then the corresponding synchronization program (e.g. a conduit - for the <application>gnome-pilot</application> package) will - also need to access the calendar storage. It is important - that both the GUI client and the synchronization program keep - a consistent view of the calendar at all times, otherwise one - of them will be left in an inconsistent state if the - calendar's data changes unexpectedly. - </para> - - <para> - &Evolution; puts the calendar storage in a daemon called the - &Wombat; and completely separates it from clients who wants to - access calendar data. This part of the &Wombat; is called the - personal calendar server, or &PCS;. Clients must contact the - &PCS; and ask it to open an existing calendar or create a new - one. When a calendar component object (e.g. an appointment or - to-do item) changes in the &PCS; it will notify all the - clients that are using the component's parent calendar. - </para> - </sect1> - - <!-- Personal Calendar Server --> - - <sect1> - <title>Personal Calendar Server</title> - - <para> - The personal calendar server, or &PCS;, provides centralized - management and storage of a user's personal calendar. - Multiple clients can connect to the &PCS; simultaneously to - query and modify the user's calendar in a synchronized - fashion. The main features of the &PCS; are as follows: - </para> - - <formalpara> - <title>Storage</title> - - <para> - 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. - </para> - </formalpara> - - <formalpara> - <title>Basic Queries</title> - - <para> - 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. - </para> - </formalpara> - - <formalpara> - <title>Recurrence and Alarm Queries</title> - - <para> - Looking for the events that recur or have alarm triggers in - a specific period of time involves scanning all the - appointments in a calendar. To keep clients from having to - load whole calendars at once, the &PCS; can do these - computations and send the results to clients. - </para> - </formalpara> - - <formalpara> - <title>Modification Log</title> - - <para> - To allow multiple handheld devices to be synchronized - against a calendar, the &PCS; keeps a log of all the - modifications that are done to the calendar. When an - appointment is updated or removed, the &PCS; logs this - action in the modification log. Synchronization conduit - programs can then use this information to do their work. - </para> - </formalpara> - </sect1> - - <!-- Data Views --> - - <sect1> - <title>Data Views</title> - - <para> - &Evolution; provides a graphical calendar client inside the - shell that is just a view onto the data stored in the personal - calendar server. You can launch as many views of a calendar - as you like and they will all receive notification from the - &PCS; when changes occur. The views are then responsible for - updating their respective displays. - </para> - - <para> - Even within a single calendar view in the &Evolution; shell - there can be multiple clients of a single calendar. For - example, in the day view of the &Evolution; calendar there are - three widgets that act as three different clients of the - &PCS;: the multi-day view, the busy days calendar, and the - task list. - </para> - </sect1> - - <!-- Non-graphical Clients --> - - <sect1> - <title>Non-graphical Clients</title> - - <para> - Clients of the personal calendar server can be non-graphical, - that is, they do not have to provide views of the data to the - user. Examples of such clients are the synchronization - conduit programs for handheld devices. These usually run with - no user interface as a result of being invoked by a daemon - that watches the connection to a handheld device. For - example, the calendar synchronization conduit in &Evolution; - gets run when the <application>gpilotd</application> daemon - from the <application>gnome-pilot</application> package - detects that the HotSync button has been pressed on a Palm - Pilot device. - </para> - - <para> - Such clients simply take advantage of the centralized storage - in the &PCS; without presenting any graphical display of the - data; they just act as middlemen between the &PCS; and other - applications. - </para> - </sect1> - </chapter> - -<!-- -Local variables: -mode: sgml -sgml-parent-document: ("../evolution-devel-guide.sgml" "book" "part" "") -End: ---> diff --git a/help/devel/calendar/cal-client/.cvsignore b/help/devel/calendar/cal-client/.cvsignore deleted file mode 100644 index 0842a93f7a..0000000000 --- a/help/devel/calendar/cal-client/.cvsignore +++ /dev/null @@ -1,3 +0,0 @@ -sgml -Makefile -Makefile.in diff --git a/help/devel/calendar/cal-client/Makefile.am b/help/devel/calendar/cal-client/Makefile.am deleted file mode 100644 index f3a2b39ec6..0000000000 --- a/help/devel/calendar/cal-client/Makefile.am +++ /dev/null @@ -1,131 +0,0 @@ -# The name of the module. -DOC_MODULE=evolution-cal-client - -# The directory containing the source code (if it contains documentation). -DOC_SOURCE_DIR=$(EVOLUTION_DIR)/calendar/cal-client - -CFLAGS =" \ - -I$(top_srcdir)/calendar \ - -I$(top_srcdir) \ - -I$(top_builddir) \ - -I$(top_builddir)/libical/src/libical \ - -I$(top_srcdir)/libical/src/libical \ - $(BONOBO_VFS_GNOME_CFLAGS) \ - " - -LDFLAGS=" \ - $(BONOBO_VFS_GNOME_LIBS) \ - $(top_builddir)/calendar/cal-client/.libs/libcal-client.a \ - $(top_builddir)/calendar/cal-util/.libs/libcal-util.a \ - $(top_builddir)/libical/src/libical/.libs/libical.a \ - $(top_builddir)/libversit/.libs/libversit.al \ - " - -DOC_DIR=$(datadir)/gnome/html - -DOC_DIR_INSTALL_FILES = \ - evolution-cal-client.args \ - evolution-cal-client.hierarchy \ - evolution-cal-client.signals \ - evolution-cal-client.types \ - evolution-cal-client-decl.txt \ - evolution-cal-client-sections.txt - -SOURCE_FILES = \ - $(top_srcdir)/calendar/cal-client/cal-client.c \ - $(top_srcdir)/calendar/cal-client/cal-client.h \ - $(top_srcdir)/calendar/cal-client/cal-client-types.c \ - $(top_srcdir)/calendar/cal-client/cal-client-types.h - -IGNORED_HEADER_FILES = \ - cal-listener.h \ - evolution-calendar.h - -scan_generated = \ - evolution-cal-client-decl.txt \ - evolution-cal-client.args \ - evolution-cal-client.hierarchy \ - evolution-cal-client.signals \ - evolution-cal-client.types - -tmpl_dependencies = \ - evolution-cal-client-decl.txt \ - evolution-cal-client-sections.txt \ - evolution-cal-client.args \ - evolution-cal-client.hierarchy \ - evolution-cal-client.signals - -tmpl_sources = \ - tmpl/cal-client.sgml \ - tmpl/evolution-cal-client-unused.sgml - -tmpl_generated = \ - evolution-cal-client-unused.txt - -sgml_dependencies = \ - evolution-cal-client-decl.txt \ - evolution-cal-client-sections.txt \ - evolution-cal-client.args \ - evolution-cal-client.hierarchy \ - evolution-cal-client.signals \ - tmpl/cal-client.sgml - -sgml_generated = \ - sgml/cal-client.sgml \ - sgml/evolution-cal-client-doc.bottom \ - sgml/evolution-cal-client-doc.top \ - sgml/object_index.sgml \ - sgml/tree_index.sgml - -EXTRA_DIST = \ - evolution-cal-client.args \ - evolution-cal-client.hierarchy \ - evolution-cal-client.signals \ - evolution-cal-client.types \ - evolution-cal-client-decl.txt \ - evolution-cal-client-sections.txt - -all: $(sgml_generated) - -if ENABLE_GTK_DOC -scan $(scan_generated): $(SOURCE_FILES) - -(cd $(srcdir) \ - && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS) \ - gtkdoc-scanobj --module=$(DOC_MODULE) \ - && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) \ - --ignore-headers="$(IGNORED_HEADER_FILES)" ) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE) - -sgml $(sgml_generated): $(sgml_dependencies) - cd $(srcdir) \ - && gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) -else -scan $(scan_generated): $(SOURCE_FILES) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - -sgml $(sgml_generated): $(sgml_dependencies) -endif - -clean-local: - rm -f *~ *.bak *.signals *-unused.txt - -maintainer-clean-local: clean - cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt - -install-data-local: - $(mkinstalldirs) $(DOC_DIR) - for i in $(DOC_DIR_INSTALL_FILES); do \ - $(INSTALL_DATA) $$i $(DOC_DIR); \ - done - -dist-hook: - mkdir $(distdir)/sgml - mkdir $(distdir)/tmpl - -cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl - -cp $(srcdir)/sgml/*.sgml $(distdir)/sgml - -cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml - -.PHONY: scan templates sgml diff --git a/help/devel/calendar/cal-client/evolution-cal-client-decl.txt b/help/devel/calendar/cal-client/evolution-cal-client-decl.txt deleted file mode 100644 index 0bc30e6462..0000000000 --- a/help/devel/calendar/cal-client/evolution-cal-client-decl.txt +++ /dev/null @@ -1,161 +0,0 @@ -<MACRO> -<NAME>CAL_CLIENT_TYPE</NAME> -#define CAL_CLIENT_TYPE (cal_client_get_type ()) -</MACRO> -<MACRO> -<NAME>CAL_CLIENT</NAME> -#define CAL_CLIENT(obj) (GTK_CHECK_CAST ((obj), CAL_CLIENT_TYPE, CalClient)) -</MACRO> -<MACRO> -<NAME>CAL_CLIENT_CLASS</NAME> -#define CAL_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), CAL_CLIENT_TYPE, CalClientClass)) -</MACRO> -<MACRO> -<NAME>IS_CAL_CLIENT</NAME> -#define IS_CAL_CLIENT(obj) (GTK_CHECK_TYPE ((obj), CAL_CLIENT_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_CAL_CLIENT_CLASS</NAME> -#define IS_CAL_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((klass), CAL_CLIENT_TYPE)) -</MACRO> -<STRUCT> -<NAME>CalClient</NAME> -</STRUCT> -<STRUCT> -<NAME>CalClientClass</NAME> -</STRUCT> -<STRUCT> -<NAME>CalClientPrivate</NAME> -</STRUCT> -<ENUM> -<NAME>CalClientOpenStatus</NAME> -typedef enum { - CAL_CLIENT_OPEN_SUCCESS, - CAL_CLIENT_OPEN_ERROR, - CAL_CLIENT_OPEN_NOT_FOUND, - CAL_CLIENT_OPEN_METHOD_NOT_SUPPORTED -} CalClientOpenStatus; -</ENUM> -<ENUM> -<NAME>CalClientGetStatus</NAME> -typedef enum { - CAL_CLIENT_GET_SUCCESS, - CAL_CLIENT_GET_NOT_FOUND, - CAL_CLIENT_GET_SYNTAX_ERROR -} CalClientGetStatus; -</ENUM> -<ENUM> -<NAME>CalClientLoadState</NAME> -typedef enum { - CAL_CLIENT_LOAD_NOT_LOADED, - CAL_CLIENT_LOAD_LOADING, - CAL_CLIENT_LOAD_LOADED -} CalClientLoadState; -</ENUM> -<STRUCT> -<NAME>CalClient</NAME> -struct CalClient { - GtkObject object; - - /* Private data */ - CalClientPrivate *priv; -}; -</STRUCT> -<FUNCTION> -<NAME>cal_client_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>cal_client_construct</NAME> -<RETURNS>CalClient *</RETURNS> -CalClient *client -</FUNCTION> -<FUNCTION> -<NAME>cal_client_new</NAME> -<RETURNS>CalClient *</RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>cal_client_open_calendar</NAME> -<RETURNS>gboolean </RETURNS> -CalClient *client, const char *str_uri, gboolean only_if_exists -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_load_state</NAME> -<RETURNS>CalClientLoadState </RETURNS> -CalClient *client -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_uri</NAME> -<RETURNS>const char *</RETURNS> -CalClient *client -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_n_objects</NAME> -<RETURNS>int </RETURNS> -CalClient *client, CalObjType type -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_object</NAME> -<RETURNS>CalClientGetStatus </RETURNS> -CalClient *client,const char *uid,CalComponent **comp -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_uids</NAME> -<RETURNS>GList *</RETURNS> -CalClient *client, CalObjType type -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_changes</NAME> -<RETURNS>GList *</RETURNS> -CalClient *client, CalObjType type, const char *change_id -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_objects_in_range</NAME> -<RETURNS>GList *</RETURNS> -CalClient *client, CalObjType type,time_t start, time_t end -</FUNCTION> -<FUNCTION> -<NAME>cal_client_generate_instances</NAME> -<RETURNS>void </RETURNS> -CalClient *client, CalObjType type,time_t start, time_t end,CalRecurInstanceFn cb, gpointer cb_data -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_alarms_in_range</NAME> -<RETURNS>GSList *</RETURNS> -CalClient *client, time_t start, time_t end -</FUNCTION> -<FUNCTION> -<NAME>cal_client_free_alarms</NAME> -<RETURNS>void </RETURNS> -GSList *comp_alarms -</FUNCTION> -<FUNCTION> -<NAME>cal_client_get_alarms_for_object</NAME> -<RETURNS>gboolean </RETURNS> -CalClient *client, const char *uid,time_t start, time_t end,CalComponentAlarms **alarms -</FUNCTION> -<FUNCTION> -<NAME>cal_client_update_object</NAME> -<RETURNS>gboolean </RETURNS> -CalClient *client, CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_client_remove_object</NAME> -<RETURNS>gboolean </RETURNS> -CalClient *client, const char *uid -</FUNCTION> -<ENUM> -<NAME>CalClientChangeType</NAME> -typedef enum { - CAL_CLIENT_CHANGE_ADDED = 1 << 0, - CAL_CLIENT_CHANGE_MODIFIED = 1 << 1, - CAL_CLIENT_CHANGE_DELETED = 1 << 2 -} CalClientChangeType; -</ENUM> -<FUNCTION> -<NAME>cal_client_change_list_free</NAME> -<RETURNS>void </RETURNS> -GList *list -</FUNCTION> diff --git a/help/devel/calendar/cal-client/evolution-cal-client-sections.txt b/help/devel/calendar/cal-client/evolution-cal-client-sections.txt deleted file mode 100644 index 0ce8d9427d..0000000000 --- a/help/devel/calendar/cal-client/evolution-cal-client-sections.txt +++ /dev/null @@ -1,44 +0,0 @@ -<INCLUDE>cal-client/cal-client.h</INCLUDE> - -<SECTION> -<FILE>cal-client</FILE> -CAL_CLIENT -<TITLE>CalClient</TITLE> - -CalClientOpenStatus -CalClientGetStatus -CalClientLoadState - -CalClientChangeType - -cal_client_new -cal_client_open_calendar -cal_client_get_load_state -cal_client_get_uri -cal_client_get_n_objects -cal_client_get_uids -cal_client_get_object -cal_client_get_changes -cal_client_change_list_free -cal_client_get_objects_in_range -cal_client_generate_instances -cal_client_get_alarms_in_range -cal_client_free_alarms -cal_client_get_alarms_for_object -cal_client_update_object -cal_client_remove_object - -<SUBSECTION Standard> - -CAL_CLIENT_TYPE -IS_CAL_CLIENT -CAL_CLIENT_CLASS -IS_CAL_CLIENT_CLASS -cal_client_get_type -cal_client_construct - -<SUBSECTION Private> -CalClient -CalClientPrivate - -</SECTION> diff --git a/help/devel/calendar/cal-client/evolution-cal-client.args b/help/devel/calendar/cal-client/evolution-cal-client.args deleted file mode 100644 index e69de29bb2..0000000000 --- a/help/devel/calendar/cal-client/evolution-cal-client.args +++ /dev/null diff --git a/help/devel/calendar/cal-client/evolution-cal-client.hierarchy b/help/devel/calendar/cal-client/evolution-cal-client.hierarchy deleted file mode 100644 index 88efa3e673..0000000000 --- a/help/devel/calendar/cal-client/evolution-cal-client.hierarchy +++ /dev/null @@ -1,2 +0,0 @@ -GtkObject - CalClient diff --git a/help/devel/calendar/cal-client/evolution-cal-client.signals b/help/devel/calendar/cal-client/evolution-cal-client.signals deleted file mode 100644 index 65d142777a..0000000000 --- a/help/devel/calendar/cal-client/evolution-cal-client.signals +++ /dev/null @@ -1,21 +0,0 @@ -<SIGNAL> -<NAME>CalClient::cal-opened</NAME> -<RETURNS>void</RETURNS> -CalClient *calclient -gint arg1 -</SIGNAL> - -<SIGNAL> -<NAME>CalClient::obj-updated</NAME> -<RETURNS>void</RETURNS> -CalClient *calclient -gchar *arg1 -</SIGNAL> - -<SIGNAL> -<NAME>CalClient::obj-removed</NAME> -<RETURNS>void</RETURNS> -CalClient *calclient -gchar *arg1 -</SIGNAL> - diff --git a/help/devel/calendar/cal-client/evolution-cal-client.types b/help/devel/calendar/cal-client/evolution-cal-client.types deleted file mode 100644 index 84d65a6637..0000000000 --- a/help/devel/calendar/cal-client/evolution-cal-client.types +++ /dev/null @@ -1,4 +0,0 @@ -#include <gnome.h> -#include <cal-client/cal-client.h> - -cal_client_get_type diff --git a/help/devel/calendar/cal-client/tmpl/cal-client.sgml b/help/devel/calendar/cal-client/tmpl/cal-client.sgml deleted file mode 100644 index 06195ca454..0000000000 --- a/help/devel/calendar/cal-client/tmpl/cal-client.sgml +++ /dev/null @@ -1,303 +0,0 @@ -<!-- ##### SECTION Title ##### --> -CalClient - -<!-- ##### SECTION Short_Description ##### --> -GTK+ object for communication with personal calendar server. - -<!-- ##### SECTION Long_Description ##### --> - <para> - The #CalClient object provides a nice GTK+ wrapper for the CORBA - interfaces that are used to communicate between calendar clients - and the personal calendar server in the user's Wombat daemon. The - CORBA interfaces transfer calendar components in RFC 2445 text - format; the #CalClient object automatically converts these into - #CalComponent structures that are easier to handle. - </para> - - <para> - After a #CalClient object is created with cal_client_new(), it - should be asked to send a request to the personal calendar server - to load or create a calendar based on its URI. The server will - asynchronously notify the client about completion of the request, - and will return an appropriate result code; this should be noted - by the client with the <link - linkend="CalClient--cal-loaded">cal_loaded</link> signal. - </para> - - <para> - When a client asks the server to update or delete a calendar - component from the storage, the server will do so and then notify - all the clients about the update or removal. This is the core of - the model/view split between calendar clients and the storage in - the personal calendar server. Clients should watch the <link - linkend="calclient-obj-updated">obj_updated</link> and <link - linkend="calclient-obj-removed">obj_removed</link> signals on the - CalClient objects they create so that they can be notified about - changes in the storage. - </para> - -<!-- ##### SECTION See_Also ##### --> - <para> - #CalComponent - </para> - -<!-- ##### MACRO CAL_CLIENT ##### --> - <para> - Casts a #GtkObject to a #CalClient. - </para> - -@obj: A GTK+ object. - - -<!-- ##### ENUM CalClientOpenStatus ##### --> -<para> - -</para> - -@CAL_CLIENT_OPEN_SUCCESS: -@CAL_CLIENT_OPEN_ERROR: -@CAL_CLIENT_OPEN_NOT_FOUND: -@CAL_CLIENT_OPEN_METHOD_NOT_SUPPORTED: - -<!-- ##### ENUM CalClientGetStatus ##### --> - <para> - These values describe the result of the cal_client_get_object() - function. - </para> - -@CAL_CLIENT_GET_SUCCESS: -@CAL_CLIENT_GET_NOT_FOUND: -@CAL_CLIENT_GET_SYNTAX_ERROR: - -<!-- ##### ENUM CalClientLoadState ##### --> -<para> - -</para> - -@CAL_CLIENT_LOAD_NOT_LOADED: -@CAL_CLIENT_LOAD_LOADING: -@CAL_CLIENT_LOAD_LOADED: - -<!-- ##### ENUM CalClientChangeType ##### --> -<para> - -</para> - -@CAL_CLIENT_CHANGE_ADDED: -@CAL_CLIENT_CHANGE_MODIFIED: -@CAL_CLIENT_CHANGE_DELETED: - -<!-- ##### FUNCTION cal_client_new ##### --> -<para> - -</para> - -@Returns: - - -<!-- ##### FUNCTION cal_client_open_calendar ##### --> -<para> - -</para> - -@client: -@str_uri: -@only_if_exists: -@Returns: - - -<!-- ##### FUNCTION cal_client_get_load_state ##### --> -<para> - -</para> - -@client: -@Returns: - - -<!-- ##### FUNCTION cal_client_get_uri ##### --> -<para> - -</para> - -@client: -@Returns: - - -<!-- ##### FUNCTION cal_client_get_n_objects ##### --> -<para> - -</para> - -@client: -@type: -@Returns: - - -<!-- ##### FUNCTION cal_client_get_uids ##### --> -<para> - -</para> - -@client: -@type: -@Returns: - - -<!-- ##### FUNCTION cal_client_get_object ##### --> -<para> - -</para> - -@client: -@uid: -@comp: -@Returns: -<!-- # Unused Parameters # --> -@ico: - - -<!-- ##### FUNCTION cal_client_get_changes ##### --> -<para> - -</para> - -@client: -@type: -@change_id: -@Returns: - - -<!-- ##### FUNCTION cal_client_change_list_free ##### --> -<para> - -</para> - -@list: - - -<!-- ##### FUNCTION cal_client_get_objects_in_range ##### --> -<para> - -</para> - -@client: -@type: -@start: -@end: -@Returns: - - -<!-- ##### FUNCTION cal_client_generate_instances ##### --> -<para> - -</para> - -@client: -@type: -@start: -@end: -@cb: -@cb_data: - - -<!-- ##### FUNCTION cal_client_get_alarms_in_range ##### --> -<para> - -</para> - -@client: -@start: -@end: -@Returns: - - -<!-- ##### FUNCTION cal_client_free_alarms ##### --> -<para> - -</para> - -@comp_alarms: - - -<!-- ##### FUNCTION cal_client_get_alarms_for_object ##### --> -<para> - -</para> - -@client: -@uid: -@start: -@end: -@alarms: -@Returns: - - -<!-- ##### FUNCTION cal_client_update_object ##### --> -<para> - -</para> - -@client: -@comp: -@Returns: -<!-- # Unused Parameters # --> -@ico: - - -<!-- ##### FUNCTION cal_client_remove_object ##### --> -<para> - -</para> - -@client: -@uid: -@Returns: - - -<!-- ##### SIGNAL CalClient::cal-opened ##### --> -<para> - -</para> - -@calclient: the object which received the signal. -@arg1: - -<!-- ##### SIGNAL CalClient::obj-updated ##### --> - <para> - This signal is emitted when the calendar clients receives - notification of a calendar component's data being changed in the - personal calendar server. Graphical clients may want to get the - new version of the object and update their display, for example. - </para> - -@calclient: the object which received the signal. -@arg1: -<!-- # Unused Parameters # --> -@client: Calendar client which received the notification. -@uid: Unique identifier of the calendar component that changed in the - personal calendar server's storage. - -<!-- ##### SIGNAL CalClient::obj-removed ##### --> - <para> - This signal is emitted when the calendar client receives - notification for a calendar component being removed from the - storage in the personal calendar server. Graphical clients may - want to delete the corresponding object from their display, for - example. - </para> - -@calclient: the object which received the signal. -@arg1: -<!-- # Unused Parameters # --> -@client: Calendar client which received the notification. -@uid: Unique identifier of the calendar component that was removed - from the personal calendar server's storage. - -<!-- -Local variables: -mode: sgml -sgml-parent-document: ("../../../evolution-devel-guide.sgml" "book" "refsect2" "") -End: ---> - diff --git a/help/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml b/help/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml deleted file mode 100644 index 56bcf3aff5..0000000000 --- a/help/devel/calendar/cal-client/tmpl/evolution-cal-client-unused.sgml +++ /dev/null @@ -1,84 +0,0 @@ -<!-- ##### FUNCTION cal_client_update_pilot_id ##### --> -<para> - -</para> - -@client: -@uid: -@pilot_id: -@pilot_status: - -<!-- ##### FUNCTION cal_client_load_calendar ##### --> -<para> - -</para> - -@client: -@str_uri: -@Returns: - -<!-- ##### ENUM CalClientLoadStatus ##### --> - <para> - These values describe the status of a calendar load or create - request. After asking a calendar factory to load or create a - calendar, the provided listener will get notification about the - result in asynchronous fashion. Such notification is represented - by one of these enumeration values. For values other than - #CAL_CLIENT_LOAD_SUCCESS, the #CalClient object will not accept - any other operations on the calendar and it should just be - destroyed. - </para> - - -<!-- ##### FUNCTION cal_client_get_events_in_range ##### --> -<para> - -</para> - -@client: -@start: -@end: -@Returns: - -<!-- ##### SIGNAL CalClient::cal-loaded ##### --> - <para> - This signal is emitted some time after the calendar clients sends - a load or create request to the personal calendar server. The - server will notify the client asynchronously of the completion of - the request. The @status parameter indicates the status of the - request. - </para> - -@calclient: the object which received the signal. -@arg1: -@client: Calendar client which received the notification. -@status: Status of the request. See the description of - #CalClientLoadStatus for more details. - -<!-- ##### FUNCTION cal_client_is_loaded ##### --> -<para> - -</para> - -@client: -@Returns: - -<!-- ##### FUNCTION cal_client_create_calendar ##### --> -<para> - -</para> - -@client: -@str_uri: -@Returns: - -<!-- ##### FUNCTION cal_client_get_uid_by_pilot_id ##### --> -<para> - -</para> - -@client: -@pilot_id: -@uid: -@Returns: - diff --git a/help/devel/calendar/cal-util/.cvsignore b/help/devel/calendar/cal-util/.cvsignore deleted file mode 100644 index 0842a93f7a..0000000000 --- a/help/devel/calendar/cal-util/.cvsignore +++ /dev/null @@ -1,3 +0,0 @@ -sgml -Makefile -Makefile.in diff --git a/help/devel/calendar/cal-util/Makefile.am b/help/devel/calendar/cal-util/Makefile.am deleted file mode 100644 index 7f567652ef..0000000000 --- a/help/devel/calendar/cal-util/Makefile.am +++ /dev/null @@ -1,142 +0,0 @@ -# The name of the module. -DOC_MODULE=evolution-cal-util - -# The directory containing the source code (if it contains documentation). -DOC_SOURCE_DIR=$(EVOLUTION_DIR)/calendar/cal-util - -CFLAGS =" \ - -I$(top_srcdir)/calendar \ - -I$(top_srcdir) \ - -I$(top_builddir) \ - -I$(top_builddir)/libical/src/libical \ - -I$(top_srcdir)/libical/src/libical \ - $(BONOBO_VFS_GNOME_CFLAGS) \ - " - -LDFLAGS=" \ - $(BONOBO_VFS_GNOME_LIBS) \ - $(top_builddir)/calendar/cal-util/.libs/libcal-util.a \ - $(top_builddir)/libical/src/libical/.libs/libical.a \ - $(top_builddir)/libversit/.libs/libversit.al \ - " - -DOC_DIR=$(datadir)/gnome/html - -DOC_DIR_INSTALL_FILES = \ - evolution-cal-util.args \ - evolution-cal-util.hierarchy \ - evolution-cal-util.signals \ - evolution-cal-util.types \ - evolution-cal-util-decl.txt \ - evolution-cal-util-sections.txt - -SOURCE_FILES = \ - $(top_srcdir)/calendar/cal-util/cal-component.c \ - $(top_srcdir)/calendar/cal-util/cal-component.h \ - $(top_srcdir)/calendar/cal-util/cal-recur.c \ - $(top_srcdir)/calendar/cal-util/cal-recur.h \ - $(top_srcdir)/calendar/cal-util/cal-util.c \ - $(top_srcdir)/calendar/cal-util/cal-util.h \ - $(top_srcdir)/calendar/cal-util/timeutil.c \ - $(top_srcdir)/calendar/cal-util/timeutil.h - -IGNORED_HEADER_FILES = \ - calobj.h - -scan_generated = \ - evolution-cal-util-decl.txt \ - evolution-cal-util.args \ - evolution-cal-util.hierarchy \ - evolution-cal-util.signals \ - evolution-cal-util.types - -tmpl_dependencies = \ - evolution-cal-util-decl.txt \ - evolution-cal-util-sections.txt \ - evolution-cal-util.args \ - evolution-cal-util.hierarchy \ - evolution-cal-util.signals - -tmpl_sources = \ - tmpl/cal-component.sgml \ - tmpl/cal-recur.sgml \ - tmpl/cal-util.sgml \ - tmpl/evolution-cal-util-unused.sgml \ - tmpl/timeutil.sgml - -tmpl_generated = \ - evolution-cal-util-unused.txt - -sgml_dependencies = \ - evolution-cal-util-decl.txt \ - evolution-cal-util-sections.txt \ - evolution-cal-util.args \ - evolution-cal-util.hierarchy \ - evolution-cal-util.signals \ - tmpl/cal-component.sgml \ - tmpl/cal-recur.sgml \ - tmpl/cal-util.sgml \ - tmpl/timeutil.sgml - -sgml_generated = \ - sgml/cal-component.sgml \ - sgml/cal-recur.sgml \ - sgml/cal-util.sgml \ - sgml/evolution-cal-util-doc.bottom \ - sgml/evolution-cal-util-doc.top \ - sgml/object_index.sgml \ - sgml/timeutil.sgml \ - sgml/tree_index.sgml - -EXTRA_DIST = \ - evolution-cal-util.args \ - evolution-cal-util.hierarchy \ - evolution-cal-util.signals \ - evolution-cal-util.types \ - evolution-cal-util-decl.txt \ - evolution-cal-util-sections.txt - -all: $(sgml_generated) - -if ENABLE_GTK_DOC -scan $(scan_generated): $(SOURCE_FILES) - -(cd $(srcdir) \ - && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS) \ - gtkdoc-scanobj --module=$(DOC_MODULE) \ - && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) \ - --ignore-headers="$(IGNORED_HEADER_FILES)" ) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE) - -sgml $(sgml_generated): $(sgml_dependencies) - cd $(srcdir) \ - && gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) -else -scan $(scan_generated): $(SOURCE_FILES) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - -sgml $(sgml_generated): $(sgml_dependencies) -endif - -clean-local: - rm -f *~ *.bak *.signals *-unused.txt - -maintainer-clean-local: clean - cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt - -install-data-local: - $(mkinstalldirs) $(DOC_DIR) - for i in $(DOC_DIR_INSTALL_FILES); do \ - $(INSTALL_DATA) $$i $(DOC_DIR); \ - done - -dist-hook: - mkdir $(distdir)/sgml - mkdir $(distdir)/tmpl - -cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl - -cp $(srcdir)/sgml/*.sgml $(distdir)/sgml - -cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml - -.PHONY: scan templates sgml diff --git a/help/devel/calendar/cal-util/evolution-cal-util-decl.txt b/help/devel/calendar/cal-util/evolution-cal-util-decl.txt deleted file mode 100644 index b524235de2..0000000000 --- a/help/devel/calendar/cal-util/evolution-cal-util-decl.txt +++ /dev/null @@ -1,780 +0,0 @@ -<MACRO> -<NAME>CAL_COMPONENT_TYPE</NAME> -#define CAL_COMPONENT_TYPE (cal_component_get_type ()) -</MACRO> -<MACRO> -<NAME>CAL_COMPONENT</NAME> -#define CAL_COMPONENT(obj) (GTK_CHECK_CAST ((obj), CAL_COMPONENT_TYPE, CalComponent)) -</MACRO> -<MACRO> -<NAME>CAL_COMPONENT_CLASS</NAME> -#define CAL_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), CAL_COMPONENT_TYPE, \ - CalComponentClass)) -</MACRO> -<MACRO> -<NAME>IS_CAL_COMPONENT</NAME> -#define IS_CAL_COMPONENT(obj) (GTK_CHECK_TYPE ((obj), CAL_COMPONENT_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_CAL_COMPONENT_CLASS</NAME> -#define IS_CAL_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((klass), CAL_COMPONENT_TYPE)) -</MACRO> -<ENUM> -<NAME>CalComponentVType</NAME> -typedef enum { - CAL_COMPONENT_NO_TYPE, - CAL_COMPONENT_EVENT, - CAL_COMPONENT_TODO, - CAL_COMPONENT_JOURNAL, - CAL_COMPONENT_FREEBUSY, - CAL_COMPONENT_TIMEZONE -} CalComponentVType; -</ENUM> -<ENUM> -<NAME>CalComponentField</NAME> -typedef enum { - CAL_COMPONENT_FIELD_CATEGORIES, /* concatenation of the categories list */ - CAL_COMPONENT_FIELD_CLASSIFICATION, - CAL_COMPONENT_FIELD_COMPLETED, - CAL_COMPONENT_FIELD_DTEND, - CAL_COMPONENT_FIELD_DTSTART, - CAL_COMPONENT_FIELD_DUE, - CAL_COMPONENT_FIELD_GEO, - CAL_COMPONENT_FIELD_PERCENT, - CAL_COMPONENT_FIELD_PRIORITY, - CAL_COMPONENT_FIELD_SUMMARY, - CAL_COMPONENT_FIELD_TRANSPARENCY, - CAL_COMPONENT_FIELD_URL, - CAL_COMPONENT_FIELD_HAS_ALARMS, /* not a real field */ - CAL_COMPONENT_FIELD_ICON, /* not a real field */ - CAL_COMPONENT_FIELD_COMPLETE, /* not a real field */ - CAL_COMPONENT_FIELD_RECURRING, /* not a real field */ - CAL_COMPONENT_FIELD_OVERDUE, /* not a real field */ - CAL_COMPONENT_FIELD_COLOR, /* not a real field */ - CAL_COMPONENT_FIELD_NUM_FIELDS -} CalComponentField; -</ENUM> -<ENUM> -<NAME>CalComponentClassification</NAME> -typedef enum { - CAL_COMPONENT_CLASS_NONE, - CAL_COMPONENT_CLASS_PUBLIC, - CAL_COMPONENT_CLASS_PRIVATE, - CAL_COMPONENT_CLASS_CONFIDENTIAL, - CAL_COMPONENT_CLASS_UNKNOWN -} CalComponentClassification; -</ENUM> -<TYPEDEF> -<NAME>CalComponentDateTime</NAME> -typedef struct { - /* Actual date/time value */ - struct icaltimetype *value; - - /* Timezone ID */ - const char *tzid; -} CalComponentDateTime; -</TYPEDEF> -<ENUM> -<NAME>CalComponentPeriodType</NAME> -typedef enum { - CAL_COMPONENT_PERIOD_DATETIME, - CAL_COMPONENT_PERIOD_DURATION -} CalComponentPeriodType; -</ENUM> -<TYPEDEF> -<NAME>CalComponentPeriod</NAME> -typedef struct { - CalComponentPeriodType type; - - struct icaltimetype start; - - union { - struct icaltimetype end; - struct icaldurationtype duration; - } u; -} CalComponentPeriod; -</TYPEDEF> -<TYPEDEF> -<NAME>CalComponentText</NAME> -typedef struct { - /* Description string */ - const char *value; - - /* Alternate representation URI */ - const char *altrep; -} CalComponentText; -</TYPEDEF> -<ENUM> -<NAME>CalComponentTransparency</NAME> -typedef enum { - CAL_COMPONENT_TRANSP_NONE, - CAL_COMPONENT_TRANSP_TRANSPARENT, - CAL_COMPONENT_TRANSP_OPAQUE, - CAL_COMPONENT_TRANSP_UNKNOWN -} CalComponentTransparency; -</ENUM> -<STRUCT> -<NAME>CalComponent</NAME> -</STRUCT> -<STRUCT> -<NAME>CalComponentClass</NAME> -</STRUCT> -<STRUCT> -<NAME>CalComponentPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>CalComponent</NAME> -struct CalComponent { - GtkObject object; - - /* Private data */ - CalComponentPrivate *priv; -}; -</STRUCT> -<FUNCTION> -<NAME>cal_component_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>cal_component_gen_uid</NAME> -<RETURNS>char *</RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>cal_component_new</NAME> -<RETURNS>CalComponent *</RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>cal_component_clone</NAME> -<RETURNS>CalComponent *</RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_new_vtype</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentVType type -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_icalcomponent</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp, icalcomponent *icalcomp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_icalcomponent</NAME> -<RETURNS>icalcomponent *</RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_vtype</NAME> -<RETURNS>CalComponentVType </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_as_string</NAME> -<RETURNS>char *</RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_commit_sequence</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_uid</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, const char **uid -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_uid</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, const char *uid -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_categories</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, const char **categories -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_categories</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, const char *categories -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_categories_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **categ_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_categories_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList *categ_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_classification</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentClassification *classif -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_classification</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentClassification classif -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_comment_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **text_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_comment_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList *text_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_completed</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype **t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_completed</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype *t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_created</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype **t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_created</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype *t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_description_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **text_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_description_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList *text_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_dtend</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentDateTime *dt -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_dtend</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentDateTime *dt -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_dtstamp</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype *t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_dtstamp</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype *t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_dtstart</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentDateTime *dt -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_dtstart</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentDateTime *dt -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_due</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentDateTime *dt -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_due</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentDateTime *dt -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_exdate_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **exdate_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_exdate_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList *exdate_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_has_exdates</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_exrule_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **recur_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_exrule_property_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **recur_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_exrule_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList *recur_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_has_exrules</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_has_exceptions</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_geo</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icalgeotype **geo -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_geo</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icalgeotype *geo -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_last_modified</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype **t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_last_modified</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, struct icaltimetype *t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_percent</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, int **percent -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_percent</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, int *percent -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_priority</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, int **priority -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_priority</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, int *priority -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_rdate_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **period_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_rdate_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList *period_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_has_rdates</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_rrule_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **recur_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_rrule_property_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList **recur_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_rrule_list</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, GSList *recur_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_has_rrules</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_has_recurrences</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_sequence</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, int **sequence -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_sequence</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, int *sequence -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_status</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, icalproperty_status *status -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_status</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, icalproperty_status status -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_summary</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentText *summary -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_summary</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentText *summary -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_transparency</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentTransparency *transp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_transparency</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentTransparency transp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_url</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, const char **url -</FUNCTION> -<FUNCTION> -<NAME>cal_component_set_url</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, const char *url -</FUNCTION> -<FUNCTION> -<NAME>cal_component_event_dates_match</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp1, CalComponent *comp2 -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_categories_list</NAME> -<RETURNS>void </RETURNS> -GSList *categ_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_datetime</NAME> -<RETURNS>void </RETURNS> -CalComponentDateTime *dt -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_exdate_list</NAME> -<RETURNS>void </RETURNS> -GSList *exdate_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_geo</NAME> -<RETURNS>void </RETURNS> -struct icalgeotype *geo -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_icaltimetype</NAME> -<RETURNS>void </RETURNS> -struct icaltimetype *t -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_percent</NAME> -<RETURNS>void </RETURNS> -int *percent -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_priority</NAME> -<RETURNS>void </RETURNS> -int *priority -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_period_list</NAME> -<RETURNS>void </RETURNS> -GSList *period_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_recur_list</NAME> -<RETURNS>void </RETURNS> -GSList *recur_list -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_sequence</NAME> -<RETURNS>void </RETURNS> -int *sequence -</FUNCTION> -<FUNCTION> -<NAME>cal_component_free_text_list</NAME> -<RETURNS>void </RETURNS> -GSList *text_list -</FUNCTION> -<STRUCT> -<NAME>CalComponentAlarm</NAME> -</STRUCT> -<TYPEDEF> -<NAME>CalAlarmInstance</NAME> -typedef struct { - /* UID of the alarm that triggered */ - const char *auid; - - /* Trigger time, i.e. "5 minutes before the appointment" */ - time_t trigger; - - /* Actual event occurrence to which this trigger corresponds */ - time_t occur; -} CalAlarmInstance; -</TYPEDEF> -<TYPEDEF> -<NAME>CalComponentAlarms</NAME> -typedef struct { - /* The actual component */ - CalComponent *comp; - - /* List of CalAlarmInstance structures */ - GSList *alarms; -} CalComponentAlarms; -</TYPEDEF> -<ENUM> -<NAME>CalAlarmAction</NAME> -typedef enum { - CAL_ALARM_NONE, - CAL_ALARM_AUDIO, - CAL_ALARM_DISPLAY, - CAL_ALARM_EMAIL, - CAL_ALARM_PROCEDURE, - CAL_ALARM_UNKNOWN -} CalAlarmAction; -</ENUM> -<ENUM> -<NAME>CalAlarmTriggerType</NAME> -typedef enum { - CAL_ALARM_TRIGGER_NONE, - CAL_ALARM_TRIGGER_RELATIVE_START, - CAL_ALARM_TRIGGER_RELATIVE_END, - CAL_ALARM_TRIGGER_ABSOLUTE -} CalAlarmTriggerType; -</ENUM> -<TYPEDEF> -<NAME>CalAlarmTrigger</NAME> -typedef struct { - CalAlarmTriggerType type; - - union { - struct icaldurationtype rel_duration; - struct icaltimetype abs_time; - } u; -} CalAlarmTrigger; -</TYPEDEF> -<FUNCTION> -<NAME>cal_component_has_alarms</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_add_alarm</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, CalComponentAlarm *alarm -</FUNCTION> -<FUNCTION> -<NAME>cal_component_remove_alarm</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp, const char *auid -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_alarm_uids</NAME> -<RETURNS>GList *</RETURNS> -CalComponent *comp -</FUNCTION> -<FUNCTION> -<NAME>cal_component_get_alarm</NAME> -<RETURNS>CalComponentAlarm *</RETURNS> -CalComponent *comp, const char *auid -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarms_free</NAME> -<RETURNS>void </RETURNS> -CalComponentAlarms *alarms -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarm_new</NAME> -<RETURNS>CalComponentAlarm *</RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarm_get_uid</NAME> -<RETURNS>const char *</RETURNS> -CalComponentAlarm *alarm -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarm_get_action</NAME> -<RETURNS>void </RETURNS> -CalComponentAlarm *alarm, CalAlarmAction *action -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarm_set_action</NAME> -<RETURNS>void </RETURNS> -CalComponentAlarm *alarm, CalAlarmAction action -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarm_get_trigger</NAME> -<RETURNS>void </RETURNS> -CalComponentAlarm *alarm, CalAlarmTrigger *trigger -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarm_set_trigger</NAME> -<RETURNS>void </RETURNS> -CalComponentAlarm *alarm, CalAlarmTrigger trigger -</FUNCTION> -<FUNCTION> -<NAME>cal_component_alarm_free</NAME> -<RETURNS>void </RETURNS> -CalComponentAlarm *alarm -</FUNCTION> -<USER_FUNCTION> -<NAME>CalRecurInstanceFn</NAME> -<RETURNS>gboolean </RETURNS> -CalComponent *comp, - time_t instance_start, - time_t instance_end, - gpointer data -</USER_FUNCTION> -<FUNCTION> -<NAME>cal_recur_generate_instances</NAME> -<RETURNS>void </RETURNS> -CalComponent *comp,time_t start,time_t end,CalRecurInstanceFn cb,gpointer cb_data -</FUNCTION> -<TYPEDEF> -<NAME>CalObjInstance</NAME> -typedef struct { - char *uid; /* UID of the object */ - time_t start; /* Start time of instance */ - time_t end; /* End time of instance */ -} CalObjInstance; -</TYPEDEF> -<FUNCTION> -<NAME>cal_obj_instance_list_free</NAME> -<RETURNS>void </RETURNS> -GList *list -</FUNCTION> -<ENUM> -<NAME>CalObjType</NAME> -typedef enum { - CALOBJ_TYPE_EVENT = 1 << 0, - CALOBJ_TYPE_TODO = 1 << 1, - CALOBJ_TYPE_JOURNAL = 1 << 2, - CALOBJ_TYPE_ANY = 0x07 -} CalObjType; -</ENUM> -<FUNCTION> -<NAME>cal_obj_uid_list_free</NAME> -<RETURNS>void </RETURNS> -GList *list -</FUNCTION> -<FUNCTION> -<NAME>isodate_from_time_t</NAME> -<RETURNS>char *</RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_add_minutes</NAME> -<RETURNS>time_t </RETURNS> -time_t time, int minutes -</FUNCTION> -<FUNCTION> -<NAME>time_add_day</NAME> -<RETURNS>time_t </RETURNS> -time_t time, int days -</FUNCTION> -<FUNCTION> -<NAME>time_add_week</NAME> -<RETURNS>time_t </RETURNS> -time_t time, int weeks -</FUNCTION> -<FUNCTION> -<NAME>time_add_month</NAME> -<RETURNS>time_t </RETURNS> -time_t time, int months -</FUNCTION> -<FUNCTION> -<NAME>time_add_year</NAME> -<RETURNS>time_t </RETURNS> -time_t time, int years -</FUNCTION> -<FUNCTION> -<NAME>time_days_in_month</NAME> -<RETURNS>int </RETURNS> -int year, int month -</FUNCTION> -<FUNCTION> -<NAME>time_from_day</NAME> -<RETURNS>time_t </RETURNS> -int year, int month, int day -</FUNCTION> -<FUNCTION> -<NAME>time_year_begin</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_year_end</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_month_begin</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_month_end</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_week_begin</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_week_end</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_day_begin</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>time_day_end</NAME> -<RETURNS>time_t </RETURNS> -time_t t -</FUNCTION> -<FUNCTION> -<NAME>print_time_t</NAME> -<RETURNS>void </RETURNS> -time_t t -</FUNCTION> diff --git a/help/devel/calendar/cal-util/evolution-cal-util-sections.txt b/help/devel/calendar/cal-util/evolution-cal-util-sections.txt deleted file mode 100644 index 1a03226591..0000000000 --- a/help/devel/calendar/cal-util/evolution-cal-util-sections.txt +++ /dev/null @@ -1,161 +0,0 @@ -<SECTION> -<FILE>cal-component</FILE> -CAL_COMPONENT -<TITLE>CalComponent</TITLE> - -CalComponentVType -CalComponentField -CalComponentClassification -CalComponentDateTime -CalComponentPeriodType -CalComponentPeriod -CalComponentText -CalComponentTransparency - -cal_component_gen_uid -cal_component_new -cal_component_clone -cal_component_set_new_vtype -cal_component_set_icalcomponent -cal_component_get_icalcomponent -cal_component_get_vtype -cal_component_get_as_string -cal_component_commit_sequence -cal_component_get_uid -cal_component_set_uid -cal_component_get_categories -cal_component_set_categories -cal_component_get_categories_list -cal_component_set_categories_list -cal_component_get_classification -cal_component_set_classification -cal_component_get_comment_list -cal_component_set_comment_list -cal_component_get_completed -cal_component_set_completed -cal_component_get_created -cal_component_set_created -cal_component_get_description_list -cal_component_set_description_list -cal_component_get_dtend -cal_component_set_dtend -cal_component_get_dtstamp -cal_component_set_dtstamp -cal_component_get_dtstart -cal_component_set_dtstart -cal_component_get_due -cal_component_set_due -cal_component_get_exdate_list -cal_component_set_exdate_list -cal_component_has_exdates -cal_component_get_exrule_list -cal_component_get_exrule_property_list -cal_component_set_exrule_list -cal_component_has_exrules -cal_component_has_exceptions -cal_component_get_geo -cal_component_set_geo -cal_component_get_last_modified -cal_component_set_last_modified -cal_component_get_percent -cal_component_set_percent -cal_component_get_priority -cal_component_set_priority -cal_component_get_rdate_list -cal_component_set_rdate_list -cal_component_has_rdates -cal_component_get_rrule_list -cal_component_get_rrule_property_list -cal_component_set_rrule_list -cal_component_has_rrules -cal_component_has_recurrences -cal_component_get_sequence -cal_component_set_sequence -cal_component_get_status -cal_component_set_status -cal_component_get_summary -cal_component_set_summary -cal_component_get_transparency -cal_component_set_transparency -cal_component_get_url -cal_component_set_url - -<SUBSECTION Functions to free returned values> -cal_component_free_categories_list -cal_component_free_datetime -cal_component_free_exdate_list -cal_component_free_geo -cal_component_free_icaltimetype -cal_component_free_percent -cal_component_free_priority -cal_component_free_period_list -cal_component_free_recur_list -cal_component_free_sequence -cal_component_free_text_list - -<SUBSECTION Alarms> -CalComponentAlarm -CalAlarmInstance -CalComponentAlarms -CalAlarmAction -CalAlarmTriggerType -CalAlarmTrigger - -cal_component_has_alarms -cal_component_get_alarm_uids -cal_component_get_alarm -cal_component_alarm_free -cal_component_alarms_free -cal_component_alarm_get_uid -cal_component_alarm_get_action -cal_component_alarm_set_action -cal_component_alarm_get_trigger -cal_component_alarm_set_trigger - -<SUBSECTION Standard> -CAL_COMPONENT_TYPE -CAL_COMPONENT_CLASS -IS_CAL_COMPONENT -IS_CAL_COMPONENT_CLASS -cal_component_get_type - -<SUBSECTION Private> -CalComponent -CalComponentPrivate - -</SECTION> - -<SECTION> -<FILE>cal-recur</FILE> -CalRecurInstanceFn -cal_recur_generate_instances -</SECTION> - -<SECTION> -<FILE>cal-util</FILE> -CalObjInstance -cal_obj_instance_list_free -CalObjType -cal_obj_uid_list_free -</SECTION> - -<SECTION> -<FILE>timeutil</FILE> -isodate_from_time_t -time_add_minutes -time_add_day -time_add_week -time_add_month -time_add_year -time_days_in_month -time_from_day -time_year_begin -time_year_end -time_month_begin -time_month_end -time_week_begin -time_week_end -time_day_begin -time_day_end -print_time_t -</SECTION> diff --git a/help/devel/calendar/cal-util/evolution-cal-util.args b/help/devel/calendar/cal-util/evolution-cal-util.args deleted file mode 100644 index e69de29bb2..0000000000 --- a/help/devel/calendar/cal-util/evolution-cal-util.args +++ /dev/null diff --git a/help/devel/calendar/cal-util/evolution-cal-util.hierarchy b/help/devel/calendar/cal-util/evolution-cal-util.hierarchy deleted file mode 100644 index cc235653f2..0000000000 --- a/help/devel/calendar/cal-util/evolution-cal-util.hierarchy +++ /dev/null @@ -1,2 +0,0 @@ -GtkObject - CalComponent diff --git a/help/devel/calendar/cal-util/evolution-cal-util.signals b/help/devel/calendar/cal-util/evolution-cal-util.signals deleted file mode 100644 index e69de29bb2..0000000000 --- a/help/devel/calendar/cal-util/evolution-cal-util.signals +++ /dev/null diff --git a/help/devel/calendar/cal-util/evolution-cal-util.types b/help/devel/calendar/cal-util/evolution-cal-util.types deleted file mode 100644 index 52b2d9bf90..0000000000 --- a/help/devel/calendar/cal-util/evolution-cal-util.types +++ /dev/null @@ -1,4 +0,0 @@ -#include <gnome.h> -#include <cal-util/cal-component.h> - -cal_component_get_type diff --git a/help/devel/calendar/cal-util/tmpl/cal-component.sgml b/help/devel/calendar/cal-util/tmpl/cal-component.sgml deleted file mode 100644 index 0cf6089d60..0000000000 --- a/help/devel/calendar/cal-util/tmpl/cal-component.sgml +++ /dev/null @@ -1,991 +0,0 @@ -<!-- ##### SECTION Title ##### --> -CalComponent - -<!-- ##### SECTION Short_Description ##### --> -RFC 2445 iCalendar component object. - -<!-- ##### SECTION Long_Description ##### --> - <para> - The #CalComponent object provides a wrapper over the &libical; - functions for manipulating calendar components. #CalComponent - presents a GTK+-like interface to calendar components according to - RFC 2445. - </para> - - <para> - While &libical; supports almost all of the features of the - iCalendar RFCs, applications are normally not interested in all - the mindless gunk that is there. Still, applications should do - their best not to drop extension fields from calendar components - or any other extra information they do not support (including - standard fields they are not interested in). The #CalComponent - object provides a wrapper over - <structname>icalcomponent</structname> structures from &libical; - so that no information in them will be lost even if the - application is not designed to handle it. Also, #CalComponent - provides a higher-level API to many of the &libical; operations so - as to make it less painful to deal with iCalendar components. - </para> - - <para> - A #CalComponent object starts out empty. It must be initialized - from an existing <structname>icalcomponent</structname> structure - by using the cal_component_set_icalcomponent() function, or from a - completely new data by specifying the desired component type to - the cal_component_set_new_vtype() function. - </para> - - <para> - #CalComponent will create an internal map of the properties in the - <structname>icalcomponent</structname> structure and then allow - random access to them via the #CalComponent API functions; - normally the &libical; API would have to be used by creating many - iterators and other unpleasant constructs. #CalComponent keeps - handles to the properties it scanned from the - <structname>icalcomponent</structname> and will let the parent - application modify them at any time without having to do any - iteration. - </para> - - <para> - Eventually a #CalComponent may be turned into the RFC 2445 string - representation of an iCalendar component by using the - cal_component_get_as_string() function. Applications can then - transfer this interoperable - <footnote> - <para> - “Interoperable.” Heavens, I love that word. - </para> - </footnote> - string to other programs that deal with iCalendar. - </para> - -<!-- ##### SECTION See_Also ##### --> - <para> - - </para> - -<!-- ##### MACRO CAL_COMPONENT ##### --> - <para> - Casts a #GtkObject to a #CalComponent. - </para> - -@obj: A GTK+ object. - - -<!-- ##### ENUM CalComponentVType ##### --> - <para> - Calendar component types as defined by RFC 2445. These values can - be used to create a new calendar component by passing them to the - cal_component_set_new_vtype() function. They are also the return - value of the cal_component_get_vtype() function. The only time - the @CAL_COMPONENT_NO_TYPE value is used is when querying the - vtype of an uninitialized #CalComponent. - </para> - -@CAL_COMPONENT_NO_TYPE: -@CAL_COMPONENT_EVENT: -@CAL_COMPONENT_TODO: -@CAL_COMPONENT_JOURNAL: -@CAL_COMPONENT_FREEBUSY: -@CAL_COMPONENT_TIMEZONE: - -<!-- ##### ENUM CalComponentField ##### --> - <para> - These values are used as identifiers for #ETable columns. These - are used by the calendar GUI code in &Evolution;. - </para> - -@CAL_COMPONENT_FIELD_CATEGORIES: -@CAL_COMPONENT_FIELD_CLASSIFICATION: -@CAL_COMPONENT_FIELD_COMPLETED: -@CAL_COMPONENT_FIELD_DTEND: -@CAL_COMPONENT_FIELD_DTSTART: -@CAL_COMPONENT_FIELD_DUE: -@CAL_COMPONENT_FIELD_GEO: -@CAL_COMPONENT_FIELD_PERCENT: -@CAL_COMPONENT_FIELD_PRIORITY: -@CAL_COMPONENT_FIELD_SUMMARY: -@CAL_COMPONENT_FIELD_TRANSPARENCY: -@CAL_COMPONENT_FIELD_URL: -@CAL_COMPONENT_FIELD_HAS_ALARMS: -@CAL_COMPONENT_FIELD_ICON: -@CAL_COMPONENT_FIELD_COMPLETE: -@CAL_COMPONENT_FIELD_RECURRING: -@CAL_COMPONENT_FIELD_OVERDUE: -@CAL_COMPONENT_FIELD_COLOR: -@CAL_COMPONENT_FIELD_NUM_FIELDS: - -<!-- ##### ENUM CalComponentClassification ##### --> - <para> - Values for the access classification property of a calendar - component. - </para> - -@CAL_COMPONENT_CLASS_NONE: -@CAL_COMPONENT_CLASS_PUBLIC: -@CAL_COMPONENT_CLASS_PRIVATE: -@CAL_COMPONENT_CLASS_CONFIDENTIAL: -@CAL_COMPONENT_CLASS_UNKNOWN: - -<!-- ##### TYPEDEF CalComponentDateTime ##### --> - <para> - This structure defines a date and time value. - </para> - - -<!-- ##### ENUM CalComponentPeriodType ##### --> - <para> - Defines how a period of time is specified. - </para> - -@CAL_COMPONENT_PERIOD_DATETIME: -@CAL_COMPONENT_PERIOD_DURATION: - -<!-- ##### TYPEDEF CalComponentPeriod ##### --> - <para> - This structure defines a period of time. - </para> - - -<!-- ##### TYPEDEF CalComponentText ##### --> - <para> - This structure defines the value of a text property that may have - an alternate representation parameter. - </para> - - -<!-- ##### ENUM CalComponentTransparency ##### --> -<para> - -</para> - -@CAL_COMPONENT_TRANSP_NONE: -@CAL_COMPONENT_TRANSP_TRANSPARENT: -@CAL_COMPONENT_TRANSP_OPAQUE: -@CAL_COMPONENT_TRANSP_UNKNOWN: - -<!-- ##### FUNCTION cal_component_gen_uid ##### --> -<para> - -</para> - -@Returns: - - -<!-- ##### FUNCTION cal_component_new ##### --> -<para> - -</para> - -@Returns: - - -<!-- ##### FUNCTION cal_component_clone ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_set_new_vtype ##### --> -<para> - -</para> - -@comp: -@type: - - -<!-- ##### FUNCTION cal_component_set_icalcomponent ##### --> -<para> - -</para> - -@comp: -@icalcomp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_icalcomponent ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_vtype ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_as_string ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_commit_sequence ##### --> -<para> - -</para> - -@comp: - - -<!-- ##### FUNCTION cal_component_get_uid ##### --> -<para> - -</para> - -@comp: -@uid: - - -<!-- ##### FUNCTION cal_component_set_uid ##### --> -<para> - -</para> - -@comp: -@uid: - - -<!-- ##### FUNCTION cal_component_get_categories ##### --> -<para> - -</para> - -@comp: -@categories: - - -<!-- ##### FUNCTION cal_component_set_categories ##### --> -<para> - -</para> - -@comp: -@categories: - - -<!-- ##### FUNCTION cal_component_get_categories_list ##### --> -<para> - -</para> - -@comp: -@categ_list: - - -<!-- ##### FUNCTION cal_component_set_categories_list ##### --> -<para> - -</para> - -@comp: -@categ_list: - - -<!-- ##### FUNCTION cal_component_get_classification ##### --> -<para> - -</para> - -@comp: -@classif: - - -<!-- ##### FUNCTION cal_component_set_classification ##### --> -<para> - -</para> - -@comp: -@classif: - - -<!-- ##### FUNCTION cal_component_get_comment_list ##### --> -<para> - -</para> - -@comp: -@text_list: - - -<!-- ##### FUNCTION cal_component_set_comment_list ##### --> -<para> - -</para> - -@comp: -@text_list: - - -<!-- ##### FUNCTION cal_component_get_completed ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_set_completed ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_get_created ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_set_created ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_get_description_list ##### --> -<para> - -</para> - -@comp: -@text_list: - - -<!-- ##### FUNCTION cal_component_set_description_list ##### --> -<para> - -</para> - -@comp: -@text_list: - - -<!-- ##### FUNCTION cal_component_get_dtend ##### --> -<para> - -</para> - -@comp: -@dt: - - -<!-- ##### FUNCTION cal_component_set_dtend ##### --> -<para> - -</para> - -@comp: -@dt: - - -<!-- ##### FUNCTION cal_component_get_dtstamp ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_set_dtstamp ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_get_dtstart ##### --> -<para> - -</para> - -@comp: -@dt: - - -<!-- ##### FUNCTION cal_component_set_dtstart ##### --> -<para> - -</para> - -@comp: -@dt: - - -<!-- ##### FUNCTION cal_component_get_due ##### --> -<para> - -</para> - -@comp: -@dt: - - -<!-- ##### FUNCTION cal_component_set_due ##### --> -<para> - -</para> - -@comp: -@dt: - - -<!-- ##### FUNCTION cal_component_get_exdate_list ##### --> -<para> - -</para> - -@comp: -@exdate_list: - - -<!-- ##### FUNCTION cal_component_set_exdate_list ##### --> -<para> - -</para> - -@comp: -@exdate_list: - - -<!-- ##### FUNCTION cal_component_has_exdates ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_exrule_list ##### --> -<para> - -</para> - -@comp: -@recur_list: - - -<!-- ##### FUNCTION cal_component_get_exrule_property_list ##### --> -<para> - -</para> - -@comp: -@recur_list: - - -<!-- ##### FUNCTION cal_component_set_exrule_list ##### --> -<para> - -</para> - -@comp: -@recur_list: - - -<!-- ##### FUNCTION cal_component_has_exrules ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_has_exceptions ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_geo ##### --> -<para> - -</para> - -@comp: -@geo: - - -<!-- ##### FUNCTION cal_component_set_geo ##### --> -<para> - -</para> - -@comp: -@geo: - - -<!-- ##### FUNCTION cal_component_get_last_modified ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_set_last_modified ##### --> -<para> - -</para> - -@comp: -@t: - - -<!-- ##### FUNCTION cal_component_get_percent ##### --> -<para> - -</para> - -@comp: -@percent: - - -<!-- ##### FUNCTION cal_component_set_percent ##### --> -<para> - -</para> - -@comp: -@percent: - - -<!-- ##### FUNCTION cal_component_get_priority ##### --> -<para> - -</para> - -@comp: -@priority: - - -<!-- ##### FUNCTION cal_component_set_priority ##### --> -<para> - -</para> - -@comp: -@priority: - - -<!-- ##### FUNCTION cal_component_get_rdate_list ##### --> -<para> - -</para> - -@comp: -@period_list: - - -<!-- ##### FUNCTION cal_component_set_rdate_list ##### --> -<para> - -</para> - -@comp: -@period_list: - - -<!-- ##### FUNCTION cal_component_has_rdates ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_rrule_list ##### --> -<para> - -</para> - -@comp: -@recur_list: - - -<!-- ##### FUNCTION cal_component_get_rrule_property_list ##### --> -<para> - -</para> - -@comp: -@recur_list: - - -<!-- ##### FUNCTION cal_component_set_rrule_list ##### --> -<para> - -</para> - -@comp: -@recur_list: - - -<!-- ##### FUNCTION cal_component_has_rrules ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_has_recurrences ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_sequence ##### --> -<para> - -</para> - -@comp: -@sequence: - - -<!-- ##### FUNCTION cal_component_set_sequence ##### --> -<para> - -</para> - -@comp: -@sequence: - - -<!-- ##### FUNCTION cal_component_get_status ##### --> -<para> - -</para> - -@comp: -@status: - - -<!-- ##### FUNCTION cal_component_set_status ##### --> -<para> - -</para> - -@comp: -@status: - - -<!-- ##### FUNCTION cal_component_get_summary ##### --> -<para> - -</para> - -@comp: -@summary: - - -<!-- ##### FUNCTION cal_component_set_summary ##### --> -<para> - -</para> - -@comp: -@summary: - - -<!-- ##### FUNCTION cal_component_get_transparency ##### --> -<para> - -</para> - -@comp: -@transp: - - -<!-- ##### FUNCTION cal_component_set_transparency ##### --> -<para> - -</para> - -@comp: -@transp: - - -<!-- ##### FUNCTION cal_component_get_url ##### --> -<para> - -</para> - -@comp: -@url: - - -<!-- ##### FUNCTION cal_component_set_url ##### --> -<para> - -</para> - -@comp: -@url: - - -<!-- ##### FUNCTION cal_component_free_categories_list ##### --> -<para> - -</para> - -@categ_list: - - -<!-- ##### FUNCTION cal_component_free_datetime ##### --> -<para> - -</para> - -@dt: - - -<!-- ##### FUNCTION cal_component_free_exdate_list ##### --> -<para> - -</para> - -@exdate_list: - - -<!-- ##### FUNCTION cal_component_free_geo ##### --> -<para> - -</para> - -@geo: - - -<!-- ##### FUNCTION cal_component_free_icaltimetype ##### --> -<para> - -</para> - -@t: - - -<!-- ##### FUNCTION cal_component_free_percent ##### --> -<para> - -</para> - -@percent: - - -<!-- ##### FUNCTION cal_component_free_priority ##### --> -<para> - -</para> - -@priority: - - -<!-- ##### FUNCTION cal_component_free_period_list ##### --> -<para> - -</para> - -@period_list: - - -<!-- ##### FUNCTION cal_component_free_recur_list ##### --> -<para> - -</para> - -@recur_list: - - -<!-- ##### FUNCTION cal_component_free_sequence ##### --> -<para> - -</para> - -@sequence: - - -<!-- ##### FUNCTION cal_component_free_text_list ##### --> -<para> - -</para> - -@text_list: - - -<!-- ##### STRUCT CalComponentAlarm ##### --> -<para> - -</para> - - -<!-- ##### TYPEDEF CalAlarmInstance ##### --> -<para> - -</para> - - -<!-- ##### TYPEDEF CalComponentAlarms ##### --> -<para> - -</para> - - -<!-- ##### ENUM CalAlarmAction ##### --> -<para> - -</para> - -@CAL_ALARM_NONE: -@CAL_ALARM_AUDIO: -@CAL_ALARM_DISPLAY: -@CAL_ALARM_EMAIL: -@CAL_ALARM_PROCEDURE: -@CAL_ALARM_UNKNOWN: - -<!-- ##### ENUM CalAlarmTriggerType ##### --> -<para> - -</para> - -@CAL_ALARM_TRIGGER_NONE: -@CAL_ALARM_TRIGGER_RELATIVE_START: -@CAL_ALARM_TRIGGER_RELATIVE_END: -@CAL_ALARM_TRIGGER_ABSOLUTE: - -<!-- ##### TYPEDEF CalAlarmTrigger ##### --> -<para> - -</para> - - -<!-- ##### FUNCTION cal_component_has_alarms ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_alarm_uids ##### --> -<para> - -</para> - -@comp: -@Returns: - - -<!-- ##### FUNCTION cal_component_get_alarm ##### --> -<para> - -</para> - -@comp: -@auid: -@Returns: - - -<!-- ##### FUNCTION cal_component_alarm_free ##### --> -<para> - -</para> - -@alarm: - - -<!-- ##### FUNCTION cal_component_alarms_free ##### --> -<para> - -</para> - -@alarms: - - -<!-- ##### FUNCTION cal_component_alarm_get_uid ##### --> -<para> - -</para> - -@alarm: -@Returns: - - -<!-- ##### FUNCTION cal_component_alarm_get_action ##### --> -<para> - -</para> - -@alarm: -@action: - - -<!-- ##### FUNCTION cal_component_alarm_set_action ##### --> -<para> - -</para> - -@alarm: -@action: - - -<!-- ##### FUNCTION cal_component_alarm_get_trigger ##### --> -<para> - -</para> - -@alarm: -@trigger: - - -<!-- ##### FUNCTION cal_component_alarm_set_trigger ##### --> -<para> - -</para> - -@alarm: -@trigger: - - diff --git a/help/devel/calendar/cal-util/tmpl/cal-recur.sgml b/help/devel/calendar/cal-util/tmpl/cal-recur.sgml deleted file mode 100644 index 092b547809..0000000000 --- a/help/devel/calendar/cal-util/tmpl/cal-recur.sgml +++ /dev/null @@ -1,42 +0,0 @@ -<!-- ##### SECTION Title ##### --> -cal-recur - -<!-- ##### SECTION Short_Description ##### --> - - -<!-- ##### SECTION Long_Description ##### --> -<para> - -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> - -</para> - -<!-- ##### USER_FUNCTION CalRecurInstanceFn ##### --> -<para> - -</para> - -@comp: -@instance_start: -@instance_end: -@data: -@Returns: -<!-- # Unused Parameters # --> -@instace_end: - - -<!-- ##### FUNCTION cal_recur_generate_instances ##### --> -<para> - -</para> - -@comp: -@start: -@end: -@cb: -@cb_data: - - diff --git a/help/devel/calendar/cal-util/tmpl/cal-util.sgml b/help/devel/calendar/cal-util/tmpl/cal-util.sgml deleted file mode 100644 index ccd35fac2e..0000000000 --- a/help/devel/calendar/cal-util/tmpl/cal-util.sgml +++ /dev/null @@ -1,48 +0,0 @@ -<!-- ##### SECTION Title ##### --> -Miscellaneous utilities - -<!-- ##### SECTION Short_Description ##### --> - - -<!-- ##### SECTION Long_Description ##### --> -<para> - -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> - -</para> - -<!-- ##### TYPEDEF CalObjInstance ##### --> -<para> - -</para> - - -<!-- ##### FUNCTION cal_obj_instance_list_free ##### --> -<para> - -</para> - -@list: - - -<!-- ##### ENUM CalObjType ##### --> -<para> - -</para> - -@CALOBJ_TYPE_EVENT: -@CALOBJ_TYPE_TODO: -@CALOBJ_TYPE_JOURNAL: -@CALOBJ_TYPE_ANY: - -<!-- ##### FUNCTION cal_obj_uid_list_free ##### --> -<para> - -</para> - -@list: - - diff --git a/help/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml b/help/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml deleted file mode 100644 index ff68fae99d..0000000000 --- a/help/devel/calendar/cal-util/tmpl/evolution-cal-util-unused.sgml +++ /dev/null @@ -1,228 +0,0 @@ -<!-- ##### ENUM CalComponentAlarmTriggerRelated ##### --> -<para> - -</para> - -@CAL_COMPONENT_ALARM_TRIGGER_RELATED_START: -@CAL_COMPONENT_ALARM_TRIGGER_RELATED_END: - -<!-- ##### FUNCTION cal_recur_free ##### --> -<para> - -</para> - -@r: - -<!-- ##### ENUM CalRecurType ##### --> -<para> - -</para> - -@CAL_RECUR_YEARLY: -@CAL_RECUR_MONTHLY: -@CAL_RECUR_WEEKLY: -@CAL_RECUR_DAILY: -@CAL_RECUR_HOURLY: -@CAL_RECUR_MINUTELY: -@CAL_RECUR_SECONDLY: - -<!-- ##### TYPEDEF CalComponentAlarmTrigger ##### --> -<para> - -</para> - - -<!-- ##### FUNCTION cal_component_get_pilot_id ##### --> -<para> - -</para> - -@comp: -@pilot_id: - -<!-- ##### FUNCTION get_time_t_hour ##### --> -<para> - -</para> - -@t: -@Returns: - -<!-- ##### FUNCTION cal_component_alarm_free_trigger ##### --> -<para> - -</para> - -@trigger: <!-- -Local variables: -mode: sgml -sgml-parent-document: ("../../../evolution-devel-guide.sgml" "book" "refsect2" "") -End: ---> - -<!-- ##### FUNCTION time_day_hour ##### --> -<para> - -</para> - -@t: -@hour: -@Returns: - -<!-- ##### FUNCTION time_from_isodate ##### --> -<para> - -</para> - -@str: -@Returns: - -<!-- ##### FUNCTION cal_component_get_pilot_status ##### --> -<para> - -</para> - -@comp: -@pilot_status: - -<!-- ##### STRUCT CalObjTime ##### --> -<para> - -</para> - -@year: -@month: -@day: -@hour: -@minute: -@second: - -<!-- ##### STRUCT CalComponentPrivate ##### --> -<para> - -</para> - - -<!-- ##### ENUM CalComponentAlarmTriggerType ##### --> -<para> - -</para> - -@CAL_COMPONENT_ALARM_TRIGGER_RELATIVE: -@CAL_COMPONENT_ALARM_TRIGGER_ABSOLUTE: - -<!-- ##### FUNCTION cal_recur_from_icalrecurrencetype ##### --> -<para> - -</para> - -@ir: -@Returns: - -<!-- ##### FUNCTION cal_alarm_instance_list_free ##### --> -<para> - -</para> - -@list: - -<!-- ##### FUNCTION isodiff_to_secs ##### --> -<para> - -</para> - -@str: -@Returns: - -<!-- ##### FUNCTION cal_component_get_first_alarm ##### --> -<para> - -</para> - -@comp: -@Returns: - -<!-- ##### TYPEDEF CalRecurrence ##### --> -<para> - -</para> - - -<!-- ##### FUNCTION cal_component_get_next_alarm ##### --> -<para> - -</para> - -@comp: -@Returns: - -<!-- ##### FUNCTION time_from_icaltimetype ##### --> -<para> - -</para> - -@itt: -@Returns: - -<!-- ##### ENUM CalComponentAlarmAction ##### --> -<para> - -</para> - -@CAL_COMPONENT_ALARM_NONE: -@CAL_COMPONENT_ALARM_AUDIO: -@CAL_COMPONENT_ALARM_DISPLAY: -@CAL_COMPONENT_ALARM_EMAIL: -@CAL_COMPONENT_ALARM_PROCEDURE: -@CAL_COMPONENT_ALARM_UNKNOWN: - -<!-- ##### FUNCTION time_from_start_duration ##### --> -<para> - -</para> - -@start: -@duration: -@Returns: - -<!-- ##### FUNCTION cal_component_set_pilot_id ##### --> -<para> - -</para> - -@comp: -@pilot_id: - -<!-- ##### FUNCTION isodiff_from_secs ##### --> -<para> - -</para> - -@secs: -@Returns: - -<!-- ##### FUNCTION format_simple_hour ##### --> -<para> - -</para> - -@hour: -@use_am_pm: -@Returns: - -<!-- ##### FUNCTION cal_component_set_pilot_status ##### --> -<para> - -</para> - -@comp: -@pilot_status: - -<!-- ##### FUNCTION parse_date ##### --> -<para> - -</para> - -@str: -@Returns: - diff --git a/help/devel/calendar/cal-util/tmpl/timeutil.sgml b/help/devel/calendar/cal-util/tmpl/timeutil.sgml deleted file mode 100644 index 2b197ad685..0000000000 --- a/help/devel/calendar/cal-util/tmpl/timeutil.sgml +++ /dev/null @@ -1,176 +0,0 @@ -<!-- ##### SECTION Title ##### --> -timeutil - -<!-- ##### SECTION Short_Description ##### --> - - -<!-- ##### SECTION Long_Description ##### --> -<para> - -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> - -</para> - -<!-- ##### FUNCTION isodate_from_time_t ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_add_minutes ##### --> -<para> - -</para> - -@time: -@minutes: -@Returns: - - -<!-- ##### FUNCTION time_add_day ##### --> -<para> - -</para> - -@time: -@days: -@Returns: - - -<!-- ##### FUNCTION time_add_week ##### --> -<para> - -</para> - -@time: -@weeks: -@Returns: - - -<!-- ##### FUNCTION time_add_month ##### --> -<para> - -</para> - -@time: -@months: -@Returns: - - -<!-- ##### FUNCTION time_add_year ##### --> -<para> - -</para> - -@time: -@years: -@Returns: - - -<!-- ##### FUNCTION time_days_in_month ##### --> -<para> - -</para> - -@year: -@month: -@Returns: - - -<!-- ##### FUNCTION time_from_day ##### --> -<para> - -</para> - -@year: -@month: -@day: -@Returns: - - -<!-- ##### FUNCTION time_year_begin ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_year_end ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_month_begin ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_month_end ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_week_begin ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_week_end ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_day_begin ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION time_day_end ##### --> -<para> - -</para> - -@t: -@Returns: - - -<!-- ##### FUNCTION print_time_t ##### --> -<para> - -</para> - -@t: - - diff --git a/help/devel/calendar/evolution-calendar.sgml b/help/devel/calendar/evolution-calendar.sgml deleted file mode 100644 index ea0d8c7127..0000000000 --- a/help/devel/calendar/evolution-calendar.sgml +++ /dev/null @@ -1,52 +0,0 @@ - <part id="evolution-calendar"> - <docinfo> - <authorgroup> - <author> - <firstname>Federico</firstname> - <surname>Mena Quintero</surname> - <affiliation> - <address> - <email>federico@ximian.com</email> - </address> - </affiliation> - </author> - </authorgroup> - </docinfo> - - <title>Developing Applications with the &Evolution; Calendar</title> - - <partintro> - <para> - This part of the &Evolution; Developer's Guide describes how - to write applications for the &Evolution; Calendar by using - its public interfaces. The &Evolution; Calendar exports its - functionality through a number of interfaces, including CORBA, - GTK+ wrappers for Bonobo objects, and other utility libraries. - This part also describes the internals of the calendar so that - it will be easy for you to make changes to &Evolution;'s core - code. - </para> - - <para> - You should read this part of the &Evolution; Developer's guide - if you intend to write client applications that use the - functionality of the &Evolution; Calendar, such as its storage - interfaces and generic recurrence engine. If you intend to - make changes to the calendar's core code, it will be useful to - read the sections on the calendar internals as well. Even if - you do not intend to modify the core code of the calendar, it - may be useful to know a few things about the way it works so - that you can make better use of the public interfaces. - </para> - </partintro> - - &calendar-architecture; - &calendar-alarm-generation; - </part> - -<!-- -Local variables: -mode: sgml -sgml-parent-document: ("../evolution-devel-guide.sgml" "book" "book" "") -End: ---> diff --git a/help/devel/calendar/public-reference.sgml b/help/devel/calendar/public-reference.sgml deleted file mode 100644 index b880bd2972..0000000000 --- a/help/devel/calendar/public-reference.sgml +++ /dev/null @@ -1,24 +0,0 @@ - <reference id="calendar-public-reference"> - <title>Calendar Public API Reference</title> - - <partintro> - <para> - This part presents the class and function reference for the - public APIs of the different components of the &Evolution; - Calendar. - </para> - </partintro> - - &CalClient; - &CalComponent; - &cal-util; - &cal-recur; - &timeutil; - </reference> - -<!-- -Local variables: -mode: sgml -sgml-parent-document: ("../evolution-devel-guide.sgml" "book" "part" "") -End: ---> diff --git a/help/devel/evolution-devel-guide.sgml b/help/devel/evolution-devel-guide.sgml deleted file mode 100644 index 4a88261da4..0000000000 --- a/help/devel/evolution-devel-guide.sgml +++ /dev/null @@ -1,97 +0,0 @@ -<!DOCTYPE book PUBLIC "-//Davenport//DTD DocBook V3.0//EN"[ -<!ENTITY preface SYSTEM "preface.sgml"> -<!ENTITY evolution-reference SYSTEM "reference.sgml"> -<!ENTITY FDL SYSTEM "fdl.sgml"> - -<!ENTITY evolution-calendar SYSTEM "calendar/evolution-calendar.sgml"> -<!ENTITY calendar-architecture SYSTEM "calendar/architecture.sgml"> -<!ENTITY calendar-alarm-generation SYSTEM "calendar/alarm-generation.sgml"> -<!ENTITY calendar-public-reference SYSTEM "calendar/public-reference.sgml"> -<!ENTITY CalClient SYSTEM "calendar/cal-client/sgml/cal-client.sgml"> -<!ENTITY CalComponent SYSTEM "calendar/cal-util/sgml/cal-component.sgml"> -<!ENTITY cal-recur SYSTEM "calendar/cal-util/sgml/cal-recur.sgml"> -<!ENTITY cal-util SYSTEM "calendar/cal-util/sgml/cal-util.sgml"> -<!ENTITY timeutil SYSTEM "calendar/cal-util/sgml/timeutil.sgml"> - -<!ENTITY importer-public-reference SYSTEM "importer/public-reference.sgml"> -<!ENTITY importer-private-reference SYSTEM "importer/private-reference.sgml"> -<!ENTITY EvolutionImporter SYSTEM "importer/sgml/evolution-importer.sgml"> -<!ENTITY EvolutionImporterClient SYSTEM "importer/sgml/evolution-importer-client.sgml"> -<!ENTITY EvolutionImporterListener SYSTEM "importer/sgml/evolution-importer-listener.sgml"> - -<!ENTITY evolution-services-public-reference SYSTEM "executive-summary/public-reference.sgml"> -<!ENTITY evolution-services-private-reference SYSTEM "executive-summary/private-reference.sgml"> -<!ENTITY ExecutiveSummaryComponent SYSTEM "executive-summary/sgml/executive-summary-component.sgml"> -<!ENTITY ExecutiveSummaryComponentFactory SYSTEM "executive-summary/sgml/executive-summary-component-factory.sgml"> -<!ENTITY ExecutiveSummaryComponentFactoryClient SYSTEM "executive-summary/sgml/executive-summary-component-factory-client.sgml"> -<!ENTITY ExecutiveSummaryHtmlView SYSTEM "executive-summary/sgml/executive-summary-html-view.sgml"> - -<!ENTITY Evolution "<application>Evolution</application>"> -<!ENTITY Wombat "<application>Wombat</application>"> -<!ENTITY Camel "<application>Camel</application>"> -<!ENTITY PCS "<acronym>PCS</acronym>"> -<!ENTITY libical "<application>libical</application>"> -<!ENTITY Executive-Summary "<application>Executive Summary</application>"> -]> - -<book id="index"> - <bookinfo> - <title>&Evolution; Developer's Guide</title> - - <authorgroup> - <corpauthor> - Ximian, Inc. - </corpauthor> - </authorgroup> - - <copyright> - <year>2000</year> - <holder>Helix Code, Inc.</holder> - </copyright> - - <copyright> - <year>2001</year> - <holder>Ximian, Inc.</holder> - </copyright> - - <legalnotice id="legalnotice"> - <para> - Permission is granted to copy, distribute and/or modify this - document under the terms of the <ulink type="help" - url="gnome-help:fdl"><citetitle>GNU Free Documentation - License</citetitle></ulink>, Version 1.1 or any later version - published by the Free Software Foundation with no Invariant - Sections, no Front-Cover Texts, and no Back-Cover Texts. You - may obtain a copy of the <citetitle>GNU Free Documentation - License</citetitle> from the Free Software Foundation by - visiting <ulink type="http" url="http://www.fsf.org">their Web - site</ulink> or by writing to: Free Software Foundation, Inc., - 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. - </para> - - <para> - Many of the names used by companies to distinguish their - products and services are claimed as trademarks. Where those - names appear in any GNOME documentation, and those trademarks - are made aware to the members of the GNOME Documentation - Project, the names have been printed in caps or initial caps. - </para> - </legalnotice> - </bookinfo> - - <!-- Introduction --> - - &preface; - - <!-- DocBook parts for each individual component --> - - &evolution-calendar; - - <!-- API Reference part --> - - &evolution-reference; - - <!-- Appendices --> - - &FDL; -</book> diff --git a/help/devel/executive-summary/Makefile.am b/help/devel/executive-summary/Makefile.am deleted file mode 100644 index 9aa53af4ec..0000000000 --- a/help/devel/executive-summary/Makefile.am +++ /dev/null @@ -1,125 +0,0 @@ -# The name of the module. -DOC_MODULE=evolution-services - -# The directory containing the source code -DOC_SOURCE_DIR=$(EVOLUTION_DIR)/executive-summary/evolution-services - -CFLAGS =" \ - -I$(top_srcdir)/executive-summary/evolution-services \ - -I$(top_srcdir)/executive-summary \ - -I$(top_srcdir) \ - -I$(top_builddir) \ - $(BONOBO_VFS_GNOME_CFLAGS) \ - " - -LDFLAGS=" \ - $(BONOBO_VFS_GNOME_LIBS) \ - $(top_builddir)/executive-summary/evolution-services/.libs/libevolution-services.a \ - " - -DOC_DIR=$(datadir)/gnome/html - -DOC_DIR_INSTALL_FILES = \ - evolution-services.args \ - evolution-services.hierarchy \ - evolution-services.signals \ - evolution-services.types \ - evolution-services-decl.txt \ - evolution-services-sections.txt - -SOURCE_FILES = \ - $(top_srcdir)/executive-summary/evolution-services/executive-summary-component.c \ - $(top_srcdir)/executive-summary/evolution-services/executive-summary-component-factory-client.c \ - $(top_srcdir)/executive-summary/evolution-services/executive-summary-html-view.c - -IGNORED_HEADER_FILES = \ - Executive-Summary.h - -scan_generated = \ - evolution-services-decl.txt \ - evolution-services.args \ - evolution-services.hierarchy \ - evolution-services.signals \ - evolution-services.types - -tmpl_dependencies = \ - evolution-services-decl.txt \ - evolution-services-sections.txt \ - evolution-services.args \ - evolution-services.hierarchy \ - evolution-services.signals - -tmpl_sources = \ - tmpl/evolution-services.sgml \ - tmpl/evolution-services-unused.sgml - -tmpl_generated = \ - evolution-services-unused.txt - -sgml_dependencies = \ - evolution-services-decl.txt \ - evolution-services-sections.txt \ - evolution-services.args \ - evolution-services.hierarchy \ - evolution-services.signals \ - tmpl/evolution-services.sgml - -sgml_generated = \ - sgml/evolution-services.sgml \ - sgml/evolution-services-doc.bottom \ - sgml/evolution-services-doc.top \ - sgml/object_index.sgml \ - sgml/tree_index.sgml - -EXTRA_DIST = \ - evolution-services.args \ - evolution-services.hierarchy \ - evolution-services.signals \ - evolution-services.types \ - evolution-services-decl.txt \ - evolution-services-sections.txt - -all: $(sgml_generated) - -if ENABLE_GTK_DOC -scan $(scan_generated): $(SOURCE_FILES) - -(cd $(srcdir) \ - && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS) \ - gtkdoc-scanobj --module=$(DOC_MODULE) \ - && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) \ - --ignore-headers="$(IGNORED_HEADER_FILES)" ) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE) - -sgml $(sgml_generated): $(sgml_dependencies) - cd $(srcdir) \ - && gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) -else -scan $(scan_generated): $(SOURCE_FILE) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - -sgml $(sgml_generated): $(sgml_dependencies) -endif - -clean-local: - rm -f *~ *.bak *.signals *-unused.txt - -maintainer-clean-local: clean - cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt - -install-data-local: - $(mkinstalldirs) $(DOC_DIR) - for i in $(DOC_DIR_INSTALL_FILES); do \ - $(INSTALL_DATA) $$i $(DOC_DIR); \ - done - -dist-hook: - mkdir $(distdir)/sgml - mkdir $(distdir)/tmpl - -cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl - -cp $(srcdir)/sgml/*.sgml $(distdir)/sgml - -cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml - -.PHONY: scan templates sgml diff --git a/help/devel/executive-summary/evolution-services-decl.txt b/help/devel/executive-summary/evolution-services-decl.txt deleted file mode 100644 index df84080700..0000000000 --- a/help/devel/executive-summary/evolution-services-decl.txt +++ /dev/null @@ -1,599 +0,0 @@ -<MACRO> -<NAME>EXECUTIVE_SUMMARY_CLIENT_TYPE</NAME> -#define EXECUTIVE_SUMMARY_CLIENT_TYPE (executive_summary_client_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_CLIENT</NAME> -#define EXECUTIVE_SUMMARY_CLIENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_CLIENT_TYPE, ExecutiveSummaryClient)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_CLIENT_CLASS</NAME> -#define EXECUTIVE_SUMMARY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_CLIENT_TYPE, ExecutiveSummaryClientClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_CLIENT</NAME> -#define IS_EXECUTIVE_SUMMARY_CLIENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_CLIENT_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_CLIENT_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_CLIENT_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryClientPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryClient</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryClientClass</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryClient</NAME> -struct ExecutiveSummaryClient { - BonoboObjectClient parent; - - ExecutiveSummaryClientPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryClientClass</NAME> -struct ExecutiveSummaryClientClass { - BonoboObjectClientClass parent_class; -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_client_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_client_construct</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryClient *client,CORBA_Object object -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_client_set_title</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryClient *client,int id,const char *title -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_client_set_icon</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryClient *client,int id,const char *icon -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_client_flash</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryClient *client,int id -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_client_update</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryClient *client,int id,const char *html -</FUNCTION> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE (executive_summary_component_factory_client_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE, ExecutiveSummaryComponentFactoryClient)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE, ExecutiveSummaryComponentFactoryClientClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryClientPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryClient</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryClientClass</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryClient</NAME> -struct ExecutiveSummaryComponentFactoryClient { - BonoboObjectClient parent; - - ExecutiveSummaryComponentFactoryClientPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryClientClass</NAME> -struct ExecutiveSummaryComponentFactoryClientClass { - BonoboObjectClientClass parent_class; -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_component_factory_client_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_factory_client_construct</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentFactoryClient *client,CORBA_Object corba_object -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_factory_client_new</NAME> -<RETURNS>ExecutiveSummaryComponentFactoryClient *</RETURNS> -const char *id -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_factory_client_create_view</NAME> -<RETURNS>CORBA_Object </RETURNS> -ExecutiveSummaryComponentFactoryClient *client -</FUNCTION> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_TYPE</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_TYPE (executive_summary_component_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_TYPE, ExecutiveSummaryComponent)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_CLASS</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_TYPE, ExecutiveSummaryComponentClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryComponentPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponent</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentClass</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponent</NAME> -struct ExecutiveSummaryComponent { - BonoboObject parent; - - ExecutiveSummaryComponentPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentClass</NAME> -struct ExecutiveSummaryComponentClass { - BonoboObjectClass parent_class; -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_component_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_new</NAME> -<RETURNS>BonoboObject *</RETURNS> -void -</FUNCTION> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE (executive_summary_component_factory_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_FACTORY</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE, ExecutiveSummaryComponentFactory)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE, ExecutiveSummaryComponentFactoryClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactory</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryClass</NAME> -</STRUCT> -<USER_FUNCTION> -<NAME>EvolutionServicesCreateViewFn</NAME> -<RETURNS>BonoboObject *</RETURNS> -ExecutiveSummaryComponentFactory *factory, - void *closure -</USER_FUNCTION> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactory</NAME> -struct ExecutiveSummaryComponentFactory { - BonoboObject parent; - - ExecutiveSummaryComponentFactoryPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentFactoryClass</NAME> -struct ExecutiveSummaryComponentFactoryClass { - BonoboObjectClass parent_class; -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_component_factory_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_factory_new</NAME> -<RETURNS>BonoboObject *</RETURNS> -EvolutionServicesCreateViewFn create_view,void *closure -</FUNCTION> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_HTML_VIEW_HTML_CHANGED</NAME> -#define EXECUTIVE_SUMMARY_HTML_VIEW_HTML_CHANGED "GNOME:Evolution:Summary:HTMLView:html_changed" -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_HTML_VIEW_TYPE</NAME> -#define EXECUTIVE_SUMMARY_HTML_VIEW_TYPE (executive_summary_html_view_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_HTML_VIEW</NAME> -#define EXECUTIVE_SUMMARY_HTML_VIEW(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE, ExecutiveSummaryHtmlView)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_HTML_VIEW_CLASS</NAME> -#define EXECUTIVE_SUMMARY_HTML_VIEW_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE, ExecutiveSummaryHtmlViewClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_HTML_VIEW</NAME> -#define IS_EXECUTIVE_SUMMARY_HTML_VIEW(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_HTML_VIEW_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_HTML_VIEW_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_HTML_VIEW_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryHtmlViewPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryHtmlView</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryHtmlViewClass</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryHtmlView</NAME> -struct ExecutiveSummaryHtmlView { - BonoboObject parent; - - ExecutiveSummaryHtmlViewPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryHtmlViewClass</NAME> -struct ExecutiveSummaryHtmlViewClass { - BonoboObjectClass parent_class; -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_html_view_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_html_view_new_full</NAME> -<RETURNS>BonoboObject *</RETURNS> -BonoboEventSource *event_source -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_html_view_new</NAME> -<RETURNS>BonoboObject *</RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_html_view_set_html</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryHtmlView *view,const char *html -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_html_view_get_html</NAME> -<RETURNS>const char *</RETURNS> -ExecutiveSummaryHtmlView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_html_view_get_event_source</NAME> -<RETURNS>BonoboEventSource *</RETURNS> -ExecutiveSummaryHtmlView *view -</FUNCTION> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE (executive_summary_component_client_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_CLIENT</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_CLIENT(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE, ExecutiveSummaryComponentClient)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE, ExecutiveSummaryComponentClientClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_CLIENT_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_CLIENT_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryComponentClientPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentClient</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentClientClass</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentClient</NAME> -struct ExecutiveSummaryComponentClient { - BonoboObjectClient parent; - - ExecutiveSummaryComponentClientPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentClientClass</NAME> -struct ExecutiveSummaryComponentClientClass { - BonoboObjectClientClass parent_class; -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_component_client_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_client_new</NAME> -<RETURNS>ExecutiveSummaryComponentClient *</RETURNS> -const char *id -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_client_set_owner</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentClient *client,ExecutiveSummary *summary -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_client_unset_owner</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentClient *client -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_client_supports</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentClient *client,gboolean *bonobo,gboolean *html -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_client_configure</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentClient *client,ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_client_destroy_view</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentClient *client,ExecutiveSummaryComponentView *view -</FUNCTION> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_TYPE</NAME> -#define EXECUTIVE_SUMMARY_TYPE (executive_summary_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY</NAME> -#define EXECUTIVE_SUMMARY(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_TYPE, ExecutiveSummary)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_CLASS</NAME> -#define EXECUTIVE_SUMMARY_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_TYPE, ExecutiveSummaryClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY</NAME> -#define IS_EXECUTIVE_SUMMARY(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummary</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryClass</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummary</NAME> -struct ExecutiveSummary { - BonoboObject parent; - - ExecutiveSummaryPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryClass</NAME> -struct ExecutiveSummaryClass { - BonoboObjectClass parent_class; - - void (* update) (ExecutiveSummary *summary, - const GNOME_Evolution_Summary_Component component, - const char *html); - void (* set_title) (ExecutiveSummary *summary, - const GNOME_Evolution_Summary_Component component, - const char *title); - void (* set_icon) (ExecutiveSummary *summary, - const GNOME_Evolution_Summary_Component component, - const char *icon); - void (* flash) (ExecutiveSummary *summary, - const GNOME_Evolution_Summary_Component component); -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_construct</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummary *es,GNOME_Evolution_Summary_ViewFrame corba_object -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_new</NAME> -<RETURNS>BonoboObject *</RETURNS> -void -</FUNCTION> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE (executive_summary_component_view_get_type ()) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_VIEW</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_VIEW(obj) (GTK_CHECK_CAST ((obj), EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE, ExecutiveSummaryComponentView)) -</MACRO> -<MACRO> -<NAME>EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS</NAME> -#define EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS(klass) (GTK_CHECK_CLASS_CAST ((klass), EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE, ExecutiveSummaryComponentClass)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW(obj) (GTK_CHECK_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_VIEW_TYPE)) -</MACRO> -<MACRO> -<NAME>IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS</NAME> -#define IS_EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS(klass) (GTK_CHECK_CLASS_TYPE ((obj), EXECUTIVE_SUMMARY_COMPONENT_VIEW_CLASS_TYPE)) -</MACRO> -<STRUCT> -<NAME>ExecutiveSummaryComponentViewPrivate</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentView</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentViewClass</NAME> -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentView</NAME> -struct ExecutiveSummaryComponentView { - GtkObject object; - - ExecutiveSummaryComponentViewPrivate *private; -}; -</STRUCT> -<STRUCT> -<NAME>ExecutiveSummaryComponentViewClass</NAME> -struct ExecutiveSummaryComponentViewClass { - GtkObjectClass parent_class; - - /* Signals */ - void (* configure) (ExecutiveSummaryComponentView *view); -}; -</STRUCT> -<FUNCTION> -<NAME>executive_summary_component_view_get_type</NAME> -<RETURNS>GtkType </RETURNS> -void -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_construct</NAME> -<RETURNS>void</RETURNS> -ExecutiveSummaryComponentView *view,ExecutiveSummaryComponent *component,BonoboControl *control,const char *html,const char *title,const char *icon -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_new</NAME> -<RETURNS>ExecutiveSummaryComponentView *</RETURNS> -ExecutiveSummaryComponent *component,BonoboControl *control,const char *html,const char *title,const char *icon -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_set_title</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentView *view,const char *title -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_get_title</NAME> -<RETURNS>const char *</RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_set_icon</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentView *view,const char *icon -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_get_icon</NAME> -<RETURNS>const char *</RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_flash</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_set_html</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentView *view,const char *html -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_get_html</NAME> -<RETURNS>const char *</RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_get_control</NAME> -<RETURNS>BonoboObject *</RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_get_id</NAME> -<RETURNS>int </RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_set_id</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentView *view,int id -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_configure</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_set_objref</NAME> -<RETURNS>void </RETURNS> -ExecutiveSummaryComponentView *view,Bonobo_Control objref -</FUNCTION> -<FUNCTION> -<NAME>executive_summary_component_view_get_widget</NAME> -<RETURNS>GtkWidget *</RETURNS> -ExecutiveSummaryComponentView *view -</FUNCTION> diff --git a/help/devel/executive-summary/evolution-services-sections.txt b/help/devel/executive-summary/evolution-services-sections.txt deleted file mode 100644 index 8ba2b42317..0000000000 --- a/help/devel/executive-summary/evolution-services-sections.txt +++ /dev/null @@ -1,95 +0,0 @@ -<INCLUDE>executive-summary-component.h</INCLUDE> -<SECTION> -<FILE>executive-summary-component</FILE> -EXECUTIVE_SUMMARY_COMPONENT -<TITLE>ExecutiveSummaryComponent</TITLE> - -executive_summary_component_new - -<SUBSECTION Standard> -EXECUTIVE_SUMMARY_COMPONENT_TYPE -EXECUTIVE_SUMMARY_COMPONENT -EXECUTIVE_SUMMARY_COMPONENT_CLASS -IS_EXECUTIVE_SUMMARY_COMPONENT -IS_EXECUTIVE_SUMMARY_COMPONENT_CLASS -executive_summary_component_get_type - -<SUBSECTION Private> -ExecutiveSummaryComponent -ExecutiveSummaryComponentPrivate - -</SECTION> - -<SECTION> -<FILE>executive-summary-component-factory</FILE> -EXECUTIVE_SUMMARY_COMPONENT_FACTORY -<TITLE>ExecutiveSummaryComponentFactory</TITLE> - -EvolutionServicesCreateViewFn - -executive_summary_component_factory_new - -<SUBSECTION Standard> -EXECUTIVE_SUMMARY_COMPONENT_FACTORY_TYPE -EXECUTIVE_SUMMARY_COMPONENT_FACTORY -EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS -IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY -IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLASS -executive_summary_component_factory_get_type - -<SUBSECTION Private> -ExecutiveSummaryComponentFactory -ExecutiveSummaryComponentFactoryPrivate - -</SECTION> - -<INCLUDE>executive-summary-component-factory-client.h</INCLUDE> -<SECTION> -<FILE>executive-summary-component-factory-client</FILE> -EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT -<TITLE>ExecutiveSummaryComponentFactoryClient</TITLE> - -executive_summary_component_factory_client_construct -executive_summary_component_factory_client_new -executive_summary_component_factory_client_create_view - -<SUBSECTION Standard> -EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_TYPE -EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT -EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS -IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT -IS_EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT_CLASS -executive_summary_component_factory_client_get_type - -<SUBSECTION Private> -ExecutiveSummaryComponentFactoryClient -ExecutiveSummaryComponentFactoryClientPrivate - -</SECTION> - -<INCLUDE>executive-summary-html-view.h</INCLUDE> -<SECTION> -<FILE>executive-summary-html-view</FILE> -EXECUTIVE_SUMMARY_HTML_VIEW -<TITLE>ExecutiveSummaryHtmlView</TITLE> - -EXECUTIVE_SUMMARY_HTML_VIEW_HTML_CHANGED - -executive_summary_html_view_new_full -executive_summary_html_view_new -executive_summary_html_view_set_html -executive_summary_html_view_get_html -executive_summary_html_view_get_event_source - -<SUBSECTION Standard> -EXECUTIVE_SUMMARY_HTML_VIEW_TYPE -EXECUTIVE_SUMMARY_HTML_VIEW -IS_EXECUTIVE_SUMMARY_HTML_VIEW -EXECUTIVE_SUMMARY_HTML_VIEW_CLASS -IS_EXECUTIVE_SUMMARY_HTML_VIEW_CLASS -executive_summary_html_view_get_type - -<SUBSECTION Private> -ExecutiveSummaryHtmlView -ExecutiveSummaryHtmlViewPrivate -</SECTION> diff --git a/help/devel/executive-summary/evolution-services.args b/help/devel/executive-summary/evolution-services.args deleted file mode 100644 index e69de29bb2..0000000000 --- a/help/devel/executive-summary/evolution-services.args +++ /dev/null diff --git a/help/devel/executive-summary/evolution-services.hierarchy b/help/devel/executive-summary/evolution-services.hierarchy deleted file mode 100644 index 07e7aad6ff..0000000000 --- a/help/devel/executive-summary/evolution-services.hierarchy +++ /dev/null @@ -1,15 +0,0 @@ -GtkObject - GtkWidget - GtkRange - GtkScale - GtkContainer - GtkBin - GtkButton - GtkToggleButton - GtkCheckButton - BonoboObject - ExecutiveSummaryComponent - ExecutiveSummaryComponentFactory - Handle to remote Bonobo::Unknown - ExecutiveSummaryComponentFactoryClient - ExecutiveSummaryHtmlView diff --git a/help/devel/executive-summary/evolution-services.signals b/help/devel/executive-summary/evolution-services.signals deleted file mode 100644 index e69de29bb2..0000000000 --- a/help/devel/executive-summary/evolution-services.signals +++ /dev/null diff --git a/help/devel/executive-summary/evolution-services.types b/help/devel/executive-summary/evolution-services.types deleted file mode 100644 index b7ac05b89c..0000000000 --- a/help/devel/executive-summary/evolution-services.types +++ /dev/null @@ -1,10 +0,0 @@ -#include <gnome.h> -#include <bonobo.h> -#include <evolution-services/executive-summary-component.h> -#include <evolution-services/executive-summary-component-factory-client.h> -#include <evolution-services/executive-summary-html-view.h> - -executive_summary_component_get_type -executive_summary_component_factory_get_type -executive_summary_component_factory_client_get_type -executive_summary_html_view_get_type diff --git a/help/devel/executive-summary/private-reference.sgml b/help/devel/executive-summary/private-reference.sgml deleted file mode 100644 index e06d7c1690..0000000000 --- a/help/devel/executive-summary/private-reference.sgml +++ /dev/null @@ -1,20 +0,0 @@ - <reference id="evolution-services-private-reference"> - <title>Evolution Services Private API Reference</title> - - <partintro> - <para> - This part presents the class and function reference for the - private APIs of the different components of the &Evolution; - Executive Summary Services Framework. - </para> - </partintro> - - &ExecutiveSummaryComponentFactoryClient; - </reference> - -<!-- -Local variables: -mode: sgml -sml-parent-document: ("../evolution-devel-guide.sgml" "book" "part" "") -End: ---> diff --git a/help/devel/executive-summary/public-reference.sgml b/help/devel/executive-summary/public-reference.sgml deleted file mode 100644 index 7758a9a5c8..0000000000 --- a/help/devel/executive-summary/public-reference.sgml +++ /dev/null @@ -1,22 +0,0 @@ - <reference id="evolution-services-public-reference"> - <title>Evolution Services Public API Reference</title> - - <partintro> - <para> - This part presents the class and function reference for the - public APIs of the different components of the &Evolution; - Executive Summary Services Framework. - </para> - </partintro> - - &ExecutiveSummaryComponent; - &ExecutiveSummaryComponentFactory; - &ExecutiveSummaryHtmlView; - </reference> - -<!-- -Local variables: -mode: sgml -sml-parent-document: ("../evolution-devel-guide.sgml" "book" "part" "") -End: ---> diff --git a/help/devel/executive-summary/tmpl/evolution-services-unused.sgml b/help/devel/executive-summary/tmpl/evolution-services-unused.sgml deleted file mode 100644 index e69de29bb2..0000000000 --- a/help/devel/executive-summary/tmpl/evolution-services-unused.sgml +++ /dev/null diff --git a/help/devel/executive-summary/tmpl/executive-summary-component-factory-client.sgml b/help/devel/executive-summary/tmpl/executive-summary-component-factory-client.sgml deleted file mode 100644 index ee8ef25689..0000000000 --- a/help/devel/executive-summary/tmpl/executive-summary-component-factory-client.sgml +++ /dev/null @@ -1,53 +0,0 @@ -<!-- ##### SECTION Title ##### --> -ExecutiveSummaryComponentFactoryClient - -<!-- ##### SECTION Short_Description ##### --> -GtkObject client to simplfy use of GNOME_Evolution_Summary_ComponentFactory - -<!-- ##### SECTION Long_Description ##### --> -<para> -This object provides an easy wrapper around the CORBA object that represents the - GNOME_Evolution_Summary_ComponentFactory interface. It handles conversion from -normal types to CORBA types and has error checking. -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> - -</para> - -<!-- ##### MACRO EXECUTIVE_SUMMARY_COMPONENT_FACTORY_CLIENT ##### --> -<para> -Casts a #GtkObject into an #ExecutiveSummaryComponentFactoryClient -</para> - -@obj: - - -<!-- ##### FUNCTION executive_summary_component_factory_client_construct ##### --> -<para> - -</para> - -@client: -@corba_object: - - -<!-- ##### FUNCTION executive_summary_component_factory_client_new ##### --> -<para> - -</para> - -@id: -@Returns: - - -<!-- ##### FUNCTION executive_summary_component_factory_client_create_view ##### --> -<para> - -</para> - -@client: -@Returns: - - diff --git a/help/devel/executive-summary/tmpl/executive-summary-component-factory.sgml b/help/devel/executive-summary/tmpl/executive-summary-component-factory.sgml deleted file mode 100644 index 7069eea9d0..0000000000 --- a/help/devel/executive-summary/tmpl/executive-summary-component-factory.sgml +++ /dev/null @@ -1,46 +0,0 @@ -<!-- ##### SECTION Title ##### --> -ExecutiveSummaryComponentFactory - -<!-- ##### SECTION Short_Description ##### --> -GtkObject wrapper for GNOME/Evolution/Summary/ComponentFactory. - -<!-- ##### SECTION Long_Description ##### --> -<para> -An ExecutiveSummaryComponentFactory simplifies the creation of a -GNOME_Evolution_Summary_ComponentFactory object. It also allows error checking -and all the standard #GtkObject signals. -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> - -</para> - -<!-- ##### MACRO EXECUTIVE_SUMMARY_COMPONENT_FACTORY ##### --> -<para> -Casts a #GtkObject to an #ExecutiveSummaryComponentFactory. -</para> - -@obj: A #GtkObject. - - -<!-- ##### USER_FUNCTION EvolutionServicesCreateViewFn ##### --> -<para> -The type of function that is called when the factory has to create a new view. -</para> - -@factory: The #ExecutiveSummaryComponent that is creating the view. -@closure: The data that was passed into executive_summary_factory_new (). -@Returns: An #ExecutiveSummaryComponent. - - -<!-- ##### FUNCTION executive_summary_component_factory_new ##### --> -<para> - -</para> - -@create_view: -@closure: -@Returns: - - diff --git a/help/devel/executive-summary/tmpl/executive-summary-component.sgml b/help/devel/executive-summary/tmpl/executive-summary-component.sgml deleted file mode 100644 index 04768b1b1c..0000000000 --- a/help/devel/executive-summary/tmpl/executive-summary-component.sgml +++ /dev/null @@ -1,37 +0,0 @@ -<!-- ##### SECTION Title ##### --> -ExecutiveSummaryComponent - -<!-- ##### SECTION Short_Description ##### --> -The base #BonoboObject that implements GNOME/Evolution/Summary/Component. - -<!-- ##### SECTION Long_Description ##### --> -<para> -This #GtkObject wrapper around the GNOME/Evolution/Summary/Component, is the -base object that has all the other interfaces aggregated onto it. These -interfaces are: GNOME/Evolution/HTMLView, Bonobo/Control, Bonobo/EventSource, -Bonobo/PropertyBag, Bonobo/PropertyControl and Bonobo/PersistStream. Each of -the aggregated interfaces performs a specific job in the creation of the service. -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> -#ExecutiveSummaryHtmlView, #BonoboControl, #BonoboEventSource, #BonoboPropertyBag, -#BonoboPropertyControl, #BonoboPersistStream. -</para> - -<!-- ##### MACRO EXECUTIVE_SUMMARY_COMPONENT ##### --> -<para> -Casts a #GtkObject to an #ExecutiveSummaryComponent. -</para> - -@obj: A #GtkObject. - - -<!-- ##### FUNCTION executive_summary_component_new ##### --> -<para> - -</para> - -@Returns: - - diff --git a/help/devel/executive-summary/tmpl/executive-summary-html-view.sgml b/help/devel/executive-summary/tmpl/executive-summary-html-view.sgml deleted file mode 100644 index 2fb66a2035..0000000000 --- a/help/devel/executive-summary/tmpl/executive-summary-html-view.sgml +++ /dev/null @@ -1,75 +0,0 @@ -<!-- ##### SECTION Title ##### --> -ExecutiveSummaryHtmlView - -<!-- ##### SECTION Short_Description ##### --> -A Bonobo component used to implement HTML based services. - -<!-- ##### SECTION Long_Description ##### --> -<para> -When writing HTML services, this component is aggregated onto an #ExecutiveSummaryComponent, to allow the Executive Summary to be able to find the HTML. -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> -#ExecutiveSummaryComponent, #BonoboEventSource -</para> - -<!-- ##### MACRO EXECUTIVE_SUMMARY_HTML_VIEW ##### --> -<para> - Casts a #GtkObject into an #ExecutiveSummaryHtmlView -</para> - -@obj: A #GtkObject - - -<!-- ##### MACRO EXECUTIVE_SUMMARY_HTML_VIEW_HTML_CHANGED ##### --> -<para> -This is the event that is emitted on the BonoboEventSource when the HTML is changed. -</para> - - - -<!-- ##### FUNCTION executive_summary_html_view_new_full ##### --> -<para> - -</para> - -@event_source: -@Returns: - - -<!-- ##### FUNCTION executive_summary_html_view_new ##### --> -<para> - -</para> - -@Returns: - - -<!-- ##### FUNCTION executive_summary_html_view_set_html ##### --> -<para> - -</para> - -@view: -@html: - - -<!-- ##### FUNCTION executive_summary_html_view_get_html ##### --> -<para> - -</para> - -@view: -@Returns: - - -<!-- ##### FUNCTION executive_summary_html_view_get_event_source ##### --> -<para> - -</para> - -@view: -@Returns: - - diff --git a/help/devel/fdl.sgml b/help/devel/fdl.sgml deleted file mode 100644 index 817adbdbb7..0000000000 --- a/help/devel/fdl.sgml +++ /dev/null @@ -1,671 +0,0 @@ -<!-- - The GNU Free Documentation License 1.1 in DocBook - Markup by Eric Baudais <baudais@okstate.edu> - Maintained by the GNOME Documentation Project - http://developer.gnome.org/projects/gdp - Version: 1.0.1 - Last Modified: Nov 16, 2000 ---> - -<appendix id="fdl"> - <docinfo> - <releaseinfo> - Version 1.1, March 2000 - </releaseinfo> - <copyright> - <year>2000</year><holder>Free Software Foundation, Inc.</holder> - </copyright> - <legalnotice id="fdl-legalnotice"> - <para> - <address>Free Software Foundation, Inc. <street>59 Temple Place, - Suite 330</street>, <city>Boston</city>, <state>MA</state> - <postcode>02111-1307</postcode> <country>USA</country></address> - Everyone is permitted to copy and distribute verbatim copies of this - license document, but changing it is not allowed. - </para> - </legalnotice> - </docinfo> - <title>GNU Free Documentation License</title> - - <sect1 id="fdl-preamble"> - <title>0. PREAMBLE</title> - <para> - The purpose of this License is to make a manual, textbook, or - other written document <quote>free</quote> 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. - </para> - - <para> - This License is a kind of <quote>copyleft</quote>, 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. - </para> - - <para> - 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. - </para> - </sect1> - <sect1 id="fdl-section1"> - <title>1. APPLICABILITY AND DEFINITIONS</title> - <para id="fdl-document"> - 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 - <quote>Document</quote>, below, refers to any such manual or - work. Any member of the public is a licensee, and is addressed - as <quote>you</quote>. - </para> - - <para id="fdl-modified"> - A <quote>Modified Version</quote> 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. - </para> - - <para id="fdl-secondary"> - A <quote>Secondary Section</quote> is a named appendix or a - front-matter section of the <link - linkend="fdl-document">Document</link> 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. - </para> - - <para id="fdl-invariant"> - The <quote>Invariant Sections</quote> are certain <link - linkend="fdl-secondary"> Secondary Sections</link> whose titles - are designated, as being those of Invariant Sections, in the - notice that says that the <link - linkend="fdl-document">Document</link> is released under this - License. - </para> - - <para id="fdl-cover-texts"> - The <quote>Cover Texts</quote> are certain short passages of - text that are listed, as Front-Cover Texts or Back-Cover Texts, - in the notice that says that the <link - linkend="fdl-document">Document</link> is released under this - License. - </para> - - <para id="fdl-transparent"> - A <quote>Transparent</quote> copy of the <link - linkend="fdl-document"> Document</link> 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 <quote>Transparent</quote> is called - <quote>Opaque</quote>. - </para> - - <para> - 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. - </para> - - <para id="fdl-title-page"> - The <quote>Title Page</quote> 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, <quote>Title Page</quote> means the text near the - most prominent appearance of the work's title, preceding the - beginning of the body of the text. - </para> - </sect1> - - <sect1 id="fdl-section2"> - <title>2. VERBATIM COPYING</title> - <para> - You may copy and distribute the <link - linkend="fdl-document">Document</link> 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 <link - linkend="fdl-section3">section 3</link>. - </para> - - <para> - You may also lend copies, under the same conditions stated - above, and you may publicly display copies. - </para> - </sect1> - - <sect1 id="fdl-section3"> - <title>3. COPYING IN QUANTITY</title> - <para> - If you publish printed copies of the <link - linkend="fdl-document">Document</link> numbering more than 100, - and the Document's license notice requires <link - linkend="fdl-cover-texts">Cover Texts</link>, 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 - <link linkend="fdl-document">Document</link> and satisfy these - conditions, can be treated as verbatim copying in other - respects. - </para> - - <para> - 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. - </para> - - <para> - If you publish or distribute <link - linkend="fdl-transparent">Opaque</link> copies of the <link - linkend="fdl-document">Document</link> numbering more than 100, - you must either include a machine-readable <link - linkend="fdl-transparent">Transparent</link> 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. - </para> - - <para> - It is requested, but not required, that you contact the authors - of the <link linkend="fdl-document">Document</link> well before - redistributing any large number of copies, to give them a chance - to provide you with an updated version of the Document. - </para> - </sect1> - - <sect1 id="fdl-section4"> - <title>4. MODIFICATIONS</title> - <para> - You may copy and distribute a <link - linkend="fdl-modified">Modified Version</link> of the <link - linkend="fdl-document">Document</link> under the conditions of - sections <link linkend="fdl-section2">2</link> and <link - linkend="fdl-section3">3</link> 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: - </para> - - <itemizedlist mark="opencircle"> - <listitem> - <formalpara> - <title>A</title> - <para> - Use in the <link linkend="fdl-title-page">Title - Page</link> (and on the covers, if any) a title distinct - from that of the <link - linkend="fdl-document">Document</link>, 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. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>B</title> - <para> - List on the <link linkend="fdl-title-page">Title - Page</link>, as authors, one or more persons or entities - responsible for authorship of the modifications in the - <link linkend="fdl-modified">Modified Version</link>, - together with at least five of the principal authors of - the <link linkend="fdl-document">Document</link> (all of - its principal authors, if it has less than five). - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>C</title> - <para> - State on the <link linkend="fdl-title-page">Title - Page</link> the name of the publisher of the <link - linkend="fdl-modified">Modified Version</link>, as the - publisher. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>D</title> - <para> - Preserve all the copyright notices of the <link - linkend="fdl-document">Document</link>. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>E</title> - <para> - Add an appropriate copyright notice for your modifications - adjacent to the other copyright notices. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>F</title> - <para> - Include, immediately after the copyright notices, a - license notice giving the public permission to use the - <link linkend="fdl-modified">Modified Version</link> under - the terms of this License, in the form shown in the - Addendum below. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>G</title> - <para> - Preserve in that license notice the full lists of <link - linkend="fdl-invariant"> Invariant Sections</link> and - required <link linkend="fdl-cover-texts">Cover - Texts</link> given in the <link - linkend="fdl-document">Document's</link> license notice. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>H</title> - <para> - Include an unaltered copy of this License. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>I</title> - <para> - Preserve the section entitled <quote>History</quote>, and - its title, and add to it an item stating at least the - title, year, new authors, and publisher of the <link - linkend="fdl-modified">Modified Version </link>as given on - the <link linkend="fdl-title-page">Title Page</link>. If - there is no section entitled <quote>History</quote> in the - <link linkend="fdl-document">Document</link>, 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. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>J</title> - <para> - Preserve the network location, if any, given in the <link - linkend="fdl-document">Document</link> for public access - to a <link linkend="fdl-transparent">Transparent</link> - 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 <quote>History</quote> - 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. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>K</title> - <para> - In any section entitled <quote>Acknowledgements</quote> or - <quote>Dedications</quote>, 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. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>L</title> - <para> - Preserve all the <link linkend="fdl-invariant">Invariant - Sections</link> of the <link - linkend="fdl-document">Document</link>, unaltered in their - text and in their titles. Section numbers or the - equivalent are not considered part of the section titles. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>M</title> - <para> - Delete any section entitled - <quote>Endorsements</quote>. Such a section may not be - included in the <link linkend="fdl-modified">Modified - Version</link>. - </para> - </formalpara> - </listitem> - - <listitem> - <formalpara> - <title>N</title> - <para> - Do not retitle any existing section as - <quote>Endorsements</quote> or to conflict in title with - any <link linkend="fdl-invariant">Invariant - Section</link>. - </para> - </formalpara> - </listitem> - </itemizedlist> - - <para> - If the <link linkend="fdl-modified">Modified Version</link> - includes new front-matter sections or appendices that qualify as - <link linkend="fdl-secondary">Secondary Sections</link> 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 <link - linkend="fdl-invariant">Invariant Sections</link> in the - Modified Version's license notice. These titles must be - distinct from any other section titles. - </para> - - <para> - You may add a section entitled <quote>Endorsements</quote>, - provided it contains nothing but endorsements of your <link - linkend="fdl-modified">Modified Version</link> 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. - </para> - - <para> - You may add a passage of up to five words as a <link - linkend="fdl-cover-texts">Front-Cover Text</link>, and a passage - of up to 25 words as a <link - linkend="fdl-cover-texts">Back-Cover Text</link>, to the end of - the list of <link linkend="fdl-cover-texts">Cover Texts</link> - in the <link linkend="fdl-modified">Modified Version</link>. - 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 <link linkend="fdl-document">Document</link> - 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. - </para> - - <para> - The author(s) and publisher(s) of the <link - linkend="fdl-document">Document</link> do not by this License - give permission to use their names for publicity for or to - assert or imply endorsement of any <link - linkend="fdl-modified">Modified Version </link>. - </para> - </sect1> - - <sect1 id="fdl-section5"> - <title>5. COMBINING DOCUMENTS</title> - <para> - You may combine the <link linkend="fdl-document">Document</link> - with other documents released under this License, under the - terms defined in <link linkend="fdl-section4">section 4</link> - above for modified versions, provided that you include in the - combination all of the <link linkend="fdl-invariant">Invariant - Sections</link> of all of the original documents, unmodified, - and list them all as Invariant Sections of your combined work in - its license notice. - </para> - - <para> - The combined work need only contain one copy of this License, - and multiple identical <link linkend="fdl-invariant">Invariant - Sections</link> 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. - </para> - - <para> - In the combination, you must combine any sections entitled - <quote>History</quote> in the various original documents, - forming one section entitled <quote>History</quote>; likewise - combine any sections entitled <quote>Acknowledgements</quote>, - and any sections entitled <quote>Dedications</quote>. You must - delete all sections entitled <quote>Endorsements.</quote> - </para> - </sect1> - - <sect1 id="fdl-section6"> - <title>6. COLLECTIONS OF DOCUMENTS</title> - <para> - You may make a collection consisting of the <link - linkend="fdl-document">Document</link> 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. - </para> - - <para> - You may extract a single document from such a collection, and - dispbibute 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. - </para> - </sect1> - - <sect1 id="fdl-section7"> - <title>7. AGGREGATION WITH INDEPENDENT WORKS</title> - <para> - A compilation of the <link - linkend="fdl-document">Document</link> 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 <link linkend="fdl-modified">Modified Version</link> - of the Document, provided no compilation copyright is claimed - for the compilation. Such a compilation is called an - <quote>aggregate</quote>, 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 <link - linkend="fdl-cover-texts">Cover Text</link> requirement of <link - linkend="fdl-section3">section 3</link> 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. - </para> - </sect1> - - <sect1 id="fdl-section8"> - <title>8. TRANSLATION</title> - <para> - Translation is considered a kind of modification, so you may - distribute translations of the <link - linkend="fdl-document">Document</link> under the terms of <link - linkend="fdl-section4">section 4</link>. Replacing <link - linkend="fdl-invariant"> Invariant Sections</link> 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. - </para> - </sect1> - - <sect1 id="fdl-section9"> - <title>9. TERMINATION</title> - <para> - You may not copy, modify, sublicense, or distribute the <link - linkend="fdl-document">Document</link> 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. - </para> - </sect1> - - <sect1 id="fdl-section10"> - <title>10. FUTURE REVISIONS OF THIS LICENSE</title> - <para> - The <ulink type="http" - url="http://www.gnu.org/fsf/fsf.html">Free Software - Foundation</ulink> 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 <ulink - type="http" - url="http://www.gnu.org/copyleft">http://www.gnu.org/copyleft/</ulink>. - </para> - - <para> - Each version of the License is given a distinguishing version - number. If the <link linkend="fdl-document">Document</link> - specifies that a particular numbered version of this License - <quote>or any later version</quote> 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. - </para> - </sect1> - - <sect1 id="fdl-using"> - <title>Addendum</title> - <para> - 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: - </para> - - <blockquote> - <para> - Copyright © YEAR YOUR NAME. - </para> - <para> - 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 <link - linkend="fdl-invariant">Invariant Sections</link> being LIST - THEIR TITLES, with the <link - linkend="fdl-cover-texts">Front-Cover Texts</link> being LIST, - and with the <link linkend="fdl-cover-texts">Back-Cover - Texts</link> being LIST. A copy of the license is included in - the section entitled <quote>GNU Free Documentation - License</quote>. - </para> - </blockquote> - - <para> - If you have no <link linkend="fdl-invariant">Invariant - Sections</link>, write <quote>with no Invariant Sections</quote> - instead of saying which ones are invariant. If you have no - <link linkend="fdl-cover-texts">Front-Cover Texts</link>, write - <quote>no Front-Cover Texts</quote> instead of - <quote>Front-Cover Texts being LIST</quote>; likewise for <link - linkend="fdl-cover-texts">Back-Cover Texts</link>. - </para> - - <para> - 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 <ulink type="http" - url="http://www.gnu.org/copyleft/gpl.html"> GNU General Public - License</ulink>, to permit their use in free software. - </para> - </sect1> -</appendix> - - - - - - diff --git a/help/devel/importer/.cvsignore b/help/devel/importer/.cvsignore deleted file mode 100644 index 0842a93f7a..0000000000 --- a/help/devel/importer/.cvsignore +++ /dev/null @@ -1,3 +0,0 @@ -sgml -Makefile -Makefile.in diff --git a/help/devel/importer/Makefile.am b/help/devel/importer/Makefile.am deleted file mode 100644 index ef3b2b98ee..0000000000 --- a/help/devel/importer/Makefile.am +++ /dev/null @@ -1,127 +0,0 @@ -# The name of the module. -DOC_MODULE=evolution-shell-importer - -# The directory containing the source code -DOC_SOURCE_DIR=$(EVOLUTION_DIR)/shell/importer - -CFLAGS =" \ - -I$(top_srcdir)/shell/importer \ - -I$(top_srcdir)/shell \ - -I$(top_srcdir) \ - -I$(top_builddir) \ - $(BONOBO_VFS_GNOME_CFLAGS) \ - " - -LDFLAGS=" \ - $(BONOBO_VFS_GNOME_LIBS) \ - $(top_builddir)/shell/importer/.libs/libevolution-importer.a \ - " - -DOC_DIR=$(datadir)/gnome/html - -DOC_DIR_INSTALL_FILES = \ - evolution-shell-importer.args \ - evolution-shell-importer.hierarchy \ - evolution-shell-importer.signals \ - evolution-shell-importer.types \ - evolution-shell-importer-decl.txt \ - evolution-shell-importer-sections.txt - -SOURCE_FILES = \ - $(top_srcdir)/shell/importer/evolution-importer.c \ - $(top_srcdir)/shell/importer/evolution-importer.h \ - $(top_srcdir)/shell/importer/evolution-importer-client.c \ - $(top_srcdir)/shell/importer/evolution-importer-client.h - -IGNORED_HEADER_FILES = \ - GNOME_Evolution_Importer.h \ - importer.h - -scan_generated = \ - evolution-shell-importer-decl.txt \ - evolution-shell-importer.args \ - evolution-shell-importer.hierarchy \ - evolution-shell-importer.signals \ - evolution-shell-importer.types - -tmpl_dependencies = \ - evolution-shell-importer-decl.txt \ - evolution-shell-importer-sections.txt \ - evolution-shell-importer.args \ - evolution-shell-importer.hierarchy \ - evolution-shell-importer.signals - -tmpl_sources = \ - tmpl/evolution-importer.sgml \ - tmpl/evolution-shell-importer-unused.sgml - -tmpl_generated = \ - evolution-shell-importer-unused.txt - -sgml_dependencies = \ - evolution-shell-importer-decl.txt \ - evolution-shell-importer-sections.txt \ - evolution-shell-importer.args \ - evolution-shell-importer.hierarchy \ - evolution-shell-importer.signals \ - tmpl/evolution-importer.sgml - -sgml_generated = \ - sgml/evolution-importer.sgml \ - sgml/evolution-shell-importer-doc.bottom \ - sgml/evolution-shell-importer-doc.top \ - sgml/object_index.sgml \ - sgml/tree_index.sgml - -EXTRA_DIST = \ - evolution-shell-importer.args \ - evolution-shell-importer.hierarchy \ - evolution-shell-importer.signals \ - evolution-shell-importer.types \ - evolution-shell-importer-decl.txt \ - evolution-shell-importer-sections.txt - -all: $(sgml_generated) - -if ENABLE_GTK_DOC -scan $(scan_generated): $(SOURCE_FILES) - -(cd $(srcdir) \ - && env CFLAGS=$(CFLAGS) LDFLAGS=$(LDFLAGS) \ - gtkdoc-scanobj --module=$(DOC_MODULE) \ - && gtkdoc-scan --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) \ - --ignore-headers="$(IGNORED_HEADER_FILES)" ) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - cd $(srcdir) && gtkdoc-mktmpl --module=$(DOC_MODULE) - -sgml $(sgml_generated): $(sgml_dependencies) - cd $(srcdir) \ - && gtkdoc-mkdb --module=$(DOC_MODULE) --source-dir=$(DOC_SOURCE_DIR) -else -scan $(scan_generated): $(SOURCE_FILE) - -templates $(tmpl_sources) $(tmpl_generated): $(tmpl_dependencies) - -sgml $(sgml_generated): $(sgml_dependencies) -endif - -clean-local: - rm -f *~ *.bak *.signals *-unused.txt - -maintainer-clean-local: clean - cd $(srcdir) && rm -rf sgml $(DOC_MODULE)-decl-list.txt $(DOC_MODULE)-decl.txt - -install-data-local: - $(mkinstalldirs) $(DOC_DIR) - for i in $(DOC_DIR_INSTALL_FILES); do \ - $(INSTALL_DATA) $$i $(DOC_DIR); \ - done - -dist-hook: - mkdir $(distdir)/sgml - mkdir $(distdir)/tmpl - -cp $(srcdir)/tmpl/*.sgml $(distdir)/tmpl - -cp $(srcdir)/sgml/*.sgml $(distdir)/sgml - -cp $(srcdir)/sgml/*.bottom $(srcdir)/sgml/*.top $(distdir)/sgml - -.PHONY: scan templates sgml diff --git a/help/devel/importer/evolution-shell-importer-sections.txt b/help/devel/importer/evolution-shell-importer-sections.txt deleted file mode 100644 index e2474f6375..0000000000 --- a/help/devel/importer/evolution-shell-importer-sections.txt +++ /dev/null @@ -1,79 +0,0 @@ -<INCLUDE>evolution-importer.h</INCLUDE> - -<SECTION> -<FILE>evolution-importer</FILE> -EVOLUTION_IMPORTER -<TITLE>EvolutionImporter</TITLE> - -EvolutionImporterSupportFormatFn -EvolutionImporterLoadFileFn -EvolutionImporterProcessItemFn -EvolutionImporterGetErrorFn - -EvolutionImporterResult - -evolution_importer_new - -<SUBSECTION Standard> -EVOLUTION_TYPE_IMPORTER -EVOLUTION_IMPORTER -EVOLUTION_IS_IMPORTER -EVOLUTION_IMPORTER_CLASS -EVOLUTION_IS_IMPORTER_CLASS -evolution_importer_get_type - -<SUBSECTION Private> -EvolutionImporter -EvolutionImporterPrivate - -</SECTION> - -<INCLUDE>evolution-importer-listener.h</INCLUDE> -<SECTION> -<FILE>evolution-importer-listener</FILE> -EVOLUTION_IMPORTER_LISTENER -<TITLE>EvolutionImporterListener</TITLE> - -EvolutionImporterListenerCallback - -evolution_importer_listener_new - -<SUBSECTION Standard> -EVOLUTION_TYPE_IMPORTER_LISTENER -EVOLUTION_IMPORTER_LISTENER -EVOLUTION_IMPORTER_LISTENER_CLASS -EVOLUTION_IS_IMPORTER_LISTENER -EVOLUTION_IS_IMPORTER_LISTENER_CLASS -evolution_importer_listener_get_type - -<SUBSECTION Private> -EvolutionImporterListener -EvolutionImporterListenerPrivate - -</SECTION> - -<INCLUDE>evolution-importer-client.h</INCLUDE> -<SECTION> -<FILE>evolution-importer-client</FILE> -EVOLUTION_IMPORTER_CLIENT -<TITLE>EvolutionImporterClient</TITLE> - -evolution_importer_client_new -evolution_importer_client_new_from_id -evolution_importer_client_support_format -evolution_importer_client_load_file -evolution_importer_client_process_item -evolution_importer_client_get_error - -<SUBSECTION Standard> -EVOLUTION_TYPE_IMPORTER_CLIENT -EVOLUTION_IMPORTER_CLIENT -EVOLUTION_IMPORTER_CLIENT_CLASS -EVOLUTION_IS_IMPORTER_CLIENT -EVOLUTION_IS_IMPORTER_CLIENT_CLASS -evolution_importer_client_get_type - -<SUBSECTION Private> -EvolutionImporterClient - -</SECTION> diff --git a/help/devel/importer/evolution-shell-importer.args b/help/devel/importer/evolution-shell-importer.args deleted file mode 100644 index e69de29bb2..0000000000 --- a/help/devel/importer/evolution-shell-importer.args +++ /dev/null diff --git a/help/devel/importer/evolution-shell-importer.heirarchy b/help/devel/importer/evolution-shell-importer.heirarchy deleted file mode 100644 index 78e430d311..0000000000 --- a/help/devel/importer/evolution-shell-importer.heirarchy +++ /dev/null @@ -1,5 +0,0 @@ -GtkObject - BonoboObject - EvolutionImporter - BonoboObjectClient - EvolutionImporterClient diff --git a/help/devel/importer/evolution-shell-importer.hierarchy b/help/devel/importer/evolution-shell-importer.hierarchy deleted file mode 100644 index 5f1b55c709..0000000000 --- a/help/devel/importer/evolution-shell-importer.hierarchy +++ /dev/null @@ -1,14 +0,0 @@ -GtkObject - GtkWidget - GtkRange - GtkScale - GtkContainer - GtkBin - GtkButton - GtkToggleButton - GtkCheckButton - BonoboObject - EvolutionImporter - Handle to remote Bonobo::Unknown - EvolutionImporterClient - EvolutionImporterListener diff --git a/help/devel/importer/evolution-shell-importer.types b/help/devel/importer/evolution-shell-importer.types deleted file mode 100644 index 9dcdf5f0f1..0000000000 --- a/help/devel/importer/evolution-shell-importer.types +++ /dev/null @@ -1,9 +0,0 @@ -#include <gnome.h> -#include <bonobo.h> -#include <evolution/importer/evolution-importer.h> -#include <evolution/importer/evolution-importer-client.h> -#include <evolution/importer/evolution-importer-listener.h> - -evolution_importer_get_type -evolution_importer_client_get_type -evolution_importer_listener_get_type diff --git a/help/devel/importer/private-reference.sgml b/help/devel/importer/private-reference.sgml deleted file mode 100644 index d28c7b8591..0000000000 --- a/help/devel/importer/private-reference.sgml +++ /dev/null @@ -1,21 +0,0 @@ - <reference id="importer-private-reference"> - <title>Importer Private API Reference</title> - - <partintro> - <para> - This part presents the class and function reference for the - private APIs of the different components of the &Evolution; - Import Framework. - </para> - </partintro> - - &EvolutionImporterListener; - &EvolutionImporterClient; - </reference> - -<!-- -Local variables: -mode: sgml -sml-parent-document: ("../evolution-devel-guide.sgml" "book" "part" "") -End: ---> diff --git a/help/devel/importer/public-reference.sgml b/help/devel/importer/public-reference.sgml deleted file mode 100644 index ba99c9b309..0000000000 --- a/help/devel/importer/public-reference.sgml +++ /dev/null @@ -1,20 +0,0 @@ - <reference id="importer-public-reference"> - <title>Importer Public API Reference</title> - - <partintro> - <para> - This part presents the class and function reference for the - public APIs of the different components of the &Evolution; - Import Framework. - </para> - </partintro> - - &EvolutionImporter; - </reference> - -<!-- -Local variables: -mode: sgml -sml-parent-document: ("../evolution-devel-guide.sgml" "book" "part" "") -End: ---> diff --git a/help/devel/importer/tmpl/evolution-importer-client.sgml b/help/devel/importer/tmpl/evolution-importer-client.sgml deleted file mode 100644 index 8122e4fb2d..0000000000 --- a/help/devel/importer/tmpl/evolution-importer-client.sgml +++ /dev/null @@ -1,83 +0,0 @@ -<!-- ##### SECTION Title ##### --> -EvolutionImporterClient - -<!-- ##### SECTION Short_Description ##### --> -A #GtkObject based client to simplify use of a GNOME_Evolution_Importer object. - -<!-- ##### SECTION Long_Description ##### --> -<para> -This #GtkObject provides a convience wrapper to the GNOME_Evolution_Importer object, providing error checking and hiding all the CORBA internals from the user. -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> - -</para> - -<!-- ##### MACRO EVOLUTION_IMPORTER_CLIENT ##### --> -<para> -Casts a #GtkObject into an #EvolutionImporterClient -</para> - -@obj: A #GtkObject - - -<!-- ##### FUNCTION evolution_importer_client_new ##### --> -<para> - -</para> - -@objref: -@Returns: - - -<!-- ##### FUNCTION evolution_importer_client_new_from_id ##### --> -<para> - -</para> - -@id: -@Returns: - - -<!-- ##### FUNCTION evolution_importer_client_support_format ##### --> -<para> - -</para> - -@client: -@filename: -@Returns: - - -<!-- ##### FUNCTION evolution_importer_client_load_file ##### --> -<para> - -</para> - -@client: -@filename: -@Returns: - - -<!-- ##### FUNCTION evolution_importer_client_process_item ##### --> -<para> - -</para> - -@client: -@listener: -<!-- # Unused Parameters # --> -@callback: -@closure: - - -<!-- ##### FUNCTION evolution_importer_client_get_error ##### --> -<para> - -</para> - -@client: -@Returns: - - diff --git a/help/devel/importer/tmpl/evolution-importer.sgml b/help/devel/importer/tmpl/evolution-importer.sgml deleted file mode 100644 index 8d8351aed2..0000000000 --- a/help/devel/importer/tmpl/evolution-importer.sgml +++ /dev/null @@ -1,86 +0,0 @@ -<!-- ##### SECTION Title ##### --> -EvolutionImporter - -<!-- ##### SECTION Short_Description ##### --> -A #BonoboObject that implements the GNOME/Evolution/Importer interface. - -<!-- ##### SECTION Long_Description ##### --> -<para> -A #BonoboObject wrapper around the GNOME/Evolution/Importer interface, providing error checking and reference counting, hiding the CORBA internals from the user and providing a simple way to create a GNOME_Evolution_Importer object. -</para> - -<!-- ##### SECTION See_Also ##### --> -<para> - -</para> - -<!-- ##### MACRO EVOLUTION_IMPORTER ##### --> -<para> -Casts a #GtkObject into an #EvolutionImporter. -</para> - -@obj: A #GtkObject. - - -<!-- ##### USER_FUNCTION EvolutionImporterSupportFormatFn ##### --> -<para> -The type of function that is called when the importer wishes to find out if the importing component can support the file given in @filename. -</para> - -@importer: The #EvolutionImporter. -@filename: The filename of the file to check. -@closure: The data passed into evolution_importer_new (). -@Returns: A #gboolean. TRUE if the importing component can import the file, FALSE otherwise. - - -<!-- ##### USER_FUNCTION EvolutionImporterLoadFileFn ##### --> -<para> -The type of function that is called when the importer wishes the importing component to load the file given in @filename, and initialise itself. -</para> - -@importer: The #EvolutionImporter. -@filename: The filename of the file to load. -@closure: The data passed into evolution_importer_new (). -@Returns: A #gboolean. TRUE if the load and initialisation was successful, FALSE otherwise. - - -<!-- ##### USER_FUNCTION EvolutionImporterProcessItemFn ##### --> -<para> -The type of function that is called when the importer wants the importing component to process the next item (or items) in a file. -</para> - -@importer: The #EvolutionImporter -@listener: A GNOME_Evolution_Importer_Listener CORBA object. -@closure: The data passed into evolution_importer_new (). -@ev: A #CORBA_Environment for returning any CORBA exceptions. - - -<!-- ##### USER_FUNCTION EvolutionImporterGetErrorFn ##### --> -<para> -The type of function that is called when the importer wants to get a string version of an error. Not all importing components support this function. -</para> - -@importer: The #EvolutionImporter. -@closure: The data passed to evolution_importer_new (). -@Returns: A string representation of the error, or NULL if there was no error, or the importing component does not support the getError method. - - -<!-- ##### ENUM EvolutionImporterResult ##### --> -<para> - -</para> - - -<!-- ##### FUNCTION evolution_importer_new ##### --> -<para> - -</para> - -@support_format_fn: -@load_file_fn: -@process_item_fn: -@get_error_fn: -@closure: -@Returns: - - diff --git a/help/devel/importer/tmpl/evolution-shell-importer-unused.sgml b/help/devel/importer/tmpl/evolution-shell-importer-unused.sgml deleted file mode 100644 index 7a9a98034b..0000000000 --- a/help/devel/importer/tmpl/evolution-shell-importer-unused.sgml +++ /dev/null @@ -1,10 +0,0 @@ -<!-- ##### USER_FUNCTION EvolutionImporterClientCallback ##### --> -<para> - -</para> - -@client: -@result: -@more_items: -@data: - diff --git a/help/devel/preface.sgml b/help/devel/preface.sgml deleted file mode 100644 index fdaa824a8b..0000000000 --- a/help/devel/preface.sgml +++ /dev/null @@ -1,113 +0,0 @@ - <preface id="introduction"> - <title>Introduction</title> - - <para> - This is the &Evolution; Developer's Guide or programming guide - for the &Evolution; groupware suite. If you are a programmer - and you wish to use &Evolution;'s functionality from your own - applications or if you wish to modify the &Evolution; core code, - you should read this guide. - </para> - - <para> - If you are an end-user of &Evolution; you do not need to read - this guide; please read the &Evolution; User's Guide instead. - </para> - - <para> - This guide contains the information you need to know to do the - following: - - <itemizedlist> - <listitem> - <para> - Write applications that use &Evolution;'s data - repositories via the &Wombat; personal information server. - Examples of this would be a <application>GNOME - Panel</application> applet that displays today's - appointments, or a telephone dialer application that uses - the contents of the &Evolution; Addressbook. - </para> - </listitem> - - <listitem> - <para> - Write applications that use the &Camel; mail library. - This includes extending &Evolution;'s own mail component - to perform additional functions. - </para> - </listitem> - - <listitem> - <para> - Write new components for the &Evolution; Shell. Instead - of writing a stand-alone application, you can provide your - users with the benefit of having integrated views of their - data from within Evolution. - </para> - </listitem> - - <listitem> - <para> - Write new modules for the &Evolution; Executive Summary. - This allows you to present commonly-accessed information - in a convenient fashion directly in the &Evolution; Shell. - </para> - </listitem> - - <listitem> - <para> - Modify the core &Evolution; code to add new features or - change its architecture. - </para> - </listitem> - </itemizedlist> - </para> - - <sect1 id="organization"> - <title>Organization of this Guide</title> - - <para> - This guide is organized in two big sections. The first is a - programming guide, which consists of one part for each one of - &Evolution;'s components: there are separate parts for the - calendar, the addressbook, the mailer, the executive summary, - and the shell. Each part gives a description of the - architecture of its corresponding component, and also gives - information about the component's internal architecture and - some implementation details. - </para> - - <para> - The second section of this guide is a reference guide for - &Evolution;'s programming interfaces. We have separated these - into public and private interfaces. The public ones are those - that most people will need to use when writing extensions or - third-party components; the private interfaces are those used - internally in &Evolution;. Even if you do not intend to - modify the &Evolution; core code, it may be useful to know a - bit about the way it is organized internally. - </para> - - <para> - &Evolution; is free software, and we want you as a programmer - to make the most of it. We have provided many useful - interfaces that you can use in your own applications. Still, - we want you to view &Evolution; as a framework for building - groupware applications, and this may occasionally involve - making changes to its core code. We want you to learn from - &Evolution;'s design because we think it marks an important - milestone in the development of large-scale free software - applications. We want you to modify it as you see fit. Free - software gives you this freedom, and we want the whole world - to benefit from it. - </para> - </sect1> - </preface> - -<!-- -Local variables: -mode: sgml -sgml-parent-document: ("evolution-devel-guide.sgml" "book" "book" "") -End: ---> diff --git a/help/devel/reference.sgml b/help/devel/reference.sgml deleted file mode 100644 index b0c81de77f..0000000000 --- a/help/devel/reference.sgml +++ /dev/null @@ -1,49 +0,0 @@ - <part id="evolution-api-reference"> - <title>&Evolution; API Reference</title> - - <partintro> - <para> - This part presents the class and function reference for the - different libraries and interfaces that &Evolution; provides. - Classes are described together with their methods; individual - functions are grouped by functional group. - </para> - - <para> - &Evolution; provides two kinds of interfaces, public and - private. The public interfaces are those designed to be used - from third-party applications or components; if you wanted to - write an application that uses &Evolution;'s data repositories - to display data in a particular way, you would use the public - interfaces. The private interfaces are those used inside - &Evolution; itself; these are generally not interesting unless - you intend to make modifications to the &Evolution; code base. - </para> - - <para> - While the public and private interfaces are described in - separate reference sections, we have decided to put them - together in the same book, this guide, because we want to - encourage you to regard &Evolution; as something more than a - black box that stores and dispatches personal information. We - want you to make modifications to the &Evolution; core if - these would allow you to present or store your data in better - ways. &Evolution; is free software; we want you to learn from - its design and implementation details so that you can make it - even better for the whole world to use. - </para> - </partintro> - - &calendar-public-reference; - &importer-public-reference; - &evolution-services-public-reference; - &importer-private-reference; - &evolution-services-private-reference; - </part> - -<!-- -Local variables: -mode: sgml -sgml-parent-document: ("evolution-devel-guide.sgml" "book" "book" "") -End: ---> diff --git a/help/white-papers/calendar/calendar.sgml b/help/white-papers/calendar/calendar.sgml deleted file mode 100644 index 2cb3132e2b..0000000000 --- a/help/white-papers/calendar/calendar.sgml +++ /dev/null @@ -1,209 +0,0 @@ -<!doctype article PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [ -<!entity Evolution "<application>Evolution</application>"> -<!entity CUA "<acronym>CUA</acronym>"> -<!entity PCS "<acronym>PCS</acronym>"> -<!entity Bonobo "<application>Bonobo</application>"> -<!entity CORBA "<acronym>CORBA</acronym>"> -<!entity GTK "<acronym>GTK+</acronym>"> -]> - -<article class="whitepaper" id="calendar"> - - <artheader> - <title>&Evolution; Calendaring Framework</title> - - <authorgroup> - <author> - <firstname>Federico</firstname> - <surname>Mena Quintero</surname> - <affiliation> - <address> - <email>federico@helixcode.com</email> - </address> - </affiliation> - </author> - </authorgroup> - - <copyright> - <year>2000</year> - <holder>Helix Code, Inc.</holder> - </copyright> - - <abstract> - <para> - 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. - </para> - </abstract> - </artheader> - - <!-- Introduction --> - - <sect1 id="introduction"> - <title>Introduction</title> - - <para> - 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 - <productname>Palm Pilot</productname> 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”. - </para> - - <para> - 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;). - </para> - - <para> - 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. - </para> - </sect1> - - <!-- Personal Calendar Server --> - - <sect1 id="pcs"> - <title>Personal Calendar Server</title> - - <para> - 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: - </para> - - <formalpara> - <title>Storage</title> - - <para> - 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. - </para> - </formalpara> - - <formalpara> - <title>Basic Queries</title> - - <para> - 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. - </para> - </formalpara> - - <formalpara> - <title>Recurrence and Alarm Queries</title> - - <para> - 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. - </para> - </formalpara> - - <formalpara> - <title>Notification of Changes</title> - - <para> - 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. - </para> - </formalpara> - </sect1> - - <!-- Calenar User Agent --> - - <sect1 id="cua"> - <title>Calendar User Agent</title> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect1> - - <!-- Calendar Client Library --> - - <sect1 id="client-lib"> - <title>Calendar Client Library</title> - - <para> - 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 - <classname>Listener</classname> interface, which defines the - notification callbacks that the PCS uses to inform clients about - changes to the calendar. - </para> - - <para> - As a convenience for >K; programmers, &Evolution; also - includes a library which provides a - <classname>CalClient</classname> class which can be used for - communication with the personal calendar server. Objects of - this class automatically contact the PCS when they are created. - <classname>CalClient</classname> 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;. - </para> - - <para> - The implementation of the <classname>CalClient</classname> class - simply wraps the &Evolution; &CORBA; interfaces for calendaring - with a familiar-looking >K; object. Calls to the - <classname>Listener</classname> interface get translated to - signal emissions from the <classname>CalClient</classname>, thus - shielding programmers from the details of the &CORBA; - interfaces. - </para> - </sect1> -</article> diff --git a/help/white-papers/mail/camel.sgml b/help/white-papers/mail/camel.sgml deleted file mode 100644 index a339909f54..0000000000 --- a/help/white-papers/mail/camel.sgml +++ /dev/null @@ -1,339 +0,0 @@ -<!doctype article PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [ -<!entity Evolution "<application>Evolution</application>"> -<!entity Camel "Camel"> -]> - -<article class="whitepaper" id="camel"> - - <artheader> - <title>The &Camel; Messaging Library</title> - - <authorgroup> - <author> - <firstname>Dan</firstname> - <surname>Winship</surname> - <affiliation> - <address> - <email>danw@helixcode.com</email> - </address> - </affiliation> - </author> - - <author> - <firstname>Bertrand</firstname> - <surname>Guiheneuf</surname> - <affiliation> - <address> - <email>bertrand@helixcode.com</email> - </address> - </affiliation> - </author> - </authorgroup> - - <copyright> - <year>2000</year> - <holder>Helix Code, Inc.</holder> - </copyright> - - </artheader> - - <sect1 id="introduction"> - <title>Introduction</title> - - <para> - &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. - </para> - - <para> - &Camel;'s initial design is heavily based on Sun's - <trademark>JavaMail</trademark> 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. - </para> - - <para> - &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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect1> - - <sect1 id="overview"> - <title>Overview</title> - - <graphic format="gif" fileref="camel"></graphic> - - <para> - To begin using &Camel;, an application first creates a - <classname>CamelSession</classname> object. This object is used - to store application defaults, and to coordinate communication - between providers and the application. - </para> - - <para> - A <classname>CamelProvider</classname> 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. - </para> - - <para> - <classname>CamelService</classname> is an abstract class for - describing a connection to a local or remote service. It - currently has two subclasses: <classname>CamelStore</classname>, - for services that store messages (such as IMAP servers and mbox - files), and <classname>CamelTransport</classname>, 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. - </para> - - <para> - A <classname>CamelStore</classname> contains some number of - <classname>CamelFolder</classname> objects, which in turn - contain messages. A <classname>CamelFolder</classname> provides - a <classname>CamelFolderSummary</classname> 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 <classname>CamelMedium</classname>. - </para> - - <para> - Email messages are represented by the - <classname>CamelMimeMessage</classname> class, a subclass of - <classname>CamelMedium</classname>. This class includes - operations for accessing RFC822 and MIME headers, accessing - subparts of MIME messages, encoding and decoding Base64 and - Quoted-Printable, etc. - </para> - - <para> - <classname>CamelTransport</classname> includes methods for - delivering messages. While the abstract - <function>CamelTransport::send</function> method takes a - <classname>CamelMedium</classname>, its subclasses may only be - able to deliver messages of specific - <classname>CamelMedium</classname> subclasses. For instance, - <classname>CamelSendmailTransport</classname> requires a - <classname>CamelMimeMessage</classname>, because it needs a - message that includes a "To:" header. A hypothetical - <classname>CamelNNTPTransport</classname> would need a - <classname>CamelNewsMessage</classname>, which would have a - "Newsgroups:" header. - </para> - - <para> - The content of messages are referred to using - <classname>CamelStream</classname> and its subclasses. In the - case of an mbox-based store, the - <classname>CamelStream</classname> would abstract the operation - of reading the correct section of the mbox file. For IMAP, - reading off the <classname>CamelStream</classname> might result - in commands being issued to the remote IMAP server and data - being read off a socket. - </para> - - <para> - The final major class in &Camel; is - <classname>CamelException</classname>, which is used to - propagate information about errors. Many methods take a - <classname>CamelException</classname> 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. - </para> - </sect1> - - <sect1 id="classes"> - <title>Major Subcomponents</title> - - <sect2 id="store"> - <title>The Message Store</title> - - <para> - A <classname>CamelStore</classname> inherits the ability to - connect and authenticate to a service from its parent class, - <classname>CamelService</classname>. It then adds the ability - to retrieve folders. A store must contain at least one folder, - which can be retrieved with - <function>CamelStore::get_default_folder</function>. There are - also methods to retrieve the "top-level" folder (for - hieararchical stores), and to retrieve an arbitrary folder by - name. - </para> - - <para> - All <classname>CamelFolder</classname>s must implement certain - core operations, most notably generating a summary and - retrieving and deleting messages. A - <classname>CamelFolder</classname> must assign a permanently - unique identifier to each message it contains. Messages can - then be retrieved via - <function>CamelFolder::get_message_by_uid</function>. Alternately, - within a single mail-reading session, messages can be referred - to by their linear position within the store using - <function>CamelFolder::get_message_by_number</function>. - </para> - - <para> - Folders must also implement the - <function>get_parent_folder</function> and - <function>list_subfolders</function> 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). - </para> - - <para> - Folders that support searching can define the - <function>search_by_expression</function> 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. - </para> - </sect2> - - <sect2 id="messages"> - <title>Messages</title> - - <para> - As mentioned before, messages are represented by subclasses of - <classname>CamelMedium</classname>. - <classname>CamelMedium</classname> itself is a subclass of - <classname>CamelDataWrapper</classname>, a generic class for - connecting a typed data source to a data sink. - <classname>CamelMedium</classname> adds the concept of message - headers versus message body. - (<classname>CamelDataWrapper</classname> has one other - important subclass, <classname>CamelMultipart</classname>, - which is used to provide separate access to the multiple - independent parts of a multipart MIME type.) - <classname>CamelMedium</classname>'s subclasses provide more - specialized handling of various headers: - <classname>CamelMimePart</classname> adds special handling for - the &ldquot;Content-*&rdquot; headers in MIME messages, and - its subclass <classname>CamelMimeMessage</classname> adds - handling for the RFC822 headers. - </para> - - <graphic format="gif" fileref="mimemessage"></graphic> - - <para> - Consider a message with two parts: a text part (in both plain - text and HTML), and an attached image: - - <programlisting> - - 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-- - </programlisting> - - <para> - In &Camel;, this would be represented as follows: - </para> - - <graphic fileref="samplemsg"></graphic> - </sect2> - - <sect2 id="streams"> - <title>Streams</title> - - <para> - Streams are a generic data transport layer. Two basic stream - classes are <classname>CamelStreamFs</classname>, for - reading and writing files, and - <classname>CamelStreamMem</classname>, for reading from and - writing to objects that are already in memory. - </para> - - <para> - 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. - </para> - </sect2> - -</article> diff --git a/help/white-papers/mail/ibex.sgml b/help/white-papers/mail/ibex.sgml deleted file mode 100644 index dcb8f5ca4b..0000000000 --- a/help/white-papers/mail/ibex.sgml +++ /dev/null @@ -1,158 +0,0 @@ -<!doctype article PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [ -<!entity Evolution "<application>Evolution</application>"> -<!entity Camel "Camel"> -<!entity Ibex "Ibex"> -]> - -<article class="whitepaper" id="ibex"> - - <artheader> - <title>Ibex: an Indexing System</title> - - <authorgroup> - <author> - <firstname>Dan</firstname> - <surname>Winship</surname> - <affiliation> - <address> - <email>danw@helixcode.com</email> - </address> - </affiliation> - </author> - </authorgroup> - - <copyright> - <year>2000</year> - <holder>Helix Code, Inc.</holder> - </copyright> - - </artheader> - - <sect1 id="introduction"> - <title>Introduction</title> - - <para> - &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. - </para> - </sect1> - - <sect1 id="goals"> - <title>Design Goals and Requirements for Ibex</title> - - <para> - The design of &Ibex; is based on a number of requirements. - - <itemizedlist> - <listitem> - <para> - 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. - </para> - </listitem> - - <listitem> - <para> - 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. - </para> - - <para> - 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. - </para> - </listitem> - - <listitem> - <para> - 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. - </para> - </listitem> - - <listitem> - <para> - 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. - </para> - </listitem> - - <listitem> - <para> - 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. - </para> - </listitem> - </itemizedlist> - - <para> - While there are a number of existing indexing systems, none of - them met all (or even most) of our requirements. - </para> - </sect1> - - <sect1 id="implementation"> - <title>The Implementation</title> - - <para> - &Ibex; is still young, and many of the details of the current - implementation are not yet finalized. - </para> - - <para> - 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 <application>gzip</application> can compress an - index file to about half its size, so we can clearly do better.) - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect1> -</article> diff --git a/help/white-papers/widgets/e-table.sgml b/help/white-papers/widgets/e-table.sgml deleted file mode 100644 index 5ff4faf2ae..0000000000 --- a/help/white-papers/widgets/e-table.sgml +++ /dev/null @@ -1,279 +0,0 @@ -<!doctype article PUBLIC "-//Davenport//DTD DocBook V3.0//EN" [ -<!entity Evolution "<application>Evolution</application>"> -<!entity ETable "<classname>ETable</classname>"> -<!entity ETableModel "<classname>ETableModel</classname>"> -<!entity ETableSimple "<classname>ETableSimple</classname>"> -<!entity ETableHeader "<classname>ETableHeader</classname>"> -<!entity ETableSpecification "<classname>ETableSpecification</classname>"> -<!entity ETableCol "<classname>ETableCol</classname>"> -]> - -<article class="whitepaper" id="e-table"> - - <artheader> - <title>The ETable Widget</title> - - <authorgroup> - <author> - <firstname>Chris</firstname> - <surname>Lahey</surname> - <affiliation> - <address> - <email>clahey@helixcode.com</email> - </address> - </affiliation> - </author> - <author> - <firstname>Miguel</firstname> - <surname>de Icaza</surname> - <affiliation> - <address> - <email>miguel@helixcode.com</email> - </address> - </affiliation> - </author> - </authorgroup> - - <copyright> - <year>2000</year> - <holder>Helix Code, Inc.</holder> - </copyright> - - </artheader> - - <sect1 id="introduction"> - <title>Introduction</title> - - <para> - &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. - </para> - - <para> - &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. - </para> - - <para> - &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. - </para> - - <para> - &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. - </para> - - <para> - &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. - </para> - - </sect1> - - <sect1 id="model"> - <title>ETableModel</title> - - <para> - 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. - </para> - - <para> - To use &ETable; you have to create a subclass of the abstract - &ETableModel; class. However, to save you the work of defining - a new <classname>GtkClass</classname> 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. - </para> - - </sect1> - - <sect1 id="columns"> - <title>Columns</title> - - <para> - 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). - </para> - - <para> - &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. - </para> - - <para> - 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 - </para> - - <para> - 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". - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - </sect1> - - <sect1 id="header"> - <title>Header</title> - - <para> - The &ETableHeader; represents the header information for the - table. The &ETableHeader; is used in two different ways. The - first is the in the <structfield>full_header</structfield> - 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;. - </para> - - <para> - 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 - <function>e_table_header_new</function> and - <function>e_table_header_add_col</function>. - </para> - </sect1> - - <sect1 id="layout"> - <title>Layout Specification</title> - - <para> - &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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - 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. - </para> - - <para> - An example &ETableSpecification; follows. - </para> - - <programlisting> - <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> - </programlisting> - - <para> - 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. - </para> - </sect1> - - <sect1 id="conclusion"> - <title>Conclusion</title> - - <para> - 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. - </para> - </sect1> -</article> |
