made a copy
implemented skeleton for request param passing to (Action|View)::execute(). Validation is not yet a filter; not even sure if we need that, but it won't be a problem to implement it. works already. refs #206
changed sample app to follow new method for retrieving request params, refs #206
changed tests to new /ActionStack(Entry)?/ behavior#
fully adjusted sample app to follow new request parameter approach
changed code templates execute() methods to accept request parameters
made AgaviParameterHolder non-abstract and added a constructor that accepts an array of paramters to be set right away
changed array of request parameters that is passed to /(Action|View)::execute(.*)?\(\)/ to a ParameterHolder
changed sample app to use new request params retrieval method
merged in changes from trunk since a5cbddceb0949e849eb6b7cd2da533a1e76f3b89
merged in changes from trunk
fix e_strict due to date() usage (switched to gmdate())
replaced the other class names with __CLASS__
fixed the ReturnArrayConfigHandlerTest
views will now auto-forward request attributes to the templates
clear global attribute namespace at the end of a forward() call
Changed the array parameter to AgaviParameterHolder in View::execute
Changed the array parameter to AgaviParameterHolder in Action::execute
Removed unnecessary attribute forwarding. This is already done in initialize().
->setAttribute() and friends inside Actions, those will be auto-forwarded to the View. And no more accessing Parameters inside execute(). That will break your apps, my apologies. Enjoy the exceptions.
reverted fix from #684 this broke calling "/" w/o rewriting