Symfony.. More Thoughts as I Continue to Play
Nov 26, 2009 · 2 minute readCategory: symfony
This is post is now quite old and the the information it contains may be out of date or innacurate.
If you find any errors or have any suggestions to update the information please let us know or create a pull request on GitHub
As it relies heavily on command line scripts, there is even room for further automation by creating my own custom scripts to chain together symfony commands. In fact I’m starting to feel like I wont need to do any PHP coding at all any more, just figure out the data model and run a custom shell script, and then issue the invoice!
Of course its not going to be that easy. For one thing, creating YAML files is still taking some getting used to. And deciphering errors on the command line is also taking some getting used to, even though they are probably the same old error messages. One thing that tripped me up was a typo in one of my YAML files that sent Propel looking for a non existant class when running the data-load command. That’s one of those “gotchas” that is bound to happen, but being so green it stumped me for a few minutes until I spotted the errant extra ‘l’ in one part of the YAML.
I now have some nice generated class structures with data models, and Netbeans’s autocomplete is making life even easier for me, suggesting object property getters as I type so I don’t even need to refer back to the schema to double check column names, cool.
Another thing I have noticed is the use of good old fashioned procedural style functions. This is good, because PHP lets you do this and why should you have to have absolutely everything inside a class when all you need is a little function that you can use here and there. Namely the template system uses functions like
<?php include_metas()?> and <?php echo url_for('module/action')?>
. I like this. I’m not a Java developer, I’m a PHP developer, so we can do this kind of thing :).