31–38 of 38 posts
Earlier quoted context omitted.
I'm not sure what you're getting at. Is there reason to believe that this will not work with PHP >= 5.3?
It will be is not structured using Namespaces, which can be annoying if you are using them on a day to day basis and want to integrate something like Yaf that doesn't use them.
I'm loving the documentation: http://us3.php.net/manual/en/yaf-loader.clearlocalnamespace....
PHP used to be minutely documented, with copious examples, which was why it was so easy to learn. Now, not so much, it seems.
This smells like another Zend product, and Zend framework was just a pain, in my experience.
Anyone else see that this looks almost identical to Zend Framework?
I'm loving the documentation: http://us3.php.net/manual/en/yaf-loader.clearlocalnamespace....
Class:nameOfFunction - *the Name of Function purpose*
$iterator = new RecursiveIteratorIterator(new RecursiveDirectoryIterator('/path/to/directory'), RecursiveIteratorIterator::SKIP_DOTS);
Why would anyone want to spend time figuring out this framework extension, or the OOP PHP stuff like SPL and Imagick, with no documentation, when there are plenty well established ones out there that have mountains of it?
One of the good things is it is not using the PHP namespace, e.g. use Zend\Controller\Action\HelperBroker;
It is interesting that there are no models. This seems to be a glorified front controller integrated with a templating engine. It is really cool that they did this as a PECL extension. I had a PHP framework many years ago that we considered converting to a PECL extension ( http://sourceforge.net/projects/cep/ ).
Generally, models can be left up to the developer to create based on business logic. Take for example, Zend Framework. It provides an active record like pattern in its Zend_Db_Table but expects the individual application to create the models that use (not inherit) Zend_Db_Table.