CakePHP is a wonderful framework. Recently I proved it to myself once again (not that I need much of that proof anyway). The problem that we had at work was a whole lot of code in once place and no obvious way of how to break that code into smaller, more manageable pieces. MVC is a fine architecture, but it wasn’t obvious to me how to apply it to larger projects.
In our particular case, we happen to have several data types, which are very similar to each other, yet should be treated differently. Two examples are:
- Client account registrations. Our application supports different types of accounts and each type has its own processing, forms, validations, etc. However, each type of account is still an account registration.
- Financial transactions. Our clients can send us money via a number of payment methods – credit cards, PayPal, bank wires, etc. Each type of the transaction has its own processing, forms, validations, etc. However, each type of the transaction is still a financial transaction of money coming in.
Having a separate model for each type of account or for each type of transaction seems excessive. There are differences between each type, but not enough to justify a separate model. Having a single model though means that it’ll continue to grow with each and every difference that needs to be coded in. Something like a class factory design pattern would solve the problem nicely, but the question is how to fit it into an existing MVC architecture. Read the rest of this post for a demonstration.
Continue reading “CakePHP : Building factories with models and behaviors”
I came across a plugin for CakePHP which helps to check if the certain code follows CakePHP coding style. While I haven’t tried it, I think the better way is to utilize CodeSniffer. As per PHP_CodeSniffer PEAR page:
Which basically means that PHP_CodeSniffer is a generic tool for validating your code. You can use for CakePHP, WordPress, or any other PHP project that you are working on. The best part is that you can create your own set of rules regarding coding style and then make sure that your team follows it. If you don’t care that much for your own rules, then you can use one of the many existing rulesets. Some of these come together with CodeSniffer package, others are available on the Web.
Setting up CodeSniffer for my team at work has been a long lasting TODO item, however it looks like I will be able to start working on this next week. Once it created, tested, and everyone is happy with it, we’ll have it in the pre-commit hook in our Subversion repository. This way, we will prevent commits of any code that does not follow our rules. Of course, I plan to only run CodeSniffer against the code that we wrote in-house. There is no need to re-format all the third-party code just for the sake of it. Plus, we are rarely doing any modifications of the third-party code at all.
Over the last couple of years I’ve been working a lot with these four applications – WordPress, CakePHP, SugarCRM, and RT. Each of these is beautiful in its own way. Each of these tools is an Open Source Software. Each of these tools has a large community. Each of these tools has a free and commercial support and development. Each of these can be used in a number of ways to solve a whole range of problems. Let me briefly introduce each one of them.
Continue reading “Toolbox : WordPress, CakePHP, SugarCRM, RT”