Re: [zeta-dev] Documenting our coding style
Hi,
On Fri, Nov 26, 2010 at 2:23 PM, Derick Rethans der...@apache.org wrote:
On Tue, 16 Nov 2010, Tobias Schlitt wrote:
for another project I needed to give advice on the coding standard used
by Apache Zeta Components. There is some very old version of the eZ
Publish coding style in [1] (from 2001) but no reliable, recent source.
So I think we should document our coding style on the website.
Please complete / correct my following brainstorming:
- Indentation with 4 spaces
- After a {
- On breakup of long lines ( 78 chars) after a (
- { and } on a new line
- 1 space after ( and before )
- No space after [ and before ]
- 1 space after ,
- 1 space before and after .
- Almost always camelCase
- classes always start with ezc followed by an upper case char
- constants all in upper case with _
There is also a script at
http://svn.apache.org/repos/asf/incubator/zetacomponents/scripts/syntax-check.sh
that has a few rough automated checks.
I remember I used a PHP Code Sniffer standard for ZC is it still
available somewhere ?
I tried the old URL and it seems it's no longer there.
Best Regards,
--
Jérôme Renard
http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Documenting our coding style
I saved in my bookmarks this one : http://pear.xplib.de/get/
http://pear.xplib.de/get/Max
2010/11/27 Jerome Renard jerome.ren...@gmail.com
Hi,
On Fri, Nov 26, 2010 at 2:23 PM, Derick Rethans der...@apache.org wrote:
On Tue, 16 Nov 2010, Tobias Schlitt wrote:
for another project I needed to give advice on the coding standard used
by Apache Zeta Components. There is some very old version of the eZ
Publish coding style in [1] (from 2001) but no reliable, recent source.
So I think we should document our coding style on the website.
Please complete / correct my following brainstorming:
- Indentation with 4 spaces
- After a {
- On breakup of long lines ( 78 chars) after a (
- { and } on a new line
- 1 space after ( and before )
- No space after [ and before ]
- 1 space after ,
- 1 space before and after .
- Almost always camelCase
- classes always start with ezc followed by an upper case char
- constants all in upper case with _
There is also a script at
http://svn.apache.org/repos/asf/incubator/zetacomponents/scripts/syntax-check.sh
that has a few rough automated checks.
I remember I used a PHP Code Sniffer standard for ZC is it still
available somewhere ?
I tried the old URL and it seems it's no longer there.
Best Regards,
--
Jérôme Renard
http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Documenting our coding style
Maxime, On Sat, Nov 27, 2010 at 10:29 AM, Maxime Thomas maxime.t...@gmail.com wrote: I saved in my bookmarks this one : http://pear.xplib.de/get/ http://pear.xplib.de/get/Max Cool, thanks :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] PHPUnit's usage
Hi Sebastian, On Sat, Nov 27, 2010 at 10:57 AM, Sebastian Bergmann sebast...@apache.org wrote: Am 27.11.2010 10:51, schrieb Jerome Renard: for those of you who are forced (like me) to use PHPUnit 3.4.* and can not (or do not want to) upgrade, you can run the following command to restore the PHPUnit 3.4.* compatible version of UnitTest/ Why are you forced to use PHPUnit 3.4? Because I work on something else that seems to be incompatible with the latest PHPUnit stable version. And since I can not commit fixes I am stuck with PHPUnit 3.4 Hopefully that will be fixed in a couple of weeks :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Survey on PHP library release modes
Hi Tobias, On Sat, Nov 27, 2010 at 7:40 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I'm about to start a little online survey to check out how users in the PHP world would love to see their favorite libraries being released. I'll mainly do this out of private interest, but it might also help us to optimize our release process. Excellent idea :) Find below some questions for discussion. Whenever there is no additional info, only a single answer may be chosen. 1. Which libraries / frameworks do you use? (multiple answers possible) - ADOdb - Apache Zeta Components - Cake PHP - CodeIgniter - Doctrine 1 - Doctrine 2 - eZ Components - Horde - PEAR - Propel - Seagull - Symfony - Zend Framework - Another framework / library (free text) - I code everything on my own 2. What is your preferred way of installing PHP libraries? - PEAR - Custom installer - Manual download - OS based package management I would just add something like (apt-get, yum, rpm), just to avoid any confusion from beginner users. - Version control (SVN external, Git sub-module, etc.) - Something else (free Text) 3. Do you prefer bundles over single component installs? - I want to install each component separately - I want a bundle with all components from a library 4. How would you expect a PHP library project to do releases? - Irregularly whenever something is ready - Regularly with multiple additions bundled 5. How do you want to deploy PHP library components? - I bundle library components with my application - I deploy libraries and application separately Do you have anything to add / change? Even though I think it looks really good, would you think relevant to add a question about depedency ? For example framework needs external dependency X or Y. How do they prefer installing this dependency ? Possible options: - via PEAR - I want to get it bundled with the framework - I want to install it manually Not sure I am completely clear here. If it's not just tell me :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard
Re: [zeta-dev] Survey on PHP library release modes
2010/11/27 Jerome Renard jerome.ren...@gmail.com Hi Tobias, On Sat, Nov 27, 2010 at 7:40 PM, Tobias Schlitt tob...@schlitt.info wrote: Hi, I'm about to start a little online survey to check out how users in the PHP world would love to see their favorite libraries being released. I'll mainly do this out of private interest, but it might also help us to optimize our release process. Excellent idea :) Find below some questions for discussion. Whenever there is no additional info, only a single answer may be chosen. 1. Which libraries / frameworks do you use? (multiple answers possible) - ADOdb - Apache Zeta Components - Cake PHP - CodeIgniter - Doctrine 1 - Doctrine 2 - eZ Components - Horde - PEAR - Propel - Seagull - Symfony - Zend Framework - Another framework / library (free text) - I code everything on my own 2. What is your preferred way of installing PHP libraries? - PEAR - Custom installer - Manual download - OS based package management I would just add something like (apt-get, yum, rpm), just to avoid any confusion from beginner users. - Version control (SVN external, Git sub-module, etc.) - Something else (free Text) 3. Do you prefer bundles over single component installs? - I want to install each component separately - I want a bundle with all components from a library 4. How would you expect a PHP library project to do releases? - Irregularly whenever something is ready - Regularly with multiple additions bundled 5. How do you want to deploy PHP library components? - I bundle library components with my application - I deploy libraries and application separately Do you have anything to add / change? Even though I think it looks really good, would you think relevant to add a question about depedency ? For example framework needs external dependency X or Y. How do they prefer installing this dependency ? Possible options: - via PEAR - I want to get it bundled with the framework - I want to install it manually Not sure I am completely clear here. If it's not just tell me :) -- Jérôme Renard http://39web.fr | http://jrenard.info | http://twitter.com/jeromerenard Excellent idea. We can also ask : - the job of the person answering : system admin / webmaster / not IT - the platform : Unix / Linux systems or Windows - the level of industrialization : tailor made platform (you have every things installed as you want), shared platform (the web hosting company has decided for you you what you can do or not), generic platform (you grouped some of your application and factorize software layers : using PEAR, Zend or whatever). I think we have to segment the survey's answer because some will use it in one way and other in the other way. Will you publish the results of the survey ? Maxime maxime.tho...@wascou.org | www.wascou.org | http://twitter.com/wascou
