Removed file. Same. Same. Removed references to devel section. Removed

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.

svn path=/trunk/; revision=3769
This commit is contained in:
Aaron Weber
2000-06-28 00:06:55 +00:00
committed by Aaron Weber
parent 73f9659b91
commit 18f1b73bcb
10 changed files with 4 additions and 192 deletions

View File

@ -1,18 +0,0 @@
<chapter id="devel-actions">
<title>Actions: Making Evolution Behave</title>
<sect1 id="devel-actions-build">
<title>Build Actions</title>
<para>
How to create an action.
</para>
</sect1>
<sect1 id="devel-actions-use">
<title>Using Actions</title>
<para>
How to use an action you or someone else has built.
</para>
</sect1>
</chapter>

View File

@ -1,24 +0,0 @@
<chapter id="devel-component">
<title>Evolution Components</title>
<subtitle> Build your own species </subtitle>
<para>
Explain exactly what an Evolution Component is.
</para>
<sect1 id="devel-component-build">
<title>Building Evolution Components</title>
<para>
Explain how to build them-- what resources are available,
what interfaces exposed.
</para>
</sect1>
<sect1 id="devel-component-use">
<title>Using Additional Evolution Components</title>
<para>
Once you've got one--either you've built it or borrowed it--
you can use it. Here's how.
</para>
</sect1>
</chapter>

View File

@ -1,17 +0,0 @@
<chapter id="devel-scripts" >
<title>Scripting: Making Evolution Sit up and Beg</title>
<sect1 id="devel-scripts-build">
<title>Writing Scripts</title>
<para>
How to write scripts for Evolution.
</para>
</sect1>
<sect1 id="devel-scripts-use">
<title>Using Scripts</title>
<para>
How to use and install scripts for Evolution.
</para>
</sect1>
</chapter>

View File

@ -8,9 +8,6 @@
<!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">
@ -99,24 +96,6 @@ standardize on second person, not 1st pers. plural.
&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 describe
what that means, if the entire part is not phased out of this
manual.
</para>
</partintro>
&DEVEL-ACTION;
&DEVEL-SCRIPT;
&DEVEL-COMPONENT;
</part>
&APX-GLOSS;
&APX-BUGS;
&APX-AUTHORS;

View File

@ -111,7 +111,7 @@
<!-- ************* END DRAFT ONLY PARAGRAPH ************** -->
<para>
This book is divided into three sections. The first section is
This book is divided into two sections. The first section is
a <link linkend="usage">guided tour</link>&mdash; it will
explain how to use <application>Evolution</application>. If
you are new to <application>Evolution</application> or to
@ -119,21 +119,7 @@
section, covering <link linkend="config">configuration</link>,
is targeted at advanced users and administrators. If you are
a network administrator, you may find yourself referring to
this section frequently. The third section is a quick <link
linkend="devel">developer's guide</link>, for power users and
hackers. If you want to add advanced scripting to
<application>Evolution</application>, write your own
embeddable components, or simply want to find out just how
powerful <application>Evolution</application> can be, this is
the section for you.
</para>
<para>
Throughout the book, you'll find examples, tips and warnings
to help you along. Most of them are decent, hardworking
pieces of information, and genuinely try to be helpful. Some
of the tips, entitled <emphasis>Bad Ideas</emphasis>,
are, in fact, out to trick you. Please don't follow their
advice, no matter how appealing it may sound.
this section frequently.
</para>
<formalpara>
<title>Typographical conventions</title>

View File

@ -1,18 +0,0 @@
<chapter id="devel-actions">
<title>Actions: Making Evolution Behave</title>
<sect1 id="devel-actions-build">
<title>Build Actions</title>
<para>
How to create an action.
</para>
</sect1>
<sect1 id="devel-actions-use">
<title>Using Actions</title>
<para>
How to use an action you or someone else has built.
</para>
</sect1>
</chapter>

View File

@ -1,24 +0,0 @@
<chapter id="devel-component">
<title>Evolution Components</title>
<subtitle> Build your own species </subtitle>
<para>
Explain exactly what an Evolution Component is.
</para>
<sect1 id="devel-component-build">
<title>Building Evolution Components</title>
<para>
Explain how to build them-- what resources are available,
what interfaces exposed.
</para>
</sect1>
<sect1 id="devel-component-use">
<title>Using Additional Evolution Components</title>
<para>
Once you've got one--either you've built it or borrowed it--
you can use it. Here's how.
</para>
</sect1>
</chapter>

View File

@ -1,17 +0,0 @@
<chapter id="devel-scripts" >
<title>Scripting: Making Evolution Sit up and Beg</title>
<sect1 id="devel-scripts-build">
<title>Writing Scripts</title>
<para>
How to write scripts for Evolution.
</para>
</sect1>
<sect1 id="devel-scripts-use">
<title>Using Scripts</title>
<para>
How to use and install scripts for Evolution.
</para>
</sect1>
</chapter>

View File

@ -8,9 +8,6 @@
<!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">
@ -99,24 +96,6 @@ standardize on second person, not 1st pers. plural.
&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 describe
what that means, if the entire part is not phased out of this
manual.
</para>
</partintro>
&DEVEL-ACTION;
&DEVEL-SCRIPT;
&DEVEL-COMPONENT;
</part>
&APX-GLOSS;
&APX-BUGS;
&APX-AUTHORS;

View File

@ -111,7 +111,7 @@
<!-- ************* END DRAFT ONLY PARAGRAPH ************** -->
<para>
This book is divided into three sections. The first section is
This book is divided into two sections. The first section is
a <link linkend="usage">guided tour</link>&mdash; it will
explain how to use <application>Evolution</application>. If
you are new to <application>Evolution</application> or to
@ -119,21 +119,7 @@
section, covering <link linkend="config">configuration</link>,
is targeted at advanced users and administrators. If you are
a network administrator, you may find yourself referring to
this section frequently. The third section is a quick <link
linkend="devel">developer's guide</link>, for power users and
hackers. If you want to add advanced scripting to
<application>Evolution</application>, write your own
embeddable components, or simply want to find out just how
powerful <application>Evolution</application> can be, this is
the section for you.
</para>
<para>
Throughout the book, you'll find examples, tips and warnings
to help you along. Most of them are decent, hardworking
pieces of information, and genuinely try to be helpful. Some
of the tips, entitled <emphasis>Bad Ideas</emphasis>,
are, in fact, out to trick you. Please don't follow their
advice, no matter how appealing it may sound.
this section frequently.
</para>
<formalpara>
<title>Typographical conventions</title>