A typical page that user would call, would fulfill the role of Controller - getting input, validating it, and then depending on input and general app state, calling the appropriate actions in different models, assembling all the presentation info received into a structure, which then gets passed to a View (we used Smarty for Views, and it worked quite OK).

something like (pseudoPHP):

AddressEntryManagement.php (controller class):
…
if (user input action is delete && $id is sane and some other checks)
{
$addr = new AddressEntry($id);
$addr->delete();
$VIEW['result']=’Success’;
}
… // other actions

$tpl= new Smarty(’AddressEntry.tpl’);

$tpl->assign(’DATA’,$VIEW);
$tpl->display();
=============
not entirely proper MVC maybe, but definitely loads better than the default approach used of simply making all the DB calls in the same place as presentation and controller.