[TYPO3-ect] Your opinions upon keyname

Martin Schoenbeck ms.usenet.nospam at schoenbeck.de
Mon Mar 13 17:14:55 CET 2006


Hi Elmar,

Elmar Hinz schrieb:

> Without alterations of the manager tools we would need to use then:
> 
> tx_t3ext_div::whyNot()

That's no good idea. First, it's to long, second the TYPO3 connection in
the name is doubled. Either tx_something, if it's just another extension or
t3_something or t3something, if it's a basic part of TYPO3. 
 
> This is a long term decision. We may do the calls to the library often
> if all our usefull stuff is going into it. So it is worth some
> thoughts at least.

Names are critical. So it's always worth thinking about them in depth. In
my opinion it has to carry that the classes and objects are related to
TYPO3, which is done with tx_ as with t3. And it has to carry that it is a
basic part to build upon. While the latter would be fulfilled by embedding
ect, that doesn't bear any information about the reason but only about the
creator. Even though it would be another short form, something like 'cel'
for 'coordinated extension library' could put more emphasize on what this
libraries are going to be.

Martin
-- 
Bitte nicht an der E-Mail-Adresse fummeln, die paßt so.



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