[TYPO3-ect] latest extension coding guidelines

[Ingo Renner]

Ries van Twisk wrote:

> Doing things MVC and OO is indeed not the TYPO3 way, but I do feel
> it's the right way, that was the whole intention of the extension.

My opinion is that MVC for sure is a good design pattern. But you can't 
use it for everything.

A thing that I especially don't like about lib/div is that it introduces 
or works around the TYPO3 standard templating mechanism by inserting PHP 
code into HTML templates.

In fact we have that modern template building concept to not have PHP 
within HTML and to let designer work on the HTML templates without the 
fear they could destroy something.

Even when doing MVC, lib/div could use the marker concept for templates. 
You could still have a marker ###SOME_TEXT### rendered by a PHP method 
$someObject->getSomeText().

IMO this would be more consistent with the rest of TYPO3 and what keeps 
me from using lib/div until this is resolved. There're some special ways 
in TYPO3 whether you like them or not that should be kept.

The other thing is that it is not PHP5. I mean if we're starting a MVC 
library, why do we use PHP4 then? If I remember right I've even seen 
comments in lib/div like "we can't do this or that because of PHP4" - so 
why using PHP4 at all? If you want to do serious MVC you should also go 
with PHP5. If you do things, do them right.

Other than that, for TYPO3 5.x things can change of course... but 
lib/div is still made for the 4.x branch, isn't it?!

Ingo