[TYPO3-ect] Voting: Classnames for BETA

[Joerg Schoppet]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Elmar Hinz wrote:
> Hi all,
> 
> now everybody had enough time to contribute his suggestions for the namings
> of BETA. I digested all suggestions and did a few tests with the extension
> manager. Now I ask you to vote for your favoured one of three alternatives. 
> 
> The first one is as v5 complient as possible. There is one message in the
> extension manager: "Naming annoyances".
> 
> The second one goes as far into that direction as possible without provoking
> error messages.
> 
> The third one is fully complient with the v4 coding guidelines.
> 
> 
>  [ ] ext/Rock/T3P_Rock_HardRock.php        (Gimme five)
> 
>  [ ] ext/Rock/tx_Rock_HardRock.php         (Robert)
> 
>  [ ] ext/rock/class.tx_rock_hardrock.php   (Ingo)
> 
> 
> Regards
> 
> Elmar
Hi,

so after a night of thinking about it I have to correct my vote to the
third one (Ingo).

Reasons:
After reading Roberts mail "TYPO3 5.0 and lib/div...", looking at the
actual code of TYPO3 5.0 and seeing the complains from Ingo I think the
following:

Actually, lib/div are TYPO3 4 extensions, which helps ext-developers to
use a lot of strong oo-pattern within there extensions. Even if TYPO3 5
will be out (somewhen in the future) the 4-branch will be alive for a
long time (IMHO). At this moment we have an extrem high count of
extensions in TER, even if only 50% are "meaningful", it will be a huge
task until only a small part of extensions will be available for 5.
Also, as Robert mentioned, and everybody can see in the code: The code
of 5 will not have so much similarities with the code of 4.
In 5 there will be a lot of the features, actually provided by lib/div,
provided by the core.

So the big question for me is, will lib/div be necessary for 5?

At the moment, I can not say! But it will be clear, that *EACH*
extension needs a rewrite. Important, for myself, is, that developers
learn from lib/div, how to program in an oo way (the concepts). Because
if the concepts are clear and understandable it will be easy for people
to move there extensions to 5 (in a conceptual way).

Naming Guidelines are necessary and because there are naming guidelines
for 4, I would use for the actual lib/div these naming guidelines.


Regards

Joerg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGzS8vq5Me6rRDqPURAg8KAJ4516ycTpTSJVM0Wd7XavX3z76QxQCfYY+S
ANhRC+89u90W4UT8wkp9E7o=
=i7hr
-----END PGP SIGNATURE-----