|
Wednesday 28 May 2008 10:51:45 pm
Hi Piotrek I've recently gone through the process of preparing an extension for eZ Network certification and one of the requirements is that the code matches the eZ coding standards. It was difficult at first but you eventually get the hang of it (like most things). Most things are simple, but can be annoying if you used to something different. e.g. 4 spaces for indent, I usually use 2 and spaces around ( ) and after spaces after ',' in param lists. I found that some of the examples and explanations, especially the template coding were not detailed enough and had to make a best guess in many situations. I'm assuming that the eZ coding standards and the components ones are the same? Though I do note that the eZ ones want comments/inline docs in doxygen while I believe components use phpdoc. if you are working with a framework that employs a particular coding standard then I think you have to use it even if it means you are using different coding standards with in your organisation. I've advocated that the particular organisation I'm working for utilise the eZ coding standards for all new projects.
The guidelines I've been working to are found at
http://ez.no/services/eznetwork/development_guidelines
cheers
Bruce
My Blog: http://www.stuffandcontent.com/
Follow me on twitter: http://twitter.com/brucemorrison
Consolidated eZ Publish Feed : http://friendfeed.com/rooms/ez-publish
|