From ef585975d00ddbc021fa9a1181723c67b3223a82 Mon Sep 17 00:00:00 2001 From: Federico Mena Quintero Date: Wed, 29 Nov 2000 16:26:59 +0000 Subject: Added an id for the API reference . Added the FDL . 2000-11-29 Federico Mena Quintero * evolution-devel-guide.sgml: Added an id for the API reference . Added the FDL . 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 . * calendar/public-reference.sgml: Added an id for the . 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. svn path=/trunk/; revision=6715 --- help/devel/ChangeLog | 32 + help/devel/Makefile.am | 42 +- help/devel/calendar/architecture.sgml | 10 +- .../calendar/cal-util/tmpl/cal-component.sgml | 2 +- help/devel/calendar/evolution-calendar.sgml | 32 +- help/devel/calendar/public-reference.sgml | 4 +- help/devel/calendar/reference.sgml | 24 - help/devel/evolution-devel-guide.sgml | 75 ++- help/devel/fdl.sgml | 671 +++++++++++++++++++++ help/devel/preface.sgml | 113 ++++ help/devel/reference.sgml | 45 ++ 11 files changed, 963 insertions(+), 87 deletions(-) delete mode 100644 help/devel/calendar/reference.sgml create mode 100644 help/devel/fdl.sgml create mode 100644 help/devel/preface.sgml create mode 100644 help/devel/reference.sgml (limited to 'help') diff --git a/help/devel/ChangeLog b/help/devel/ChangeLog index 555db7d161..a8b4069d35 100644 --- a/help/devel/ChangeLog +++ b/help/devel/ChangeLog @@ -1,3 +1,35 @@ +2000-11-29 Federico Mena Quintero + + * evolution-devel-guide.sgml: Added an id for the API reference . + Added the FDL . + 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 . + + * calendar/public-reference.sgml: Added an id for the . + 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 * evolution-devel-guide.sgml: Made the toplevel id be diff --git a/help/devel/Makefile.am b/help/devel/Makefile.am index 0d3cec5a1c..0dd533057e 100644 --- a/help/devel/Makefile.am +++ b/help/devel/Makefile.am @@ -10,28 +10,42 @@ HTML_DIR=$(datadir)/gnome/html TARGET_DIR=$(HTML_DIR)/$(DOC_MODULE) -evolution_devel_guidedir = $(HTML_DIR) -evolution_devel_guide_DATA = \ - evolution-devel-guide.html +# Add your toplevel files here -content_files = \ - evolution-devel-guide.sgml +content_files = \ + evolution-devel-guide.sgml \ + fdl.sgml \ + preface.sgml \ + reference.sgml -EXTRA_DIST = \ - $(evolution_devel_guide_DATA) \ +# Add your module's hand-written and auto-generated files here; these +# are used for dependency tracking. + +local_entities = \ + 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 + +EXTRA_DIST = \ $(content_files) +all: evolution-devel-guide.html + if ENABLE_GTK_DOC -evolution-devel-guide.html: html/book1.html - -cd $(srcdir) && cp html/book1.html evolution-devel-guide.html +evolution-devel-guide.html: html/index.html + -cd $(srcdir) && cp html/index.html evolution-devel-guide.html else evolution-devel-guide.html: endif -html/book1.html: $(content-files) - $(MAKE) html - -html: +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) @@ -60,5 +74,3 @@ install-data-local: dist-hook: mkdir $(distdir)/html -cp $(srcdir)/html/*.html $(srcdir)/html/*.css $(distdir)/html - -.PHONY: html diff --git a/help/devel/calendar/architecture.sgml b/help/devel/calendar/architecture.sgml index 08e4c82b35..f121144d29 100644 --- a/help/devel/calendar/architecture.sgml +++ b/help/devel/calendar/architecture.sgml @@ -2,10 +2,10 @@ Architecture of the Calendar - This chapter gives an overview of the Evolution Calendar + This chapter gives an overview of the &Evolution; Calendar architecture. It describes the model/view split of the calendar - into a personal calendar server, or PCS, and the GUI clients - that appear inside the Evolution shell. + into a personal calendar server, or &PCS;, and the GUI clients + that appear inside the &Evolution; Shell. @@ -14,7 +14,7 @@ Model/View Separation - Like other base components in Evolution, the calendar + 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, @@ -30,7 +30,7 @@ - Evolution puts the calendar storage in a daemon called the + &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 diff --git a/help/devel/calendar/cal-util/tmpl/cal-component.sgml b/help/devel/calendar/cal-util/tmpl/cal-component.sgml index 2f800e583f..56a04b02a0 100644 --- a/help/devel/calendar/cal-util/tmpl/cal-component.sgml +++ b/help/devel/calendar/cal-util/tmpl/cal-component.sgml @@ -95,7 +95,7 @@ RFC 2445 iCalendar component object. These values are used as identifiers for #ETable columns. These - are used by the calendar GUI code in Evolution. + are used by the calendar GUI code in &Evolution;. @CAL_COMPONENT_FIELD_CATEGORIES: Component's list of categories. diff --git a/help/devel/calendar/evolution-calendar.sgml b/help/devel/calendar/evolution-calendar.sgml index f3936d9bbc..82015689ec 100644 --- a/help/devel/calendar/evolution-calendar.sgml +++ b/help/devel/calendar/evolution-calendar.sgml @@ -1,4 +1,4 @@ - + @@ -13,30 +13,30 @@ - Developing Applications for the Evolution Calendar + Developing Applications with the &Evolution; Calendar - This part of the Evolution Developer's Guide describes how to - write applications for the Evolution Calendar by using its - public interfaces. The Evolution Calendar exports its + 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. - You should read this part of the Evolution Developer's guide + You should read this part of the &Evolution; Developer's guide if you intend to write client applications that use the - functionality of the Evolution Calendar. - - - - This part does not describe the internal interfaces of the - Evolution Calendar; for that you should read the Evolution - Internals Guide. You should only need to read that guide if - you are interested in the way the calendar works internally or - if you want to make changes directly to the Evolution Calendar - code. + 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. diff --git a/help/devel/calendar/public-reference.sgml b/help/devel/calendar/public-reference.sgml index f8aa6e848d..b880bd2972 100644 --- a/help/devel/calendar/public-reference.sgml +++ b/help/devel/calendar/public-reference.sgml @@ -1,10 +1,10 @@ - + Calendar Public API Reference This part presents the class and function reference for the - public APIs of the different components of the Evolution + public APIs of the different components of the &Evolution; Calendar. diff --git a/help/devel/calendar/reference.sgml b/help/devel/calendar/reference.sgml deleted file mode 100644 index f8aa6e848d..0000000000 --- a/help/devel/calendar/reference.sgml +++ /dev/null @@ -1,24 +0,0 @@ - - Calendar Public API Reference - - - - This part presents the class and function reference for the - public APIs of the different components of the Evolution - Calendar. - - - - &CalClient; - &CalComponent; - &cal-util; - &cal-recur; - &timeutil; - - - diff --git a/help/devel/evolution-devel-guide.sgml b/help/devel/evolution-devel-guide.sgml index 9db8f1bdf0..d0988eb1aa 100644 --- a/help/devel/evolution-devel-guide.sgml +++ b/help/devel/evolution-devel-guide.sgml @@ -1,19 +1,27 @@ - - - - - - - - -PCS"> -libical"> + + + + + + + + + + + + + +Evolution"> +Wombat"> +Camel"> +PCS"> +libical"> ]> - Evolution Developer's Guide + &Evolution; Developer's Guide @@ -25,26 +33,45 @@ 2000 Helix Code, Inc. + + + + 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 no Invariant + Sections, no Front-Cover Texts, and no Back-Cover Texts. You + may obtain a copy of the GNU Free Documentation + License from the Free Software Foundation by + visiting their Web + site or by writing to: Free Software Foundation, Inc., + 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. + + + + Many of the names used by companies to distinguish their + products and services are claimed as trademarks. Where those + names appear in any GNOME documentation, and those trademarks + are made aware to the members of the GNOME Documentation + Project, the names have been printed in caps or initial caps. + + + + + &preface; + &evolution-calendar; - - Evolution Public API Reference + &evolution-reference; - - - This part presents the class and function reference for the - different libraries and interfaces that Evolution provides. - Classes are described together with their methods; individual - functions are grouped by functional group. - - + - &calendar-reference; - + &FDL; diff --git a/help/devel/fdl.sgml b/help/devel/fdl.sgml new file mode 100644 index 0000000000..817adbdbb7 --- /dev/null +++ b/help/devel/fdl.sgml @@ -0,0 +1,671 @@ + + + + + + Version 1.1, March 2000 + + + 2000Free Software Foundation, Inc. + + + +
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. + + + + GNU Free Documentation License + + + 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 + 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. + + + + + 7. AGGREGATION WITH INDEPENDENT WORKS + + A compilation of the Document or its derivatives with + other separate and independent documents or works, in or on a + volume of a storage or distribution medium, does not as a whole + count as a Modified Version + of the Document, provided no compilation copyright is claimed + for the compilation. Such a compilation is called an + aggregate, and this License does not apply to the + other self-contained works thus compiled with the Document , on + account of their being thus compiled, if they are not themselves + derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these + copies of the Document, then if the Document is less than one + quarter of the entire aggregate, the Document's Cover Texts may + be placed on covers that surround only the Document within the + aggregate. Otherwise they must appear on covers around the whole + aggregate. + + + + + 8. TRANSLATION + + Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with + translations requires special permission from their copyright + holders, but you may include translations of some or all + Invariant Sections in addition to the original versions of these + Invariant Sections. You may include a translation of this + License provided that you also include the original English + version of this License. In case of a disagreement between the + translation and the original English version of this License, + the original English version will prevail. + + + + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document except as expressly + provided for under this License. Any other attempt to copy, + modify, sublicense or distribute the Document is void, and will + automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this + License will not have their licenses terminated so long as such + parties remain in full compliance. + + + + + 10. FUTURE REVISIONS OF THIS LICENSE + + The Free Software + Foundation may publish new, revised versions of the GNU + Free Documentation License from time to time. Such new versions + will be similar in spirit to the present version, but may differ + in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. + + + + Each version of the License is given a distinguishing version + number. If the Document + specifies that a particular numbered version of this License + or any later version applies to it, you have the + option of following the terms and conditions either of that + specified version or of any later version that has been + published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, + you may choose any version ever published (not as a draft) by + the Free Software Foundation. + + + + + Addendum + + To use this License in a document you have written, include a copy of + the License in the document and put the following copyright and + license notices just after the title page: + + +
+ + Copyright © YEAR YOUR NAME. + + + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the + Free Software Foundation; with the Invariant Sections being LIST + THEIR TITLES, with the Front-Cover Texts being LIST, + and with the Back-Cover + Texts being LIST. A copy of the license is included in + the section entitled GNU Free Documentation + License. + +
+ + + If you have no Invariant + Sections, write with no Invariant Sections + instead of saying which ones are invariant. If you have no + Front-Cover Texts, write + no Front-Cover Texts instead of + Front-Cover Texts being LIST; likewise for Back-Cover Texts. + + + + If your document contains nontrivial examples of program code, + we recommend releasing these examples in parallel under your + choice of free software license, such as the GNU General Public + License, to permit their use in free software. + + + + + + + + + diff --git a/help/devel/preface.sgml b/help/devel/preface.sgml new file mode 100644 index 0000000000..fdaa824a8b --- /dev/null +++ b/help/devel/preface.sgml @@ -0,0 +1,113 @@ + + Introduction + + + 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. + + + + If you are an end-user of &Evolution; you do not need to read + this guide; please read the &Evolution; User's Guide instead. + + + + This guide contains the information you need to know to do the + following: + + + + + Write applications that use &Evolution;'s data + repositories via the &Wombat; personal information server. + Examples of this would be a GNOME + Panel applet that displays today's + appointments, or a telephone dialer application that uses + the contents of the &Evolution; Addressbook. + + + + + + Write applications that use the &Camel; mail library. + This includes extending &Evolution;'s own mail component + to perform additional functions. + + + + + + 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. + + + + + + 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. + + + + + + Modify the core &Evolution; code to add new features or + change its architecture. + + + + + + + Organization of this Guide + + + 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. + + + + 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. + + + + &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. + + + + + diff --git a/help/devel/reference.sgml b/help/devel/reference.sgml new file mode 100644 index 0000000000..3773821a0f --- /dev/null +++ b/help/devel/reference.sgml @@ -0,0 +1,45 @@ + + &Evolution; API Reference + + + + This part presents the class and function reference for the + different libraries and interfaces that &Evolution; provides. + Classes are described together with their methods; individual + functions are grouped by functional group. + + + + &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. + + + + 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. + + + + &calendar-public-reference; + + + -- cgit v1.2.3