Hi there, a couple of you have been asking for a way of keeping assosiated views/controllers/models in the same folder. I don’t know if anyones made it yet, but I thought I’d share mine (it’s not commented or anything - it was just intended to be of my own use).

Modular Separation has been deprecated by Matchbox. However, Matchbox is backwards compatible with its predecessor so you can switch over without problems.

See the Wiki Page for documentation.

Very nice and I will play with your contribution tonight. Elliot did something similar for the CodeIgnition CMS project on svn. I think his solution was developed for 1.4.1 and is being upgraded to 1.5.x. For your reference, you might want to take a look at what he did.

Excuse me to interrupt the discussion but I do not understand interest of this thing. I think I missed something perhaps relevant.
Could you explain me why you want to keep this stuff in the same folder ?

Thanks

Well. In most cases you wouldn’t But if you’re developing something you’d like to share, or some sort of module based application where you’d like people to pick just the parts they like, etc. they would only need to drop in a folder, instead of copying the assosiated files into different folders. As a bonus, it’s also easier to get rid of the modules ... But really, not many people will need this.

ok, I understand now

I keep it in mind in case.
thx

dynazack - 07 November 2006 02:54 PM

The files should be placed in the following folders:

/system/application/modules/controllers/MODULENAME/controllers/
/system/application/modules/controllers/MODULENAME/models/
/system/application/modules/controllers/MODULENAME/views/

Hi dynazack, great contribution . Wouldn’t it make more sense if the folder structure for modules was like below? I don’t understand why the modules sit within an extra directory called ‘controllers’

Ooops, actually thats how it already is. It went a little fast explaining the fodler structure. I’ll edit it right away. I’d be great if some people would try it out just so i know it works.

Thanks dynazack for the contribution, i’ll keep you posted on how it goes

Hi again dynazack. Been trying to use your libraries but Im having some trouble implementing them.

Firstly I’m using PHP4 and I don’t understand this step:

/system/codeigniter/Base4.php
...

class CI_Base extends MY_Loader {

...

That is, replacing CI_Loader with MY_Loader.

I changed it so that CI_Base extends MY_Loader but then it complains “MY_Loader doesn’t exist…”.

Secondly, I’ve got the MY_Loader and MY_Router files under my application/cms/libraries/ folder and I’ve loaded the libraries into my Controller constructor and I get “Unable to load the class MY_Router…”.

What am I doing wrong?

Thanks in advance:)

First of all, MY_Libraries are extended base libraries. Therefore, MY_Loader and MY_Router goes in and does a few changes to the native CI mechanics. Base libraries that are loaded automaticly (including Loader and Router) does not need to be loaded in a controller, and neither does their extensions. So, you do not need to load those libraries.

That it complains about not being able to find MY_Loader is strange. Since youve put em in the application/cms/libraries, are you sure you have set the correct application path in your index.php file? This whole solution shouldn’t need any configuration at all, only that little bug fix with PHP4. Thanks for telling me this, please tell me if there is still problems.