Initial Import
Based on Mojavi b8ffc12c5e78d84d42a09a2580c197a941152475 - http://www.mojavi.org/
implement zimba's MultipleControllerFactory from Mojavi forums
http://forum.mojavi.org/index.php?showtopic=958&hl=xmlrpc
closes #1
implement EmailValidator
closes #7
implement DateValidator
closes #8
patch Controller for recursive global models
closes #4
patch ValidatorConfigHandler for required but not validated parameters
closes #5
implement PropelDatabase
closes #6
Projects Be Gone!
First round of changes required to implement ConsoleController.  Running into issues with getopt() on my build (entropy.ch) of PHP5, so I'm committing to see if other platforms have the same issues.
references #3, #4
remove a print_r I forgot to remove before committing.
references #2, #3
add an inCLI() method to Controller
references #2 #3
create a dev_unit_tests branch for.. umm.. Development of Unit Tests ;)
Initial working version of unit testing with PHPUnit2.
All tests must be run using phing (test target).
Moved www and webapp into samples dir (rename to examples?) 
Moved source/agavi to src and removed source dir (rename src to source?)
make tests working again after the directory restructuring
add tests for Validator and ParameterHolder.
add tests for Controller
make phpunit2 phing task ignore files below directories named "sandbox"
add tests/All.php , which can be run by phpunit command-line style.
turn phing's test target into using the xml output and xsl translation to create reports only, not display output on the console.
add etc directory for phpunit2 xsl files
add skeleton reports directory
throw PHPUnit2_Framework_IncompleteTestError if the test isn't written, since phpunit's regular output (ie when not called from phing) is nice about it.
swap order of args to assert calls, since the output indicates it's expecting the expectation first, and the input second.
commit up agavi-dist - script destined for /usr/bin or wherever.. that will call phing with agavi's src/build.xml
add src/build.xml - I figure this one will contain the "module/action buildler" target, and possibly the test target that could run webapp specific tests.