Meet the new Joomla Framework
Judging by my previous articles about Joomla ( this , this and this ), everyone on the Habrr considers the Joomla team to be cycling builders, and complain that too often this Joomla is broken and everything is done anew.
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 select from it a framework (which was called the Joomla Platform). It turned out not so much - now I had to edit the bugs in two repositories, to agree on compatibility between them, and the profit (applications that users would build on the Platform without a CMS) somehow did not appear. It would have lived this strange symbiosis, if someone had not said - "Enough." And the following was suggested:
What will happen in the new Joomla Framework?
')
CMS will NOT use this framework. At least for now. Since completely incompatible. It is possible in the future, the CMS developers will want to integrate into it some components of the framework, but it will not be soon.
Some more radical users suggest the following: “If I were a major developer, I would“ write off ”the current CMS architecture at the end of the 4.x series life, which will be at the end of 2016. In 2014, when release 4.0 will be released, I would release Joomla! Next, which would be built from scratch on the Framework. In order to maintain backward compatibility, I would use 4.x as a transitional level between the 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 make every effort to keep the existing infrastructure extensions in place, as this is what Joomla! makes his money. "
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 select from it a framework (which was called the Joomla Platform). It turned out not so much - now I had to edit the bugs in two repositories, to agree on compatibility between them, and the profit (applications that users would build on the Platform without a CMS) somehow did not appear. It would have lived this strange symbiosis, if someone had not said - "Enough." And the following was suggested:
- Platform will gradually be bent and will be integrated into the CMS. For nefig support an application that is still nowhere except the CMS has never been used. Bugs will be ruled in one place, everyone is happy. Web developers will not notice anything.
- Instead, Platform 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?
')
- Package system The framework can be installed in parts using PHP Composer
- Namespace support
- The user may not load some components of the framework, and may add their own
CMS will NOT use this framework. At least for now. Since completely incompatible. It is possible in the future, the CMS developers will want to integrate into it some components of the framework, but it will not be soon.
Some more radical users suggest the following: “If I were a major developer, I would“ write off ”the current CMS architecture at the end of the 4.x series life, which will be at the end of 2016. In 2014, when release 4.0 will be released, I would release Joomla! Next, which would be built from scratch on the Framework. In order to maintain backward compatibility, I would use 4.x as a transitional level between the 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 make every effort to keep the existing infrastructure extensions in place, as this is what Joomla! makes his money. "
Source: https://habr.com/ru/post/175237/
All Articles