4. Infastructure

4.1 Overview

phpGroupWare attempts to provide developers with a sound directory structure to work from.
The directory layout may seem complex at first, but after some use, you will see that it is designed to accommidate a large number of applications and functions.

4.2 Directory tree

.-- addressbook
|   `-- images
|   |   `-- navbar.gif
|   `-- inc
|   |   |-- functions.inc.php
|   |   |-- header.inc.php
|   |   `-- footer.inc.php
|   `-- templates
|       `-- default
|-- admin
|   `-- images
|   |   `-- navbar.gif
|   `-- inc
|   |   |-- functions.inc.php
|   |   |-- header.inc.php
|   |   `-- footer.inc.php
|   `-- templates
|       `-- default
|-- calendar
|   `-- images
|   |   `-- navbar.gif
|   `-- inc
|   |   |-- functions.inc.php
|   |   |-- header.inc.php
|   |   `-- footer.inc.php
|   `-- templates
|       `-- default
|-- cron
|-- doc
|-- email
|   `-- images
|   |   `-- navbar.gif
|   `-- inc
|   |   |-- functions.inc.php
|   |   |-- header.inc.php
|   |   `-- footer.inc.php
|   `-- templates
|       `-- default
|-- filemanager
|-- files
|   |-- groups
|   `-- users
|-- inc
|   |-- phpgwapi
    |   |-- phpgw.inc.php
    |   |-- phpgw_info.inc.php
    |   |-- phpgw_common.inc.php
|   |   `-- etc...
|   `-- templates
|       |-- default
|       |   |-- addressbook
|       |   |-- admin
|       |   |-- calendar
|       |   |-- common
|       |   |-- email
|       |   |-- filemanager
|       |   |-- headlines
|       |   |-- preferences
|       |   |-- todo
|       |   `-- tts
|       `-- icons
|           |-- email
|           |-- calendar
|           `-- tts
|-- preferences
|   `-- images
|   |   `-- navbar.gif
|   `-- inc
|   |   |-- functions.inc.php
|   |   |-- header.inc.php
|   |   `-- footer.inc.php
|   `-- templates
|       `-- default
|-- themes
`-- todo
    `-- images
    |   `-- navbar.gif
    `-- inc
    |   |-- functions.inc.php
    |   |-- header.inc.php
    |   `-- footer.inc.php
    `-- templates
        `-- default
  

4.3 Translations

The translations are now being done thru the database, and will be configurable to use other mechanisms.
We are completing a program called Transy, which will provide developers/translators a nice GUI for building and updating translations.
In the mean time you will need to create a sql script yourself and name it lang.sql. You can copy the one in doc/lang.sql and use it as a template.