28
Quote:
XOOPS really needs some fresh ideas, and to release some old bagage - especially on this site. No need for 50 different mods that do the same thing, weed out the crap and focus efforts on one or 2 good implementations. When everyone keeps reiventing the same wheel all you get is a bunch of mediocre wheels.
Quote:
I do and don't agree with this at the same time, lol if one module did everything, but with options to turn on and off the feature then yeah, but this won't happen, so if each different module offered different features and benefits this is not a bad thing.
What about creating one core module for each functional area, but with the flexibility to add additional functionality through module plugins/addons? For example, instead of having 5 or 6 different article management systems, there could be one core article management module, which could be expanded through third party plugin development.
My biggest struggle with XOOPS modules is trying to find the modules that accomplish what I need. Recently, I've been debating whether to use News, SmartSection, or AMS for the article management system of my site. The problem is that each module has specific features that I need, but there isn't one module that includes all those features. So, my choices are limited to either forgoing some features or spending weeks trying to make modifications with my very limited PHP knowledge.
I believe that XOOPS modules would become much more functional and advanced if the focus was on adding features or plugins to core module frameworks, instead of having several different modules for each category of module, each with varying features. Also, the support would improve too, since everyone would be focusing on a set of core modules. There is also less risk of development and support of a specific module stopping, since there is only one version of the module. The worst case scenario would be that the development or support of a particular plugin would stop. However, that isn't as bad as development/support of an entire module stopping, especially if your site has been depending on it.
Anyway, I hope that I'm making some sense here. I'm not a CMS developer and I don't know the complexities involved with what I'm suggesting. Thus, it may or may not be feasible. It is just an idea though.
Dave