Yeah, sorry, but MODx is not going to be integrated into Symfony by me. Though Symfony has some lovely features, after evaluating Symfony, I was not impressed with the do it like we did in Java/Struts approach, nor was system performance what I expected, especially when using the Propel O/R mapping portion, which is just bloated with code and doesn’t offer any reasonable PHP 4/5 compatibility. It’s just too heavy on the framework side IMO, and MODx will be taking a slightly different, and I think, unique approach to rapid web application development with PHP; one that better fits the language itself.
In fact I rewrote the MODx core using Propel last December and the results were okay, but less than impressive. In my view, adopting Symfony/Propel would mean a significant trade-off in performance for a debatable gain in developer flexibility. With that in mind, I ended up writing an ultra-light O/R mapping system that specifically avoids using a query abstraction layer (Propel uses Creole for this), opting instead for encouraging any non-standard SQL logic to be optimized to the database platform being used. It will require work to port projects built on it because of this, but the end-result should be better-performing applications that can take advantage of platform specific features. This
xPDO project I’m describing is still in development, but already being used to power a number of client database applications in conjunction with MODx.
But feel free to port a version of MODx on over to Symfony if you want to. It would be interesting to see how they would fit together.
MODX Staff
MODX Staff