...

World Wide Web Server 2012-07-04 16:03:35 -07:00
parent 87884a0dbf
commit 47b9150ff5

@ -16,8 +16,7 @@ And that's it! *sound of party blowers*
[h3]... Unless you are running PHP 4[/h3]
In which case you will have to use [[File:Modular_Separation_PHP4.zip | my custom Base4.php file]]. Download it and overwrite the original in your [i]/codeigniter/[/i] folder.
[h2]Usage[/h2]
[h3]Folder structure[/h3]
[h2]Folder structure[/h2]
I would like to start with pointing out that you are still able to use models, views, controllers and other resources as usual when using Modular Separation. This also means that you can have global resources in your standard folders and call them from your modules. If you, on the other hand, want to get rid of the folders then you are free to do so, [b]with the exception of the controllers folder[/b].
Modules must be placed in the /application/modules/ folder. A module is a folder (the foldername is the name of the module) containing folders for models, views, controllers and other resources. These are not required and you do not have to add folders for e.g. models if you are not including any models in the module.
@ -47,4 +46,7 @@ system
categories.php
[/code]
[h3]Loader methods[/h3]
[h2]Usage[/h2]
Now, all you have to do in order to load a resource from the current module, is add its name as the last argument of one of the loader methods. But since most of those have additional arguments that are not commonly used, I have also made special module-methods where the name of the module is the first argument. Here is a full list of methods and their arguments:
[h3]library($library = '', $params = null, $module = '')[/h3]