This has been a big week for Mouf. Amongst the many packages that have been added this week, I'm proud to announce a brand new "html.renderer". This is a package (PHP 5.4+) that allow you to easily make your objects renderable in HTML.
The rendering system allows you to overload templates provided by package developers. It is a simple, yet powerful sy
Annotation are now widely used among a lot of languages and development frameworks.
At the begining, annotatations where used as standards for describing the code, and parsed by most IDEs in order to provide autocompletion:
Mouf 2 final release is approaching. Today, Mouf is getting support for injection in properties or setters defined in traits (that have been added in PHP 5.4).
Adding support for traits was less straightforward that initially thought (due to a strange behaviour of the Reflection API), but we hopefully found a workaround. You can now use a trait in your class
Being a Mouf developer, I have been quite heavily relying on the PHP Reflection API, and so far, I must say things were quite ok.
PHP provides a nice API to access your code structure through ReflectionClass, ReflectionMethod, ReflectionProperty, etc...
Recently, I started adding support for traits in Mouf. This means that I need to do some reflection on traits. In particular, I need to answer this question:
Mouf has had self-check validators for quite a long time now. And for quite a long time, it was possible to extend those validators in your packages.
It was possible, but not complely easy, as you add to write several conf files to set them up.
This time is over! Now, you can write your own validators in a breeze, just by extending one interface.
In this article, I will add every day what's new in the upcoming Mouf 2.0 release!
This article will be regularly updated as we add new features to Mouf 2.0
- The Mouf packaging system has been completely deprecated and replaced by Composer, that will very certainly become the new de-facto packaging standard.