I'm still in very early investigations of FuelPHP although I think we're going to use it for our software as it does look very good.
I have found one thing which I feel might want to be a variable in future however and that is having to have controller/models/views in a folder called classes. For some modules which are quite basic there may not be a lot of other subfolders involved.
Well if you want to move them I have found the 2 locations which (unless I'm wrong) is all you need to change:
Start by explaining why you have a need to change this? Perhaps there are better ways to solve your problem.
FuelPHP is already very flexible as to where files are stored (through modules and packages), but in those locations the folder structure is fixed (not only for classes).
The reason for this is simple, a fixed location limits the number of file lookups, which are a performance it. You don't want the autoloader to have to run a lot of file_exists() checks to be able to load a file...
Again, start by explaining what you want (at the functional level).
A FuelPHP application that is of reasonable size and is designed in a modular and loosely coupled fashion has dozens of 'classes' folders. We have applications with more than 100...
Each of these locations have a fixed structure: - classes - views - config - vendor - lang - tests
This is structured by function, and impossible to merge without creating something very complex, which in turn will make your application difficult to handle, and slow.
Donate
