symphonycms/symphony-2 — Issue #822: Rethinking the lib/ directory
Author: eKoeS
Created: 2011-10-10 20:13:34+00:00
State: open

Every time I look at the `lib/` directory I ask myself why it's organised that way:

* There's a `core` folder with a handful of classes required for both the frontend and the backend.
* There's a `lang` folder with just one file that is mentioned only once by `toolkit/class.lang.php` (@nilshoerrmann is there a way to remove it completely and include the needed stuff in the `class.lang.php` file itself?)
* There's `boot` folder that actually doesn't contain libraries or utility classes (can't we move them to the parent directory?)
* There's a `toolkit` folder that is responbile for 98% of the things we need in the backend.

In my opinion, the old demo called "Symphony 3" did a better job from this point of view, by putting everything in one single folder called `lib`: https://github.com/symphonycms/symphony-3/tree/master/symphony/lib

Question: would it be possible to emulate Symphony 3 and re-think the whole `lib/` directory so that it makes more sense?