7434b2831b
* 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. svn path=/trunk/; revision=3222
131 lines
3.8 KiB
Plaintext
131 lines
3.8 KiB
Plaintext
<!DOCTYPE Book PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"[
|
|
|
|
<!ENTITY PREFACE SYSTEM "preface.sgml">
|
|
<!ENTITY USAGE-SETUP SYSTEM "usage-setup.sgml">
|
|
<!ENTITY USAGE-MAINWINDOW SYSTEM "usage-mainwindow.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 CONFIG-SETUPASSIST SYSTEM "config-setupassist.sgml">
|
|
<!ENTITY CONFIG-PREFS SYSTEM "config-prefs.sgml">
|
|
<!ENTITY CONFIG-SYNC SYSTEM "config-sync.sgml">
|
|
<!ENTITY DEVEL-ACTION SYSTEM "devel-action.sgml">
|
|
<!ENTITY DEVEL-SCRIPT SYSTEM "devel-script.sgml">
|
|
<!ENTITY DEVEL-COMPONENT SYSTEM "devel-component.sgml">
|
|
<!ENTITY APX-GLOSS SYSTEM "apx-gloss.sgml">
|
|
<!ENTITY APX-BUGS SYSTEM "apx-bugs.sgml">
|
|
<!ENTITY APX-AUTHORS SYSTEM "apx-authors.sgml">
|
|
<!ENTITY APX-FDL SYSTEM "apx-fdl.sgml">
|
|
|
|
]>
|
|
|
|
|
|
<!-- Almost every chapter is an entity. Files, Chapter id's, and entity names correspond. APX is for appendix. -->
|
|
<book id="index">
|
|
<bookinfo>
|
|
<title>A User's Guide to Evolution</title>
|
|
<author><firstname>Aaron</firstname><surname>Weber</surname></author>
|
|
<copyright><year>2000</year><holder>Helix Code, Inc.</holder></copyright>
|
|
|
|
<legalnotice>
|
|
<para>
|
|
PUT THE RIGHT LEGALNOTICE IN HERE
|
|
</para>
|
|
</legalnotice>
|
|
|
|
<releaseinfo>
|
|
This is version 0.4 of the Evolution manual.
|
|
</releaseinfo>
|
|
<!-- this is version of manual, not application -->
|
|
|
|
<!-- ########## TO DO LIST: ########### -->
|
|
<!--
|
|
finish content.
|
|
standardize capitalization/formatting of titles, interface and
|
|
component names.
|
|
standardize spelling of buzzwords & techterms like email
|
|
add glossterms and glossary
|
|
standardize on second person, not 1st pers. plural.
|
|
-->
|
|
|
|
</bookinfo>
|
|
|
|
&PREFACE;
|
|
|
|
<part id="usage">
|
|
<title>Using Evolution</title>
|
|
<subtitle>A Guide for Everybody</subtitle>
|
|
<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, as with most of
|
|
Linux, there's more than one way to do things, and you can
|
|
pick whichever method you like best.
|
|
</para>
|
|
</partintro>
|
|
|
|
&USAGE-MAINWINDOW;
|
|
&USAGE-MAIL;
|
|
&USAGE-CONTACT;
|
|
&USAGE-CALENDAR;
|
|
&USAGE-SYNC;
|
|
|
|
</part>
|
|
<part id="config">
|
|
<title>Configuring and Managing Evolution</title>
|
|
<subtitle>A guide for Power Users and Administrators</subtitle>
|
|
<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 hackers to
|
|
"configure" themselves a working system. When we say
|
|
configurable, we mean that although
|
|
<application>Evolution</application> will work perfectly well
|
|
with minimal setup hassle, you can alter its behavior to fit
|
|
your needs with just a little more work.
|
|
</para>
|
|
</partintro>
|
|
|
|
&CONFIG-SETUPASSIST;
|
|
&CONFIG-PREFS;
|
|
&CONFIG-SYNC;
|
|
</part>
|
|
<part id="devel">
|
|
<title>Developing for Evolution</title>
|
|
<subtitle>An Introduction for the Happy Few</subtitle>
|
|
<partintro>
|
|
<para>
|
|
There are three levels of developing for
|
|
<application>Evolution</application>. You can write actions.
|
|
You can write scripts. And you can write full-fledged
|
|
Evolution components. This paragraph will eventually
|
|
desfcribe what that means.
|
|
</para>
|
|
</partintro>
|
|
|
|
&DEVEL-ACTION;
|
|
&DEVEL-SCRIPT;
|
|
&DEVEL-COMPONENT;
|
|
</part>
|
|
&APX-GLOSS;
|
|
&APX-BUGS;
|
|
&APX-AUTHORS;
|
|
&APX-FDL;
|
|
|
|
</book>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|