callisto-debian/evolution
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

more small typo fixes.

Browse Source 
svn path=/trunk/; revision=1438
This commit is contained in:
Michael Meeks
1999-11-26 13:05:15 +00:00
parent a9efae5d56
commit b92f33ed11
3 changed files with 12 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
NEWS
View File

@ -1,7 +1,7 @@
01/Jun/1999
-----------
New developpement document from Giao Nguyen :
New development document from Giao Nguyen :
TITLE: An in-depth look at the virtual folder mechanism
(see devel-docs/query)

12
camel/CODING.STYLE
View File

@ -6,12 +6,12 @@ be sure to follow the same coding style as the intial authors.
Please read the file HACKING in gnumeric and follow the
general guidelines explained in it.
Please take a look at camel source files and try to
imitate the coding style the best possible. We are perfectly
aware that this is not the best and unique style, but it
is absolutely mandatory that Camel is homogeneous.
If you find the current coding style to have some weaknesses,
please contact the authors to discuss this matter.
Please take a look at camel source files and try to exactly
imitate the coding style. We are perfectly aware that this
is not the best and unique style, but it is absolutely
mandatory that Camel is homogeneous. If you find the current
coding style to have some weaknesses, please contact the
authors to discuss this matter.
Thanks.

10
devel-docs/camel/README_AND_TODO.txt
View File

@ -1,4 +1,4 @@
Camel is currently (conceptually) separated in four parts:
Camel is currently (conceptualy) separated in four parts:
* the session handling
* the storage mechanism.
@ -15,13 +15,13 @@ CamelSession is an object used to store some parameters on a user
basis. This can be a permanent (fs based) or volatile
(ram only) storage depending on user preferences.
The session object is, for example, responsible for
remmbering authentication datas during application lifetime.
remembering authentication datas during application lifetime.
It is also responsible for selecting and loading providers
corresponding to protocols. In the case where only one
provider exists for a given protocols, the task is trivial,
provider exists for a given protocol, the task is trivial,
but when multiple providers exist for a given protocol, the
user can choose its prefered one. Given its relationship
with providers, the session objects is also used to instanciate
user can choose their prefered one. Given its relationship
with providers, the session object is also used to instanciate
a store given an URL.
Associated Classes: