[eluser]adamp1[/eluser]
After reading your reply I don't think you quite understood why I wanted sub folders. Ill try to explain what I mean.
In my admin area at the top I have a drop down menu system much like ExpressionEngine. One option is
Code:
System
-> Users
-> Settings
-> etc
If the user clicks on 'Users' I want them to go to a page showing them the list of users. If they click on 'Settings' I want it to show the settings and so on. BUT if they click on 'System' I want it to show a page which shows the sub options 'Users','Settings'. That's all this system_default controller would do.
Now for why I wanted to be able to put it in its own sub folder. This was the structure I wanted.
Code:
admin/
system/
default.php
users.php
settings.php
The reason for this mean then all code to do with managing the system is within a single folder. This would mean then you would have a new folder for each parent menu item thus keeping the code modular.
So If I wanted to add a menu item to control site pages the structure would be as follws
Code:
admin/
pages/
default.php
pages.php
templtes.php
stylesheets.php
system/
default.php
users.php
settings.php
I could probably do what you said, but then I would be splitting up the code to view the front page of a controller and the inner subfuctions. Which to me seems to complicate the matter.
The reason I said I would have to have a large controller is it would have a single controller 'System' which would do the job of the folder (IE keep all code related to system operations together)
