44
I returned after a few months break. Maybe I missed some discussion, but let me throw in there some opinions.
First. What exactly the functionality we expect from a module framework? What classes should include, feature lists, etc..
Personally (I have some experience in develop XOOPS modules), I do not see a huge need for additional layers as the module framework. Perhaps the collection classes and helpers, yes. But whether we call this framework?
Many developers have their own ideas and habits and can not meet all of one 'universal' framework.
In my vision, the core defines modules routine (how mods interact with each other, with layers of data, logic, presentation) and provide the bricks (such as XoopsObjects) to build these modules.
So... I think more useful is good documentation and tutorials how to build the modern XOOPS modules, how to properly use XoopsObject, etc. Unfortunately, my knowledge in this area is quite limited to help into docs.
Quote:
Adding a lot of code to the Core will create tons of dependencies and higher complexity, and higher chances to break things.
Well, everything depends on how the core is designed as a modular and if we stick rigidly MVC or MVP... but I do not have much experience, so I can not judge.