Page
Many different PAD parts together in one page.
- Line in _inits.pad / root
- Variable in _inits.php / def/klm
- Line in _inits.pad / def
- Variable in _inits.php / def/klm
- Line in _inits.pad / def/klm
- Variable in _inits.php / def/klm
- Line in page.pad / def/klm
- Variable in page.php / def/klm
- XML 1 from _data / def
- XML 2 from _data / def
- Line in _tags/myTag.pad / root
- Variable in _tags/myTag.php / root
- Line for _function/Myfunction.php in root
- Line for _option/myOption.php in def/klm
- Line for _scripts/myScript.sh def
- Line for _callbacks/myCallback in def/klm
- Line in _include/myInclude.pad / root
- Variable in _include/myInclude.php / root
- Line in _lib/myLib.pad / def/klm
- Variable in _lib/myLib.php / def/klm
- Line in _exits.pad / def/klm
- Variable in _exits.php / root
- Line in _exits.pad / def
- Variable in _exits.php / root
- Line in _exits.pad / root
- Variable in _exits.php / root
Sequence of calls
Note that some values 'root/abc/klm/xyz' look incorrect. This comes because all inits/exits/page PHP sources are called before the rendering of the PAD templates start. The sequence is.
- /_inits.php
- /abc/_inits.php
- /abc/klm/_inits.php
- /abc/klm/xyz/_inits.php
- /abc/klm/xyz/page.php
- /abc/klm/xyz/_exits.php
- /abc/klm/_exits.php
- /abc/_exits.php
- /_exits.php
So it is possible (and in this example application it happens) that:
- <page>.php PHP code overwrites variables from the _inits.php PHP code
- the _exit.php files overwrites variabeles from <page>.php and _inits.php fPHP code
An earlier version of PAD did prevent this, but in reality it is handy, this way you can set for exampe a $title variable in the page PHP code that is used in the _inits.pad template.