I saw fule's code today, and I noticed one thing.
All core code in namespace \fuel\core, but packages on \package-name.
It is not sexy. I think all package may put \fuel\package\package-name. All packages also made by users, must be followed this namespace rule.
Otherwise, 1st level namespace will be occupied by packages, general user must think about their namespace...
An user must be able to use any namespace without \fuel
You are are completely free from selecting any namespace you want.
For packages, it doesn't have to be \packagename, you can make it \this\that\the\other\package if you want.
But you can not use \Fuel, this is reserved for the framework.
I see.
But about fuel task, we must set namespace Fule\Tasks, I think.
On package, developer can put name freely, but on task we must put Fuel/Tasks exactly. Umm, I think it is not logical on the view point of an user.
The namespace for tasks is set because oil doesn't have any way of determining the namespace defined for a task class.
It can find and load the task, but it can never call it if it doesn't know the namespace.
We're open for suggestions, If you have a better solution, please code it up and send a pull request.
Donate
