A couple more bugs have been found which must have been around for a while, actually. Not sure why noone picked those up or reported them, though.
Anyway, just a friendly reminder that it pays off to keep an eye on the bug tracker. Even if bugs are only fixed in the next release, the comments usually contain workarounds to avoid getting a cold.

On a different matter I’ve added another bean related method and also some new unit tests for bean handling.

The new method is called getBean($definition). It’s only a few lines of code, but allows to do something like this:

$obj = ZMBeanUtils::getBean('ZMObject#foo=bar&x=y');

After that, you’ll have an instance of ZMObject in $obj with the methods setFoo('bar'); and setX('y'); called.

First place where this is going to be used is as syntax tfor config options. Plugins will be able to specify widget classes and multiple properties to render the form elements of their configuration options.

Perhaps it will even be possible to extend the simple syntax [classname]#[property1=value1&proerty2value2&...] to reference existing objects?

Next on the list is to add support for this to the url mappings. That will allow to specify both controller and view properties without the need for more parameter (instead there will be less!)