[TYPO3-ect] Voting: Classnames for BETA

[Elmar Hinz]

Hello Michael,

Michael Stucki wrote:

> Well, I have to admit that I have no idea what this is all about. Are just
> discussing the naming of a single extension? Or is it a request to change
> the coding guidelines? Just give me a pointer, please!

It's about extensions based on the lib/div libraries. It's not about coding
guidelines in general.

There are two reasons for this discussion in context of lib: 

1.) Jörg Schoppet prepares a PHP5 based autoloader for lib classes. A loader
needs a naming scheme.

2.) I am convinced, probably some others too, that the migration path of a
lib/div based extension can be reduced much, if we do some good decisions
now in a dialog with Robert.



> Every 4.x extension will require a full rewrite for 5.0 compatibility, so
> why should it pretend the opposite?

That is true, if you do it in the traditional 4.x way without further
reflection. 

I have to pretend the opposite and I think there are good reasons to do so.
By applying clean patterns and functional seperation, it can be possible to
nearly capsulate the need to rewrite to the model part of extensions.

> It may remove redundancy (consider Roberts comment about using lower-case
> which I agree with him). But given by the fact that the naming scheme will
> change for 5.0 again, I see no practical use in this change.

The naming scheme of 5.0 is already defined. I will use full v5 style in my
private extensions. That is:  ext/Rock/T3P_Rock_HardRock.php

If Robert doesn't change the coding guidlenes, I will be able to migrate a
part of my classes to v5 without even touching them. It's a different
question for the public naming scheme of lib/div extensions. That's what
this voting is about.

> 
> - michael

Kind regards

Elmar