Site Blog
We have established an amazing growth from 12 language packs in the 0.7.x era to 23 language packs in v1.0.0. My personal motivation is: the more translations we have, the bigger possible audience for e107 we might attract! And so far it has been very rewarding for e107.
Also I try to reach as close to 100% perfection as possible for all language packs, in order to assure the quality is also good for users working in foreign languages. That means there is close and intensive communication necessary with the official e107 translators. We discuss missing language items, language interpretations, features, bugs etc. Currently I'm still awaiting final contributions of Latvian and Norwegian, I hope we can also add these to the list on short notice. Of course we want to grow further, so we have set our goals to also have Korean and Japanese as supported languages. We are still looking for official e107 translators for these languages. These and more jobs can be found at the e107.org jobs section.
You can read the latest published news article about our language growth here: http://e107.org/news.php?extend.886
In short, the list of e107 translation packages has doubled and is still growing. We would like to express our gratitude to our loyal members making this all possible, and a special thanks for all the efforts made by our expanding translation team. It's an excellent example of the potential of the community at the e107 website content management system.
EDIT: Norwegian language pack has been posted March 19, 2012.
Development of PHP scripts without a preconceived plan to manage them is asking for a headache. The goal of a framework is to make the process of writing web-based applications simpler. Due to e107 popularity, things got a bit out of hand during the development. It is time to iron some things out that slipped in during these past years. Currently the e107 devs just 'make things work' and 'make things a bit more secure', but old legacy code is still there and it's procrastinating security and performance improvements. The e107 devs see a need to get rid of old procedural code and provide permanent solutions for the e107 system.
An application designed around MVC is easier to manage because it is split into tiers, which allow for independent development. This promotes code re-usability by building models, which are reusable throughout the application. That is why we would like to embrace MVC and single entry point (Front Controller) in the e107 0.8 version.
What is MVC?
Model-View-Controller (MVC) is a software architecture, currently considered an architectural pattern used in software engineering. The pattern isolates "domain logic" (the application logic for the user) from input and presentation (GUI), permitting independent development, testing and maintenance of each.
MVC is often seen in web applications where the view is the HTML or XHTML generated by the app. The history of e107 was working with classes, but not really in an MVC efficient way. Working with MVC will bring better OOP (object oriented programming) standards closer.
What's in it for you?
Applying MVC will bring you more security enhancement (possible 'sandbox-ed' environment, possibilities to implement security mechanisms on different application layers/request stages, etc).
Please note that the code producing will not take so much time. The time consuming process is the design and analysis - the code preparation phase to implement all this.
To summarize all benefits for you: a better, safer and much more flexible CMS platform, that will provide plugin writers to integrate even better in e107, with an architecture ready for future developments. The catch? Well, it might take a while; but that's an old story.
Relevant links
http://en.wikipedia.org/wiki/Model-view-controllerhttp://www.phpro.org/tutorials/Model-View-Controller-MVC.html
http://www.mustap.com/phpzone_post_73_top-10-php-mvc-frameworks
Follow us
