Ricardo Costa

I 100% agree with avoiding the global scope and have classes implementing interfaces, etc. Has for plugins, they do not require configuration. Regarding the move to namespaces, we will probably...

I would like to know what features of system module should be exported to other modules. I am currently working on a 'waiting' module. What should I do next? I...

I proposed making a module for holding the usermenu block, so the plugins would work with this module instead of the system module. I think Xoops/Html/Menu should be implemented as...

An example of a xoops module namespace could be: xoops\modules\dummy Example of usage in file ROOT/modules/dummy/class/ObjectHandler.php: namespace xoops\modules\dummy\class; class ObjectHandler {} Do we need a namespace key in xoops_version.php? The...

Ok Richard, I agree with you. Let us go with ease. I would like to see modules actions separated from views. I plan on making a module that will extend...

@geekwright Great, thanks! I had the idea that plugins_dir was a private method.

I would just use ``` if (class_exists('xoops\modules\system\Install')) { $install = new xoops\modules\system\Install; $success = $install->postInstall($module); } ``` And XoopsLoad would look for the class in private folder and in public...