[TYPO3-ect] naming conventions

Elmar Hinz elmar.DOT.hinz at team.MINUS.red.DOT.net
Fri Mar 10 17:56:51 CET 2006


Ingo Renner schrieb:
> Am Fri, 10 Mar 2006 15:18:34 +0100 schrieb Elmar Hinz:
> 
> 
>>ext_div::whatEver() could indeed be a solution. It is short enough
>>that I would enjoy to work with it.
>>
>>Combining both we could come to the extension key "div" with the
>>usage: tx_div::whatEver().
> 
> 
> what I meant is "ext" as your new namespace if you choose any at all...
> so that ext_div would be the similar to t3lib_div or ext_fe like tslib_fe
> but that would also require a new folder in the rootlevel I think which

The 3 proposals all have this same pattern in their call:
xxx_yyy::zzz() but only two need an own namespace.

Following the repository organisation of PEAR a new namespace would
indeed require an own folder. TYPO3 doesn't follow this PEAR pattern.

PEAR:
-----------------------------------
Category_Package
Category/Package.php
Category/Package/packagehelper.php  // case !!!!

still similar to PEAR:
-----------------------------------
t3lib_div
t3lib/class.t3lib_div.php

not PEAR but confusing:
-----------------------------------
tx_ccdebug_pi1
ext/cc_debug/pi1/class.tx_ccdebug_pi1.php


no extra folder necessary but nice:
-----------------------------------

ect_div
ext/ect_div/class.ect_div.php
ect/class.ect_div.php

ext_div
ext/ext_div/class.ext_div.php

tx_div
ext/div/class.tx_div.php



> would be hard to explain to the coredevs...
> 

If coredevs would not give others the necessary space to work in, they
will not be surprised if others can't support the project ... That
depends on the targets they have ....













More information about the TYPO3-team-extension-coordination mailing list