I'm not speaking about a fork. If I wanted another CMS, then I would probably start from scratch and build it based on Mojavi (MVC 2), WACT, or Ambivalence (Maverick). I'm more interested in eliminating the need to say 'it's coming in 5.0' in the interest of encouraging more developers to migrate to Mambo and giving users things they ask for.
There are large numbers of valuable hacks hidden away in message threads that the average user would have difficulty installing themselves with no knowledge of PHP or SQL. We could put together a team from the community and start a project where those features could be integrated into a core superpack. After each maintenance release, those enhancements could be added to the superpack file set using a file comparator such as BeyondCompare. It's also possible to add those improvements using conditionals from admin, so the site admin could make intelligent decisions about what to enable or disable based on their needs. The interface for doing that could be a component.
Gayle had a good idea earlier about making the existing class library extensible. There is no reason why one or more XML-RPC or SOAP server/client could not be created in component form based on class libraries absorbed into the core using that method. It could be used for multisite and inter-application authentication replication or could be used in conjunction with the existing metabloggarapi library.
As Andrew has already indicated, adding ADODB opened the door to make it easier to complete the phpGACL implementation. This could be done now for 4.5 with the ADODB extension. A lot of other nice libraries are built on top of ADODB (dbForms is an example).
Take sub_templates as another example. Part of the reason why they cannot be implemented simpler is because table rows are missing from the menu creation forms. For Content Section, Content Category, Content Section Archive and Content Category Archive, adding a single table row to those forms will add the necessary textarea field to make it work. The rest of the code has been in there since the betas. It would take a bit of sleuthing, but adding sub_template support to Typed Content and URL menu types should be possible. Many people want this feature, but it appears to be a low priority item for the core team.
I have not taken a look at MambelFish lately, but I would guess that it may be possible to use mapping tables to implement it without modifying each and every component.
Basically, there are a lot of things that could be done to 4.5 to enhance what's there. It's my guess that some brainstorming sessions about 5.0 roadmap features might yield some ideas on implementing many of those features with minimal changes to the 4.5 core.
Quote:
|
Originally Posted by SvenErik I doubt this superhacked core would be compatible with the v5.0 since with the introduction of XML-RPC and all (I guess) most of the core code if not all, would be replaced with a whole new codebase. And you would also soon end up with a codebase that would require components to be made in 2 versions, one for the original v4.5 core, and one for the superhack core. And such a fork would not benefit the community... |
Re: Mambo 4.6 / 5? 
Linear Mode
