It's interessting to see more people abandoning Ruby on Rails. Not that I have something against Ruby itself, but it really seems to me that RoR does not scale. Hope Twitter tries with PHP. ;)
I recently stumbled over reflecting private properties in PHP again. As you might know, this was not possible until now and if you tried this:
The yearly International PHP Conference in Frankfurt (or like I usually say: the family meeting) is approaching rapidly and I'd like to invite you to join me in my Hands on eZ Components full day workshop. The session will take place on the first workshop day, which is Sunday the 4th of November, and will provide 6 hours of bundled eZ Components knowledge to you.
When I returned from vacation, which already wasn't as relaxing as expected due to priate issues, I directly returned to a huge mess, which you might already have been noticing by the downtime of phpunit.de website.
Are you using my phpDocumentor for VIM plugin? Go ahead and stack it! :)
Almost 1 year ago I blogged about Ohloh, and eZ Components being registered there. Those days I just found it funny to see how they measure the project cost of open source projects based on the ammount of code contained and things. Recently I am actively watching Ohloh and I think, by now it becomes a serious project with real value for every involved party. The maintainers added many new features to Ohloh, since I last blogged about it, and many contributors started participating in the service. So, I want to revise my "review" of Ohloh from the last year and explain how I see it by now.
Jeff Moore posted an article on procata.com about getters, setters and real properties. I fully agree with him. Especially the usage of interceptors (__get()/__set()/__isset()/__call()) makes your API a lot more readable and comfortable, while maintaining the purpose behind getters and setters: Checking the correctness of values assigned to a property and wrapping around retrieval mechanisms for a property. I personally call the way of maintaining value-correctness for properties through interceptors virtual properties, which fits quite nice I think.
I wrote an article, that introduces the relation featuresw of our ORM compoenent "PersistentObject" to you, using a practical example application. For me the coolest feature of PersistentObject is, that the component does not require you're ORM enabled classes to inherit from a certain base to allow your objects to be stored in a database (made persistent). PersistentObject simply allows you to configure any of your applications objects to be persistent and you keep a nice an clean OO structure. If you are interessted in learning more, just follow my trip into PersistentObject on ez.no.
My friend Kore is going mad again. As usual, it has something to do with graphics... But this time in a completly different way than before: Kore created his own small programming language, which he named "kaforkl".
During my current exam phase I'm working on some tiny private project to relax after learning. In there I'm using a main controller class, which implements a singleton pattern and initializes several sub-controllers while being created. The singletons purpose is, that the other controllers can access to main controller and its functionality whenever they need, without storing a reference each. The code for the singleton looked about like this: