diff --git a/phpgwapi/doc/contacts.readme.txt b/phpgwapi/doc/contacts.readme.txt index 92ec92020a..aba459c3f1 100644 --- a/phpgwapi/doc/contacts.readme.txt +++ b/phpgwapi/doc/contacts.readme.txt @@ -1,6 +1,6 @@ /**************************************************************************\ - * phpGroupWare API - Contacts class documentation * - * This file written by Miles Lott * + * eGroupWare API - Contacts class documentation * + * This file written by Miles Lott * * -------------------------------------------------------------------------* * This library is free software; you can redistribute it and/or modify it * * under the terms of the GNU Lesser General Public License as published by * diff --git a/phpgwapi/doc/cvs.html b/phpgwapi/doc/cvs.html index 9af82aea8d..9b803096d9 100755 --- a/phpgwapi/doc/cvs.html +++ b/phpgwapi/doc/cvs.html @@ -2,7 +2,7 @@ -phpgroupware.org +egroupware.org @@ -14,7 +14,7 @@ - +
@@ -22,16 +22,16 @@ eGroupWare XML-RPC/SOAP Methodology
-

You can get your own copy of the phpGroupWare CVS tree by using a CVS client from your own system. If you don't already +

You can get your own copy of the eGroupWare CVS tree by using a CVS client from your own system. If you don't already have one, you can find one at http://www.cvshome.org. You can get your own copy of the tree with the commands:

-
cvs -d:pserver:anonymous@cvs.phpgroupware.sourceforge.net:/cvsroot/phpgroupware login
+
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/egroupware login

When it asks you for a password, simply press the Enter key

Then type:

-
cvs -z3 -d:pserver:anonymous@cvs.phpgroupware.sourceforge.net:/cvsroot/phpgroupware co [ -r <TAG> ] <MODULE>
+
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/egroupware co [ -r <TAG> ] <MODULE>

This will create a <MODULE> directory in your current directory. It may take a bit of time, especially if your network connection @@ -55,59 +55,30 @@ wish to checkout. At this time, tags that would be of use are:

Valid module names are:

- - + + - - - - - - - - - - - - - - - - - - - - - + + - - - - + - - - - + - - - -
phpgroupware * The core phpGroupWare libraries
phpgwapi * The phpGroupWare API
egroupware * The core eGoupWare libraries
phpgwapi * The eGoupWare API
addressbook * an addressbook
admin * Administration module
bookkeeping Personal finance manager
bookmarks Bookmark manager
calendar * personal/Group calendar
cart ?
cdb Contact Database Manager (work in progress)
chat chat system
chora CVS repository front-end
comic Comic Strip system
cron * cron files for administrative uses
dj MP3 list manager (Indirectly interfacing with icecast)
eldaptdir LDAP Browser
email * EMAIL reader (interfaces to IMAP/POP3)
filemanager * Personal/Group Filemanagement
files * Simple Structure for filemanager system
forum A forum system
ftp web based FTP client
headlines news site headline system
hr Human Resource module
inv Invoice system
manual * online phpGroupWare manual
mediadb Media database tracking system
news_admin create system wide news for your phpGroupWare installation
nntp * Network News Reader
notes * create personal/group notes
phonelog * Phonelog system
bookkeeping Personal finance manager
phpgroupware * The core phpGroupWare libraries
phpgwapi * The phpGroupWare API
phpgwnetsaint Netsaint viewer
manual * online eGoupWare manual
news_admin create system wide news for your eGoupWare installation
polls * create/administer polls
preferences * Manage phpGroupWare user preferences
projectbilling ?
projectdelivery ?
projecthours ?
preferences * Manage eGoupWare user preferences
projects ?
projectstatistics?
rbs Remote Booking System (soon to be merged into calendar)
setup * phpGroupWare setup
squirrelmail * EMAIL reader (interfaces to IMAP/POP3)
setup * eGoupWare setup
stocks stock info grabber
todo * TO-DO List manger
transy * Language translation management
tts Trouble Ticket System
wap Wireless Application Protocol templates
weather weather information grabber
-

You should probably check out phpgroupware first, then -cd phpgroupware, and then check out any additional modules that you +

You should probably check out egroupware first, then +cd egroupware, and then check out any additional modules that you want.
We suggest at a minimum that you install those modules that mare marked with an "*".

Please keep in mind that the CVS '-r HEAD' version may not always work correctly, diff --git a/phpgwapi/doc/vfs/vfs-1.html b/phpgwapi/doc/vfs/vfs-1.html index 1e696fb082..455d8fe649 100644 --- a/phpgwapi/doc/vfs/vfs-1.html +++ b/phpgwapi/doc/vfs/vfs-1.html @@ -14,7 +14,7 @@ Previous

1. Introduction and Purpose

-

The latest version of the VFS for phpGroupWare combines actual +

The latest version of the VFS for eGroupWare combines actual file system manipulation with fully integrated database support. It features nearly transparent handling of files and directories, as well as files inside and outside the virtual root. This document diff --git a/phpgwapi/doc/vfs/vfs-2.html b/phpgwapi/doc/vfs/vfs-2.html index 2bbb95d2ab..5a32d208a4 100644 --- a/phpgwapi/doc/vfs/vfs-2.html +++ b/phpgwapi/doc/vfs/vfs-2.html @@ -23,7 +23,7 @@ An example:

 $GLOBALS['phpgw_info']['flags'] = array(
-     'currentapp' => 'phpwebhosting',
+     'currentapp' => 'filemanaer',
      'noheader' => False,
      'noappheader' => False,
      'enable_vfs_class' => True,
@@ -99,8 +99,8 @@ to use the virtual paths. For example, instead of using:

 

 
 $GLOBALS['phpgw']->vfs->cp (array(
-     'from' => '/var/www/phpgroupware/files/home/user/file1',
-     'to' => '/var/www/phpgroupware/files/home/user/file2',
+     'from' => '/var/www/egroupware/files/home/user/file1',
+     'to' => '/var/www/egroupware/files/home/user/file2',
      'relatives' => array(
           RELATIVE_NONE|VFS_REAL,
           RELATIVE_NONE|VFS_REAL
diff --git a/phpgwapi/doc/vfs/vfs-3.html b/phpgwapi/doc/vfs/vfs-3.html
index 054d029f94..2276185cb7 100644
--- a/phpgwapi/doc/vfs/vfs-3.html
+++ b/phpgwapi/doc/vfs/vfs-3.html
@@ -71,8 +71,8 @@ $p = $GLOBALS['phpgw']->vfs->path_parts (array(
 
  • $p->fake_leading_dirs - /home/jason/dir
    • 
 
  • $p->fake_extra_path - home/jason/dir
    • 
 
  • $p->fake_name - file
    • 
-
  • $p->real_full_path - /var/www/phpgroupware/files/home/jason/dir/file
    • 
-
  • $p->real_leading_dirs - /var/www/phpgroupware/files/home/jason/dir
+
  • $p->real_full_path - /var/www/egroupware/files/home/jason/dir/file
    • 
+
  • $p->real_leading_dirs - /var/www/egroupware/files/home/jason/dir
  
    • 
 
  • $p->real_extra_path - home/jason/dir
    • 
 
  • $p->real_name - file
    • 
@@ -89,7 +89,7 @@ with it using different paths and relativities as we explore relativity.
    
 
     3.2 cd ()
 
    
 
-
    Part of the overall goal for the VFS in phpGroupWare is to give
+
    Part of the overall goal for the VFS in eGroupWare is to give
 the user a seamless experience during their session. For example,
 if they upload a file using a file manager to the directory /home/my_group/project1,
 and then go to download an email attachment, the default directory
diff --git a/phpgwapi/doc/vfs/vfs-4.html b/phpgwapi/doc/vfs/vfs-4.html
index 38117da8a3..973cce2867 100644
--- a/phpgwapi/doc/vfs/vfs-4.html
+++ b/phpgwapi/doc/vfs/vfs-4.html
@@ -29,7 +29,7 @@ right off the bat to keep things neater.
    
 
    One of the design challenges for a Virtual File System is to
 try to figure out whether the calling application is referring to
 a file inside or outside the virtual root, and if inside, exactly
-where. To solve this problem, the phpGroupWare VFS uses RELATIVE
+where. To solve this problem, the eGoupWare VFS uses RELATIVE
 defines that are used in bitmasks passed to each function. The result
 is that any set of different relativities can be used in combination
 with each other. Let's look at a few examples. Say you want to move
@@ -59,12 +59,12 @@ MOVE "$fakebase/jason/logo.png" TO "$fakebase/my_group/project1/logo.png"
 
    and the actual file system call would be:
    
 
    
 
    -rename ('/var/www/phpgroupware/files/home/jason/logo.php', '/var/www/phpgroupware/files/home/my_group/project1/logo.png');
+rename ('/var/www/egroupware/files/home/jason/logo.php', '/var/www/egroupware/files/home/my_group/project1/logo.png');
 
    
 
    
 
    Those used to the old VFS will note that you do not have to translate
 the path beforehand. Let's look at another example. Suppose you were
-moving an email attachment stored in phpGroupWare's temporary directory
+moving an email attachment stored in eGoupWare's temporary directory
 to the 'attachments' directory within the user's home directory (we're
 assuming the attachments directory exists). Note that the temporary
 directory is outside the virtual root.
    
@@ -92,7 +92,7 @@ like this (keep in mind that $randomdir and $randomfile
 are just random strings):
    
 
    
 
    -rename ('/var/www/phpgroupware/tmp/0ak5adftgh7/jX42sC9M', '/var/www/phpgroupware/files/home/jason/attachments/actual_name.ext');
+rename ('/var/www/egroupware/tmp/0ak5adftgh7/jX42sC9M', '/var/www/egroupware/files/home/jason/attachments/actual_name.ext');
 
    
 
    
 
    Of course you don't have to know that, nor should you be concerned
diff --git a/phpgwapi/doc/vfs/vfs-5.html b/phpgwapi/doc/vfs/vfs-5.html
index e5cad3ba7f..4c78cffbb8 100644
--- a/phpgwapi/doc/vfs/vfs-5.html
+++ b/phpgwapi/doc/vfs/vfs-5.html
@@ -15,7 +15,7 @@
 
     5. Function reference
    
 
 
    To view the function reference for the VFS, use the doc/inlinedocparser.php
-script that comes with phpGroupWare, ie 
+script that comes with eGroupWare, ie 
 http://localhost/doc/inlinedocparser.php?fn=class.vfs_sql.inc.php.
    
 
    
 Next
diff --git a/phpgwapi/doc/vfs/vfs-7.html b/phpgwapi/doc/vfs/vfs-7.html
index 63027f449b..ae560d7d30 100644
--- a/phpgwapi/doc/vfs/vfs-7.html
+++ b/phpgwapi/doc/vfs/vfs-7.html
@@ -33,9 +33,7 @@ quotes, and GLOBALS.
    
 
    7.3 Contributing
 
    
 
-
    Contributions are always welcome. Please send to the current
 maintainer, Jason Wies, 
-zone@phpgroupware.org.
    
 
    
 Next
 Previous
diff --git a/phpgwapi/doc/vfs/vfs.html b/phpgwapi/doc/vfs/vfs.html
index 7552617479..341bc57293 100644
--- a/phpgwapi/doc/vfs/vfs.html
+++ b/phpgwapi/doc/vfs/vfs.html
@@ -17,7 +17,7 @@ Contents
 
    Jason Wies
    June 2001, February 2002
 
    
 The VFS, or Virtual File System, handles all file system activity
- for phpGroupWare.
+ for eGroupWare.
 
    
 
    
 
    1. Introduction and Purpose
    
diff --git a/phpgwapi/doc/vfs/vfs.lyx b/phpgwapi/doc/vfs/vfs.lyx
index 4ebce166a2..69ff0a0068 100644
--- a/phpgwapi/doc/vfs/vfs.lyx
+++ b/phpgwapi/doc/vfs/vfs.lyx
@@ -45,7 +45,7 @@ Introduction and Purpose
 
 \layout Standard
 
-The latest version of the VFS for phpGroupWare combines actual file system
+The latest version of the VFS for eGoupWare combines actual file system
  manipulation with fully integrated database support.
  It features nearly transparent handling of files and directories, as well
  as files inside and outside the virtual root.
@@ -210,10 +210,10 @@ can
 $GLOBALS['phpgw']->vfs->cp (array(
 \layout Verbatim
 
-     'from' => '/var/www/phpgroupware/files/home/user/file1',
+     'from' => '/var/www/egroupware/files/home/user/file1',
 \layout Verbatim
 
-     'to' => '/var/www/phpgroupware/files/home/user/file2',
+     'to' => '/var/www/egroupware/files/home/user/file2',
 \layout Verbatim
 
      'relatives' => array(
@@ -392,10 +392,10 @@ $p->fake_extra_path - home/jason/dir
 $p->fake_name - file
 \layout Itemize
 
-$p->real_full_path - /var/www/phpgroupware/files/home/jason/dir/file
+$p->real_full_path - /var/www/egroupware/files/home/jason/dir/file
 \layout Itemize
 
-$p->real_leading_dirs - /var/www/phpgroupware/files/home/jason/dir 
+$p->real_leading_dirs - /var/www/egroupware/files/home/jason/dir 
 \layout Itemize
 
 $p->real_extra_path - home/jason/dir
@@ -430,7 +430,7 @@ cd ()
 
 \layout Standard
 
-Part of the overall goal for the VFS in phpGroupWare is to give the user
+Part of the overall goal for the VFS in eGoupWare is to give the user
  a seamless experience during their session.
  For example, if they upload a file using a file manager to the directory
  /home/my_group/project1, and then go to download an email attachment, the
@@ -538,7 +538,7 @@ What is it and how does it work?
 One of the design challenges for a Virtual File System is to try to figure
  out whether the calling application is referring to a file inside or outside
  the virtual root, and if inside, exactly where.
- To solve this problem, the phpGroupWare VFS uses RELATIVE defines that
+ To solve this problem, the eGoupWare VFS uses RELATIVE defines that
  are used in bitmasks passed to each function.
  The result is that any set of different relativities can be used in combination
  with each other.
@@ -608,14 +608,14 @@ $fakebase/my_group/project1/logo.png
 and the actual file system call would be:
 \layout Verbatim
 
-rename ('/var/www/phpgroupware/files/home/jason/logo.php', '/var/www/phpgroupware
+rename ('/var/www/egroupware/files/home/jason/logo.php', '/var/www/egroupware
 /files/home/my_group/project1/logo.png');
 \layout Standard
 
 Those used to the old VFS will note that you do not have to translate the
  path beforehand.
  Let's look at another example.
- Suppose you were moving an email attachment stored in phpGroupWare's temporary
+ Suppose you were moving an email attachment stored in eGoupWare's temporary
  directory to the 'attachments' directory within the user's home directory
  (we're assuming the attachments directory exists).
  Note that the temporary directory is 
@@ -668,7 +668,7 @@ outside
  $randomdir and $randomfile are just random strings):
 \layout Verbatim
 
-rename ('/var/www/phpgroupware/tmp/0ak5adftgh7/jX42sC9M', '/var/www/phpgroupware
+rename ('/var/www/egroupware/tmp/0ak5adftgh7/jX42sC9M', '/var/www/egroupware
 /files/home/jason/attachments/actual_name.ext');
 \layout Standard
 
@@ -878,7 +878,7 @@ Function reference
 \layout Standard
 
 To view the function reference for the VFS, use the doc/inlinedocparser.php
- script that comes with phpGroupWare, ie 
+ script that comes with eGoupWare, ie 
 \begin_inset LatexCommand \url[http://localhost/doc/inlinedocparser.php?fn=class.vfs_sql.inc.php]{http://localhost/doc/inlinedocparser.php?fn=class.vfs_sql.inc.php}
 
 \end_inset 
@@ -1110,7 +1110,7 @@ Contributing
 
 Contributions are always welcome.
  Please send to the current maintainer, Jason Wies, 
-\begin_inset LatexCommand \url[zone@phpgroupware.org]{mailto:zone@phpgroupware.org}
+
 
 \end_inset 
 
diff --git a/phpgwapi/doc/vfs/vfs.sgml b/phpgwapi/doc/vfs/vfs.sgml
index a0e8276bb4..265a6c96ec 100644
--- a/phpgwapi/doc/vfs/vfs.sgml
+++ b/phpgwapi/doc/vfs/vfs.sgml
@@ -13,12 +13,12 @@ June 2001, February 2002
 
 
 The VFS, or Virtual File System, handles all file system activity
- for phpGroupWare.
+ for eGoupWare.
 
 
 Introduction and Purpose
    		phpGroupWare XML-RPC/SOAP Methodology
    Business layer requests

    Once a successful login return packet has been received and sessionid/kp3 have been extracted, every subsequent packet sent to the phpgroupware server must be preceded by an Authorization header. Here is a sample header: +> Once a successful login return packet has been received and sessionid/kp3 have been extracted, every subsequent packet sent to the egroupware server must be preceded by an Authorization header. Here is a sample header:

    eGoupWare XML-RPC/SOAP Methodology
    POST /phpgroupware/xmlrpc.php HTTP/1.0
+>POST /egroupware/xmlrpc.php HTTP/1.0
 User-Agent: PHP XMLRPC 1.0
 Host: my.local.host
 Authorization: Basic ZDgxNDIyZDRkYjg5NDEyNGNiMzZlMDhhZTdlYzAxZmY6NTU3YzkyYjBmNGE4ZDVlOTUzMzI2YmU2OTQyNjM3YjQ=
@@ -293,4 +293,4 @@ VALIGN="top"
 >
\ No newline at end of file
+>
diff --git a/phpgwapi/doc/xmlrpc/phpgw_server-2.html b/phpgwapi/doc/xmlrpc/phpgw_server-2.html
index 115172a3c4..8a801424fe 100644
--- a/phpgwapi/doc/xmlrpc/phpgw_server-2.html
+++ b/phpgwapi/doc/xmlrpc/phpgw_server-2.html
@@ -8,7 +8,7 @@ NAME="GENERATOR"
 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
 ">
    		phpGroupWare XML-RPC/SOAP Methodology
    More to come...

    Documenting every single call will be difficult, but should be done. In leiu of this, please see the class.bo{APPNAME}.inc.php files in each application/inc directory in the phpgroupware cvs. In this file will be a list_methods() function, which returns the information to the server about input/output structure for each call. If the file does not have this function, then it is not yet workable via this interface. As for the actual functions, they are also in this file. Generally, they will all accept associative array input and return same, but not always. This code is in flux, have fun. +> Documenting every single call will be difficult, but should be done. In leiu of this, please see the class.bo{APPNAME}.inc.php files in each application/inc directory in the egroupware cvs. In this file will be a list_methods() function, which returns the information to the server about input/output structure for each call. If the file does not have this function, then it is not yet workable via this interface. As for the actual functions, they are also in this file. Generally, they will all accept associative array input and return same, but not always. This code is in flux, have fun.

    \ No newline at end of file +> diff --git a/phpgwapi/doc/xmlrpc/phpgw_server.lyx b/phpgwapi/doc/xmlrpc/phpgw_server.lyx index 34ec92be37..658f90bd75 100644 --- a/phpgwapi/doc/xmlrpc/phpgw_server.lyx +++ b/phpgwapi/doc/xmlrpc/phpgw_server.lyx @@ -354,12 +354,12 @@ Business layer requests \layout Standard Once a successful login return packet has been received and sessionid/kp3 - have been extracted, every subsequent packet sent to the phpgroupware server + have been extracted, every subsequent packet sent to the egroupware server must be preceded by an Authorization header. Here is a sample header: \layout Code -POST /phpgroupware/xmlrpc.php HTTP/1.0 +POST /egroupware/xmlrpc.php HTTP/1.0 \layout Code User-Agent: PHP XMLRPC 1.0 diff --git a/phpgwapi/doc/xmlrpc/phpgw_server.ps b/phpgwapi/doc/xmlrpc/phpgw_server.ps index 6ff4701d76..341ed7b4c1 100644 --- a/phpgwapi/doc/xmlrpc/phpgw_server.ps +++ b/phpgwapi/doc/xmlrpc/phpgw_server.ps @@ -456,10 +456,10 @@ y()396 3202 y()-2 3876 y Ff(2.)34 b(Business)h(la)n(y)o(er)f(requests)396 4044 y Fd(Once)20 b(a)h(successful)f(login)f(return)g(pack)o(et)h(has)g(been)g(recei)n(v) o(ed)e(and)i(sessionid/kp3)f(ha)n(v)o(e)g(been)h(e)o(xtracted,)e(e)n(v) -o(ery)396 4152 y(subsequent)h(pack)o(et)g(sent)h(to)g(the)g(phpgroupw)o +o(ery)396 4152 y(subsequent)h(pack)o(et)g(sent)h(to)g(the)g(egroupw)o (are)c(serv)o(er)j(must)h(be)g(preceded)e(by)h(an)h(Authorization)d (header)-5 b(.)19 b(Here)h(is)396 4259 y(a)h(sample)f(header:)396 -4440 y Fb(POST)44 b(/phpgroupware/xmlrpc.php)d(HTTP/1.0)396 +4440 y Fb(POST)44 b(/egroupware/xmlrpc.php)d(HTTP/1.0)396 4537 y(User-Agent:)i(PHP)i(XMLRPC)e(1.0)396 4634 y(Host:)h (my.local.host)396 4731 y(Authorization:)f(Basic)h (ZDgxNDIyZDRkYjg5NDEyNGNiMzZlMDhhZTdlYz)o(AxZmY6)o(NTU3Y)o(zkyYjB)o diff --git a/phpgwapi/doc/xmlrpc/phpgw_server.sgml b/phpgwapi/doc/xmlrpc/phpgw_server.sgml index e767caf12e..d2246a18cb 100644 --- a/phpgwapi/doc/xmlrpc/phpgw_server.sgml +++ b/phpgwapi/doc/xmlrpc/phpgw_server.sgml @@ -171,10 +171,10 @@ Business layer requests - Once a successful login return packet has been received and sessionid/kp3 have been extracted, every subsequent packet sent to the phpgroupware server must be preceded by an Authorization header. Here is a sample header: + Once a successful login return packet has been received and sessionid/kp3 have been extracted, every subsequent packet sent to the egroupware server must be preceded by an Authorization header. Here is a sample header: -