[TYPO3-core] Class namespaces with 6.0

Felix Kopp felix-source at phorax.com
Sat Aug 4 19:00:34 CEST 2012

On 04.08.12 12:43, Oliver Hader wrote:
> Hey everybody,
> ... and thanks for your detailed explanation and feedback so far.
> Currently we (Tom, Susi, Christian and me) are sitting in Fürth/DE to
> finalize the namespace schemes for TYPO3 6.0.
> However, one question still is basically unanswered - it's about our own
> namespace for "the current TYPO3" - "\TYPO3" is used by FLOW3 and
> Phoenix already, and if we once want to include FLOW3 packages to TYPO3
> 6.x/7.x, we will face conflicts (e.g. \TYPO3\Fluid which would be
> available in both projects, however with different source code).
> Thus, for TYPO3 6.0 we have currently two alternatives for "\TYPO3":
> * \T3 (example \T3\Backend\..., \T3\Fluid, ...)
> * \TYPO3CMS (example \TYPO3CMS\Backend\..., \T3\Fluid\...)

Then the namespace should be TYPO3.

The new product/phoenix if ready should receive a new name and 
corresponding namespace I suppose.

Cheers for the invested power already!

> We are going to take the decision today be able to continue with the
> whole task and be ready until the feature freeze in some days...
> So, if you have objections, questions, ideas or suggestions - then
> please speak up now. Thanks in advance for any feedback!
> Cheers,
> Olly
> Am 24.07.12 00:07, schrieb Christian Kuhn:
>> So, what do we aim for?
>> - Goal is a clean namespacing for all classes in the core, for example
>> under main topic '\TYPO3CMS'
>> - Goal is to become more close to the FLOW3 project, we want more easy
>> transition of code, and maybe even load packages from FLOW3 as is, or
>> the other way around
>> - We want no more naming clashes
>> - Goal is a clearly separated and indistinguishable naming scheme for
>> all core and core extension classes
>> - Goal is to get rid of evil class names that do not say a thing like
>> 't3lib_div' or 't3lib_tsStyleConfig' or 'tslib_content'.
>> - Goal is to define an easy definition for namespaces like
>> \vendor\extension to further reduce possible clashes

More information about the TYPO3-team-core mailing list