(04-08-2015, 01:57 PM)Mel9pr Wrote: (04-08-2015, 08:56 AM)Narf Wrote: You can have as many classes in as many subdirectories (although I wouldn't advise you to do that), but there's no way to make any of them a default controller.
Due to organization purposes I have all my controllers on sub folders (application/controllers/links/Links_controller.php... application/controllers/news/News_controller.php...... application/controllers/about_us/About_us_controller.php... and so on...) All is working OK using custom routes on routes.php. So my question is why you don't advise to do that? Is there something to be worry about it?
I was talking about nested directory levels (as in dir1/dir2/dir3/dir4/file.php), because each nesting level degrades performance.
Your examples don't go that far, but if they're real ... you're not organizing, you're only creating redundancy. And even if you are organizing, that's not a practical benefit.
