CMS components. Standardization or anarchy?

with Ulysses sub forum
KBleivik
Site Admin
Posts: 178
Joined: Tue Sep 29, 2009 6:25 pm
Location: Moss Norway
Contact:

CMS components. Standardization or anarchy?

Postby KBleivik » Mon Jun 27, 2011 1:18 am

There are a lot of cms systems http://www.cmsmatrix.org/, so many that it is extremly difficult to get an overview. Some of them may die as older versions of a programming languag like php is deprecated. Php 6.0 takes time to finalize because of unicode implementation. But most of the 6.0 features like name spaces etc. are already implemented in the last stable version, php 5.3.6 when these words are written. Multiple inheritance is now implemented for interfaces and object relational mapping http://www.oopschool.com/books/ProPHP6Example.pdf opens the possibility to write very compact and efficient code. By using the PDO http://php.net/manual/en/book.pdo.php database object and prepared statements it will be much easier to prevent SQL injection attacks and write safer code. The php cURL http://php.net/manual/en/book.curl.php added in php 4.02 and similar extensions standardizes and eases implementation. Even one of the worlds most popular blog / cms systems, WordPress is slow to adapt to the new php 6 functionality and flexibility viewtopic.php?f=18&t=213

Every cms system needs
  • an authentification
  • an email system
  • a security system
  • etc. etc.

Dont Repeat Yourself = DRY is a central principle in object oriented programming. Code reuse is the word for it. Most of the web masters that develope their own sites know the MVC pattern http://heim.ifi.uio.no/~trygver/themes/ ... index.html developed years ago by Trygve M. H. Reenskaug http://heim.ifi.uio.no/~trygver/ In a sense design patterns are generalized classes.

The author of this post knows C++Builder professional http://www.embarcadero.com/products/cbuilder very well. C++Builder's IDE was inspired by "Object pascal's / Delphi's" Rapid Application Development (RAD) framework. Components are dropped on a form and you see the GUI at design time. In a sense components are generalised patterns.

So what the world needs from php 6.0 is different components that use the above mentioned techniques to develope core CMS functionality like an authenification component, database components, email components, URL components etc.

Then we may see much flexibility in the development of new secure and easy to upgrade CMS systems. Has the time come for an Open CMS component organization?

Then, will we need Drupal, Elgg etc core?

Return to “PHP 6 and later”

Who is online

Users browsing this forum: No registered users and 2 guests