Directory structure for homegrown MVC app

[digicution]

I was wondering how everyone else would design a directory structure for a homegrown MVC application.

The two options I see are

[CODE}
/app_base
/models(Contains Pear_DBObjects generated models)
/views (contains smarty code and templates)
/smarty_includes
/templates
/templates_c
/controllers (contains classes that are the glue between the views and the models)
[/CODE]

The app_base would have an index.php file in it which fires off to controllers, the controllers would call data pulled from model objects based on the actions and variables/data posted/getted. The index.php file would then call a $controller->display() function.

The views section would have subdirs that are essentially storage places for smarty templates.

The other way I thought about doing it is to combine my controllers and my views since they work hand in hand, ie

/app_base
/models(Contains Pear_DBObjects generated models)
/controllers
/controller1
/view_template

How would you guys do this?
Am I just heading down a rabbit hole?

[bpat1434]

DOCUMENT_ROOT
|
+-- models
|
+-- smarty_include
|
+-- controllers
|
+-- themes
[indent]|
+-- views[/indent]

Or something to that effect. I might even take it one step further and say that all the regular files (like index.php) would be under the document root. Then, all the templates, and smarty code would be inside of the "themes" folder, and all other includes separated up into a directory called "incs".

~Brett