[TYPO3-dev] Official coding guidelines of TYPO3

Dan Osipov dosipov at phillyburbs.com
Mon Apr 20 15:37:13 CEST 2009


"X will be a number"

So it should be pi1, pi2, mod1, etc...

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Rik Willems wrote:
> Hi,
> 
> Good to see these guidelines in place. Will use them starting now.
> 
> One question from my side. It is unclear to me what is meant.
> On page 5 of the document this can be read:
> 
> piX/
> These directories contain Frontend plugins. If extension is generated by 
> the Kickstarter, X will be a number. It is recommended to give more 
> meaningful names to Frontend plugin directories.
> svX/
> These directories contain TYPO3 services. If extension is generated by 
> the Kickstarter, X will be a number. It is recommended to give more 
> meaningful names to service directories.
> modX/
> These directories commonly contain Backend modules. If extension is 
> generated by the Kickstarter, X will be substituted with a number. It is 
> recommended to give more meaningful names to Backend module directories.
> 
> All extensions in TER leave the X=1 or X=2 in place. Is it actually 
> meant that these directories should be rename to for instance 
> piNewsArchive?
> 
> Regards,
> Rik
> 
> Dmitry Dulepov schreef:
>> Hi!
>>
>> Andy Grunwald [wmdb] wrote:
>>> In my search for the official coding guidelines i`ve found 3 versions:
>>> typo3.org: last update: 28.04.2007 11:36
>>> http://typo3.org/documentation/document-library/core-documentation/doc_core_cgl/current/ 
>>>
>>>
>>> wiki.typo3.org: draft version
>>> http://wiki.typo3.org/index.php/TYPO3_Coding_Guidelines_-_Notes
>>>
>>> Dmitry Dulepovs blog: result of discussion by TYPO3-(Core-)Team
>>> http://dmitry-dulepov.com/article/get-typo3-coding-guidelines-here.html
>>>
>>> So i dont know which coding guidelines are to use. Any idea?
>>
>> Here is the recent draft that core team uses de facto:
>> http://forge.typo3.org/repositories/entry/typo3v4-core/Documentation/trunk/doc_core_cgl/doc/doc_core_cgl.sxw?format=raw 
>>
>>
>> It is awaiting approval from the TYPO3 core team leader.
>>




More information about the TYPO3-dev mailing list