| 4 | | Moving each component to its own subfolder provides several advantages, in particular the ability to add further support files (images, libraries, metadata, settings) for each component. So instead of calling an action as {{{actions/calendar.php}}} we will call it as {{{actions/calendar/calendar.php}}}. Component folders are also useful to provide drop-in support for user-contributed plugins that may come as zipped files or tarballs to extract and put in the appropriate directory. As for language packages, this modification will allow to store localized definitions for default pages within specific language folders, e.g.: |
| | 4 | Moving each component to its own subfolder provides several advantages, in particular the ability to add further support files (images, libraries, metadata, settings) for each component. So instead of calling an action as {{{actions/calendar.php}}} we will call it as {{{actions/calendar/calendar.php}}}. Component folders are also useful to provide drop-in support for user-contributed plugins that may come as zipped files or tarballs to extract and put in the appropriate directory, e.g. |
| | 5 | |
| | 6 | {{{ |
| | 7 | actions/ |
| | 8 | .....myaction/ |
| | 9 | ........css/ |
| | 10 | ........img/ |
| | 11 | ........inc/ |
| | 12 | ........js/ |
| | 13 | ........lang/ |
| | 14 | ........myaction.php |
| | 15 | }}} |
| | 16 | |
| | 17 | As for language packages, this modification will allow to store localized definitions for default pages within specific language folders, e.g.: |
