Meet the new Joomla Framework

    Judging by my previous articles about Joomla ( this , this and this ) everyone on the hub thinks the Joomla team is a bicycle builder, and they complain that too often this Joomla breaks everything and does it all over again.
    But, in November last year, something special happened.

    But first, a little history:
    As everyone remembers, initially Joomla was just a CMS (somewhere before version 1.6). Then the developers decided to allocate a framework from it (which was called Joomla Platform). It didn’t work out very well - now I had to edit the bugs in two repositories, agree on compatibility between them, and somehow the profit (applications that users would build on the Platform without CMS) did not appear. This strange symbiosis would have lived if someone had not said, “Enough.” And the following was suggested:

    • Platform will gradually bend and be integrated into the CMS. Because nefig to support an application that is still nowhere except CMS has never been used. Bugs will be corrected in one place, everyone is happy. Web developers will not notice anything.
    • Instead of Platform there will be Framework - a very rewritten and incompatible product with the original Platform. It will not be used in CMS, as it is incompatible.


    What will happen in the new Joomla Framework?

    • Batch system. The framework can be installed in parts using PHP Composer
    • Namespace support
    • The user may not load some components of the framework, but may add his own


    CMS will NOT use this framework. At least for now. Since it is completely incompatible. It is possible, in the future, CMS developers will want to integrate some components of the framework into it, however, this will not be soon.
    Some more radical usersoffer the following: “If I were the main developer, I would write off the current CMS architecture at the end of the life of the 4.x series, which will be at the end of 2016. In 2014, when release 4.0 is released, I would release Joomla! Next, which would be built from scratch on the Framework. In order to support backward compatibility, I would use 4.x as a transition layer between two applications. The goal is that extensions should work on 3.5 and 4.x or 4.x and Next with minor problems, but not on 3.5 and Next at the same time. In addition, I would do my best to keep the existing infrastructure of extensions in place, as this is what Joomla! makes his money. ”

    Also popular now: