26
Quote:
Yes, it's easy and possible to hack blocks, but the point of improving XOOPS is to make it so that the less things people have to hack the better, and these block/display issues, imo, are a major part of the core of any CMS, otherwise A CMS becomes "pointless" if you end up forcing people to hack blocks and news/article posting modules to get it to do certain basic things that all relate to handling "CONTENT."
I'm not talking about hacking blocks, I'm talking about creating additional blocks to cater to your needs. This in no way has anything to do with the core of Xoops. Everything you guys have mentioned concerning the news module can be done by creating, not hacking, additional blocks and altering templates. Trust me, I've done it. It requires no change at all to the core of Xoops.
Quote:
And the News Module is part of the "core." The core comprises several standard modules which the new module development team is working on and these include News, Sections, Blocks, Forums, Downloads, Headlines, etc. At the moment the first module getting the major overhall treatment is the Sections Mod. But all of these modules are part of the "Xoops" standard "Core," such as it is.
No, it isn't part of the "core". It was developed by the core team but is not required to run xoops. The core implies the required files for running Xoops. The brains of the system.
I'm well aware of what the modules team is working on, since I'm on it. All of the above mentioned modules have been handed over to the module team because they are no longer being developed by the core team. In fact, eventually there won't be any modules included WTIH the core (other than the system module), but rather you will choose between prepackaged Xoop products depending on your needs. Community portals will include the required modules to run such a site. Same for a magazine style site, etc.
Quote:
I don't think you can have any realistic discussion about the "core" without talking about improving these modules and what the end user and administrative processes are going to be. Sure you can talk about function classes until you are blue in the face, but without real world applications it's pointless, especially for all of us non-coders.
On the contrary, there are many things to discuss. The problem is the ones who require these changes are not the end user, it is the module developers. End users only see the end product, which is made up almost entirely of the modules used. SO I understand your confusion but your concerns don't concern the core, but the modules involved. We, the module developers, need these "silly" classes to build the modules you use. And that is what this discussion is about. As I stated earlier, there will be a discussion on modules at a later date and you can reveal your concerns about them then. For now lets stay focused on the topic at hand, the core.