Pulling my hairout

[eluser]jayrulez[/eluser]
[quote author="phantomkiwi" date="1249281860"]It means the viewers controllers and models are stored in a database with a backend manager...

So you can quickly create a template embed a page in side the template attach javascript and css add inlcudes (snippets). Assign permissions (auth) publish dates etc...

Then you can create dynamic menus based on permissions and orders without going through lots of files and editing variables.

Plus it has a fall-back to the 'normal' flat file approach, for backwards compatibility.

I'm working on it now...

Just think of it as CodeIgnitor on steroids![/quote]

what would be the advantages to storing controllers and models in the database? i was under the impression that controllers are supposed to call models in order to interact with the database, and following this logic in accordance with your aim, you would interact with the database to access a controller which will get a model from the database in order to call a model to interact with the database. what would be the sense to doing all that?

and with regards to auth/rbac/acl there are frameworks like yii,i-framework etc... that provide those and you can create dynamic menus based on permission with them.

and as for templates, there are frameworks that offer what u mentioned