Roadmap: Namespace Conversion for Kernel Classes

[geekwright]

Using a Namespace for classes is considered best practice. Some kernel classes have been converted to the Xoops\Core\Kernel namespace, but more remain.

[alain91]

does this concern all classes in class and kernel directories ? if not what are the rules to decide ?

[geekwright]

Alain,

Thanks for taking an interest in this one!

The first priority would be to update the kernel directory. Currently, only object.php has been converted.

I would like to move the these to the Xoops\Core\Kernel\Handlers namespace.

Each separate class should be in its own file in that namespace.

The classes in existing files would be converted to stubs, for example, like this for blocks.php:

class XoopsBlock extends Xoops\Core\Kernel\Handlers\XoopsBlock
{
}

class XoopsBlockHandler extends Xoops\Core\Kernel\Handlers\XoopsBlockHandler
{
}

These will be retained for legacy code compatibility, and will be removed in a future version.

Xoops::getHandler() will need to be modified to go directly to the namespaced handlers.

The classes directory is very similar, but has a big mix of what has and has not been done. There are also a few exceptions. I'll do an inventory and post the plan for those separately.