Looking for volunteers to join your project? Need help with a script but can't afford to pay? Want to offer your services as a volunteer to build up your portfolio? This is the place for you...
PHP 5.3 is needed it does not work with 5.2.X ( I see this as a feature )
Namespaces
OOP
Autoloading
Smarty
Doctrine ORM
Rest API
Module based
Module validation
Official Extension server and Client, Restful API connected.
Already lots of modules, i.e. complex rating widget, comment widget, admin panel, news posting/blog, static pages, link module, auth system (complex)
Spam control: RECaptcha
Very well documented! Including Wiki/ API docs and video tutorials.
Overriding compatible template files, themes can override every single tpl file in the core of PeecFW. This means, output is based on what theme you use. This also means that PeecFW can really be any type of application.
http://code.google.com/p/peecfw/ wrote:MAT replaces the old MVC (Model View Controller) pattern. MAT is a new concept based on 3 basic things.
Module is where you have logic bound to POST/GET variables. You can use Modules inside Modules and Modules can rely on specific Modules.
Application is the framework itself it has alot of libraries that makes your life easier, you can access Libraries and Application methods from one specific Module.
Template Application & Module can access the template engine. Every Module and Application have it's own instance of the Template engine to avoid variables. You are anyway able to access all the diferent template instances from one specific Module.
Looking at your pages on Google Code it would seem that where one might (in the old MVC days) have separated concerns into controllers and models it all now goes into modules.
What are the benefits as you seem them of MAT over MVC?
Some benefits:
- Easier structure of files / folders
- Controller logic in "MVC" is not reusable, therefor we integrated this into the "model" in PeecFW.