On 19-May-2000 Henri Bergius wrote:
> On 18 May, Nick Rohrlach wrote:
>>> <(code-compat)>
>>
>> What does this one do?
>
> These 'reserved' elements don't do anything by themselves,
> only what you program them to do.
>
> However, a convenient practice could be the following:
>
> code-compat
> Compatibility code used for handling possible
> differences between Midgard versions. Can be
> also useful when moving to Midgard from regular
> PHP
>
> code-global
> Handling of globally-used functions and
> variables
>
> code-init
> Handling of active page parameters and setting
> variables needed in page construction. Also,
> setting additional HTTP headers could be done
> here.
>
Also I should add that these element's names just a convention. You are welcome
to tune midgard-root.php3 file for your needs (even select another naming
scheme) but in general current scheme is not bad :-)
And, after all, Admin Site uses it, so if you'll changes it, Admin Site will
not work.
But you can create customized midgard-root.php3 by putting MidgardRootFile
command in Apache's configuration file somewhere in virtual host (or directory
under it) because MidgardRootFile directive can be defined on per-directory
basis. It might have sense in some complex environments.
In general, Midgard is just parsing engine, and you could think that it is
similar to Emacs' LISP engine on which Emacs built itself.
----------------------------------
E-Mail: Alexander Bokovoy <[EMAIL PROTECTED]>
Date: 19-May-2000
Time: 12:24:47
This message was sent by XFMail
----------------------------------
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
