In our current layout the Kohana application is a shell around the modules. This means that if you have your own Kohana application, you can (with some minimal effort) embed the set of Gallery modules directly into your existing Kohana application as Kohana modules. If we put all the controllers, etc into the application directory then you would not be able to do that. We originally had it all in application and restructured it specifically to get this benefit.
---
Problems? Check gallery3/var/logs bugs/feature req's | upgrade to the latest code | use git
Posts: 7934
Yep, there's a reason for it
In our current layout the Kohana application is a shell around the modules. This means that if you have your own Kohana application, you can (with some minimal effort) embed the set of Gallery modules directly into your existing Kohana application as Kohana modules. If we put all the controllers, etc into the application directory then you would not be able to do that. We originally had it all in application and restructured it specifically to get this benefit.
---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git
Posts: 2
Great, thanks for the reply. Makes sense now.