[TYPO3-ect] Your opinions upon keyname

Ernesto Baschny [cron IT] ernst at cron-it.de
Mon Mar 13 16:10:27 CET 2006


Elmar Hinz schrieb am 12.03.2006 12:13:

> the first part of our common ECT library, the link class works pretty
> fine and has passed a lot of tests. Before anybody can work with it
> she want's security upon the persistance of registration key. Also to
> write documentation I would like to know the final keyname.> 
> Still we have not come to a solution that is carried by a broad conset
> of ECT supporters. So please bring in your opinion.
> 
> Variant A: ect
> Variant B: ext
> Variant C: ect_div + ect_lib
> Variant D: div + lib

I don't like "ect" in the name, because this is the name of the team, as
already said here. If we want to stress the fact to the "newbies" that
these classes are the "ect-approved" way of writing extensions, the name
has to be as generic as possible.

As Jean-Baptiste already suggested, I also would go for something like:

  t3ext_div::whyNot()    class: t3ext_link

And I don't think we need to have a new subdirectory for this. These
classes could simply be provided by an extension called "t3ext", which
should/could/must be shipped with future TYPO3 versions.

Cheers,
Ernesto



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