Modular system!

[streever]

Hi all,

the one thing (even more than my permissions ) that I really think CMSMS could benefit from would be to simplify it a little more

What I think is that the modules are not reliable. I mean, if I see calguys name, yea, I know that'll be good. and I know if it has a bug, he'll iron it out. There are several others, too, who are reliable.

But a quick browse turns up dozens of unusable or very, very poorly documented modules.

I think one HUGE fix would be to make some simple things that are re-used over and over.

For instance: categories. Why aren't categories always done the same? All modules should use the same category system, so that it can then be incorporated into something like permissions. (x user has y permission for z category) I mean, this would not be hard if all modules used the same category system.

ALSO: it'd be SO MUCH EASIER to make a module!

Just think about it! If all modules used the same category code, you'd just drag and drop.

Same thing for dates. (It looks like that is already the case) and other things.

I think it should all be standardized, with components of each being modularized.

that's about it

then you could go to dev.cmsmadesimple.org & download the "categories" system, which will be updated regularly. We could have alternate versions, but one OFFICIAL version. then, each module must list which components it uses.
"Official categories 1.0"
"Official Dates 1.0"
etc

[Duketown]

streever,

I agree with you that it would be very nice indeed that only one part would hold the categories. This is possible only one of those parts that should be centralized or maybe a better characteristic would be a core module. Bear however in mind that there are numerous other modules that should be upgraded to the new module. This takes time and as in most cases time is limited especially for the core development team (its just my idea since I see that in my IT job as well). It all has to do with setting the priorities and thus the planning. I would like to propose a poll that allows the community to select one of many modules to be centralized. Based upon the outcome the core development team gets an idea what the community want to see grow in both quality as well as support.

I see these things (multiple categories) on the other side as very positive. In my opinion it means that there are quite a number of persons out there that believe that CMSMS is a good system an they either build from scratch or adapt another system. Both with their own consequences. eCommerce module is another good example of this. When you build from scratch it would be very benifical that you know about the other modules (inside out??) and use parts of the other modules instead of reinventing the wheel.

Duketown