[TYPO3-50-general] Old names in FLOW3 code

[Robert Lemke]

Am 10.03.2008 um 14:00 schrieb Martin Kutschker:

>> About the question "F3_" or "FLOW3_" ... yes, generally I prefer
>> speaking names but I don't see a problem using the shortcut here.  
>> Some class like
>> "FLOW3_FLOW3_Component_Manager" looks too ugly for me, don't you  
>> think?
>
> But why has the package name to repeat the top-level name space?
> FLOW3_Component_Manager seems to be nice :-)

Because FLOW3 is package itself. Currently a class name follows thise  
scheme:

NamespacePrefix_PackageName_ComponentName or
NamespacePrefix_PackageName_SubPackageName_ComponentName

e.g.

F3_TYPO3_Backend_Controller_Default
F3_TYPO3_DomainModel_Page
F3_FLOW3_Component_Manager
F3_TypoScript_Parser
F3_Installer_Controller_Default

The "F3" is only necessary because we can't be sure that "Installer"  
for example
is not already used.

> But it seems that I don't get quite the idea of the top-level name  
> space,
> because I wouldn't like to write my own app within FLOW3_.

Of course we could use "F3_" only for the official FLOW3 packages but  
again,
were to draw the line? In case of ZF it's easy: All parts of the Zend  
Framework
are provided by Zend, therefore they can use the "Zend_" prefix. But  
we won't
force that control - it should be possible to use any package provided  
by anyone.

robert
-- 
http://typo3.org/gimmefive
http://buzz.typo3.org/people/robert-lemke/