ChangeLog is here:

http://tinymvc-php.googlecode.com/svn/trunk/NEWS

I'm using Smarty as my view layer. Just playing around, I adjusted my default controller so it will try to load a template straight from the URL, so for example:

http://www.domain.com/foobar
or:
http://www.domain.com/foobar.tpl

This will try to load a template named foobar.tpl. Likewise:

http://www.domain.com/foo/bar/baz
or:
http://www.domain.com/foo/bar/baz.tpl

Will load foo/bar/baz.tpl. If the path ends in slash:

http://www.domain.com/foo/bar/baz/

This will attempt to load foo/bar/baz/index.tpl

What purpose does this serve? It makes things SUPER easy for static content. Want a documentation page? Create documentation.tpl file, then just put /documentation in the URL, and it just works. Couple that with Smarty 3 and template inheritance, and things get pretty interesting! Of course if a controller file exists, that will get picked up by TinyMVC and go the normal controller processing route. This is basically for static content that does not require any prior variable assignments.

Here is the default controller I am using. This could easily be edited to work with straight up TinyMVC view files instead of Smarty templates, but you get the idea.

<?php

/**
 * default.php
 *
 * default application controller
 *
 * @package TinyMVC
 * @author Monte Ohrt
 */

class Default_Controller extends TinyMVC_Controller
{
  function index()
  {
        // be sure the uri library is autoloaded
$this->__call($this->uri->segment(1),array());
  }

  function __call($method,$args) {
// create a template path from the path info
// if template exists, display it
    $this->load->library('Smarty_Wrapper','smarty');
$tpl_path = $_SERVER['PATH_INFO'];
if(substr($tpl_path,-4) !== '.tpl') {
if(substr($tpl_path,-1)==DS)
$tpl_path .= 'index.tpl';
else
$tpl_path .= '.tpl';
}
if($this->smarty->templateExists($tpl_path)) {
$this->smarty->display($tpl_path);
} else {
     $this->smarty->assign('url',$_SERVER['REQUEST_URI']);
     $this->smarty->display('error.tpl');
}
  }

}

?>


quite a few things have changed internally in the SVN.

* The main bootstrap process now uses a class to perform the initialization, and house the entire MVC.
* the default c-based spl_autoload() is now used for speed. This means many internal file names/structure have been changed. Be sure to get a full svn update
* you can now control which controller/method (action) is used in the config instead of the url with $config['root_controller'] and $config['root_action']
* unknown actions now use $config['default_action'] as default, or 'index' if not given

* You can now access several things through the tmvc instance:

$tmvc = tmvc::instance();
$tmvc->controller // the controller object
$tmvc->action // the controller method being used
$tmvc->url_segments // the array built from path_info
$tmvc->config // the loaded config array

Please post any issues you may find!

[edit] also, exceptions are used for much error handling now, instead of trigger_error()

I just added simple URI routing to the SVN repository (four simple lines of code

Here is how it works:

Checkout SVN and update your code. (specifically, sysfiles/TinyMVC.php)
In your myapp/configs/application.php file, add:

/* URL routing, use preg_replace() compatible syntax */
$config['routing']['search'] =  array();
$config['routing']['replace'] = array();
Now TinyMVC respects these settings, and will do an internal replacement on the PATH_INFO (everything past the index.php). Use preg_replace() compatible format.

For example, if you want this:

/groups/list

to map to:

/groups/listing

you would create a route as such:

$config['routing']['search'] =  array('!list!');
$config['routing']['replace'] = array('listing');
Be sure to include delimiters in the search query.

You have to be careful with this, it does a simple preg_replace, so anywhere in your PATH_INFO, list will be replaced with listing. It may be wise to check for the slash prefix too:

$config['routing']['search'] =  array('!/list!');
$config['routing']['replace'] = array('/listing');
All rules for preg_replace apply, so if you want:

/groups/123

to map to:

/groups/view/id/123

You could do this:

$config['routing']['search'] =  array('!^/groups/(\d+)!');
$config['routing']['replace'] = array('/groups/view/id/${1}');
And of course, multiple replaces apply in the order they are given:

$config['routing']['search'] =  array(
  '!/list!',
  '!^/groups/(\d+)!'
  );
$config['routing']['replace'] = array(
  '/listing',
  '/groups/view/id/${1}'
  );

note: I thought about some nifty simplified syntax but to be honest, I saw no sense in crippling the power/speed of preg_replace(), and you should already know the syntax

Let me know how it goes! I will likely be putting out a new distribution soon.

TinyMVC has a new repository home, updated from CVS to SVN. Please use the new location:
svn checkout http://tinymvc-php.googlecode.com/svn/trunk/ tinymvc-php-read-only