[TYPO3-ect] Voting: Classnames for BETA

[Elmar Hinz]

Hi,

finally here comes my own voting:

>  [X] ext/Rock/T3P_Rock_HardRock.php        (Gimme five)



Reasons: 

The task of coding guidlines is to assist interoperability of software. They
are extremly important when applied to the fields where necessary. The task
is not to hinder technological progress.

I see few relevance of the file names of lib/div for the interoperablility
within v4. (In fact there are many file names of core components that
absolutely break with coding guidelines. But they still don't stop the
interoperability. It's important that the interfaces work smoothly.)

I see high relevance for the amount of work that is required, when finally
porting an extension to v5. The more filenames and classnames need to be
altered the more work has to be done. I would like to have an option to
reduce that work.

The primary targets of lib/div are to find an easy path of migration and to
improve the technological features for extension development. It's also to
abandon concepts that turned out to be inferior to other solutions like the
inflexible T3 templates in comparism to smarty.  

Naming annoyances" in the extension manager is a price that I think is
acceptable to pay with the perspective to save hours of file renamings
later. I don't pretend that a migration can be done without alteration of
the extensions at all. There will still enough work to be done. It's a
question of the amount of renamings and alterations for me.


Regards

Elmar