If you are looking for DotKernel 3 related posts, go here.
Finally we reached DotKernel 1.2.0 milestone.
Since the previous released 1.1.2, some changes have been made.
- On database, we changed the names and structure of tables to respect database naming convention. http://www.dotkernel.com/dotkernel/dotkernel-database-naming-conventions-for-mysql/
- A new word came into our DotKernel discussions: dots. We use this term when talking about a submodule and all its component files. For example, “user” is a submodule of frontend module. Note that one dots can be part of multiple modules. (For example, “user” dots belong to frontend and admin module). For each dots, the configurations values have been added to xml files which are stored in configs/dots folder. In the preview versions, this values where hard-coded in the php files.
- Another change made in configs folder is resource.xml, which contains the configuration values for the controllers of each module.
To be easier to start an application from DotKernel, in admin module, there are now the following dots: admin, user and system.
New library classes have been implemented: Dot_Geoip and Dot_Seo, and some of the existing ones have been updated: Dot_Curl and Dot_Session (each module has his own session).
In DotKernel, all SQL queries are written as prepared statements. We strongly encourage this practice: http://www.dotkernel.com/php-development/protection-against-sql-injection-using-pdo-and-zend-framework/
For more details, see ChangeLog 1.2.0