| version 1.7, 2003/03/31 18:29:33 |
version 1.8, 2003/04/06 19:32:33 |
|
|
| <!-- $Platon: phpMyEdit/doc/sgml/extensions.sgml,v 1.6 2003/03/31 00:11:41 nepto Exp $ --> |
<!-- $Platon: phpMyEdit/doc/sgml/extensions.sgml,v 1.7 2003/03/31 18:29:33 nepto Exp $ --> |
| |
|
| <chapter id="extensions"> |
<chapter id="extensions"> |
| <title id="extensions.title">Extensions</title> |
<title id="extensions.title">Extensions</title> |
|
|
| |
|
| There are often situations, when more specific functionality is needed from |
There are often situations, when more specific functionality is needed from |
| &name;. You will surely agree, that it will be really strange to hardcode all |
&name;. You will surely agree, that it will be really strange to hardcode all |
| these particular requirements into core &name; class. For this purpose is |
these particular requirements into the core &name; class. For this reason the |
| extension mechanism provided. |
extension mechanism provided. |
| |
|
| </para> |
</para> |
| Line 16 extension mechanism provided. |
|
| Line 16 extension mechanism provided. |
|
| <title id="extensions.overview.title">Overview</title> |
<title id="extensions.overview.title">Overview</title> |
| <para> |
<para> |
| |
|
| Extensions are &name;_<something> classes, where <something> is |
Extensions are &name;_<something> classes, where <something> is an |
| appropriate extension name. They extend base &name; class, but they also add |
appropriate extension name. They not only extend base &name; class, but they |
| some new functionality. But they may not <!-- ??? must not ??? --> only to add |
also add new functionality. But they may not only add new things. It is |
| new things. It is possible also to disable such features, simply to get |
possible also to disable such features, simply to get the desirable behaviour. |
| desirable behaviour. |
|
| |
|
| </para> |
</para> |
| <para> |
<para> |
| Line 28 desirable behaviour. |
|
| Line 27 desirable behaviour. |
|
| In addition to common &name; configuration options, extension configuration is |
In addition to common &name; configuration options, extension configuration is |
| usually provided by <varname>$opts['ext']</varname> associative array. |
usually provided by <varname>$opts['ext']</varname> associative array. |
| Possible keys are described on particular extension pages in this manual. |
Possible keys are described on particular extension pages in this manual. |
| Please refer to them to get particular information. |
Please refer to them to get more information. |
| |
|
| </para> |
</para> |
| <para> |
<para> |
| |
|
| Extensions are currently not part of &name; distribution. They are only in |
Extensions are currently not part of &name; distribution. They are only in |
| <ulink url="http://www.platon.sk/cvs/cvs.php/&name;/extensions/">CVS |
<ulink url="http://www.platon.sk/cvs/cvs.php/&name;/extensions/">CVS |
| repository</>, because they are still under development and they are changing a |
repository</>, because they are still under development and they are changing |
| lot. This manual chapter is provided for letting &name; users know, that |
a lot. This manual chapter is provided for letting &name; users know, that |
| something like this exists. The only way how to get extension files is to |
something like this exists. The only way how to get extension files is to |
| fetch them from CVS. All extensions need to be placed under <filename |
fetch them from CVS. All extensions need to be placed under the <filename |
| class=directory>extensions/</> subdirectory of place, where basic &name; core |
class=directory>extensions/</> subdirectory below the &name; core class |
| class is located. |
location. |
| |
|
| </para> |
</para> |
| <para> |
<para> |
| |
|
| Several new extensions are planned to create to handle more or less specific |
Several new extensions are planned to create or handle more or less specific |
| tasks, especially these which are not appropriate for &name; core class. You |
tasks, especially those which are not appropriate for the &name; core class. |
| can feel absolutely free to improve already existing extensions, suggest new |
You can feel absolutely free to improve existing extensions, suggest new |
| improvements for them, or create new extensions to fit your own needs. We will |
improvements for them, or create new extensions to fit your own needs. We will |
| be happy to add them to repository. |
be happy to add them to repository. |
| |
|