[TYPO3-ect] Controller for Typo3

[Michael Scharkow]

Elmar Hinz wrote:

> I am neither working on models, nor I am working view methods. I am
> precisly working on a flexible but fully standardized interface
> between them.
> 
> This interface has already been defined by Marcus Boerger:
> 
> http://www.php.net/~helly/php/ext/spl/classRecursiveIteratorIterator.html
> 
> ( In fact I am thinking of a simple list of such
> RecursiveIteratorIterators.)
> 
> 
> * It is a PHP standard.
> 
> * It has an builtin interface for foreach-loops.
> 
> * It can transport more complex data then a simple result set, just a
> tree of sets (comparable to xml structure)
> 
> * Such a tree of sets can result from join queries. It represents
> still a single result complex, reorganized by relations between the
> objects. Multiple results can return more than one of this objecttrees.
> 
> * If to complex for beginners or simple applications, then just use a
> single object like any resultset.

Okay, I admit that I have no idea of how that relates to the controller 
mechanism but I wait for an actual (pseudo)-code example. All this 
interfaces and abstraction makes my mind boggle ;)

> Read my post about "Inversion of control" for the BE from yesterday
> specially for you. I think we need a container first.

I read your post and also thought about that: Either make the BE one 
controller that calls the modules or leave all modules as standalone 
scripts that inherit form a BE controller that provides the necessary 
infrastructure as auth, rendering the modules frame and the page tree...

Both seem like a hell of a lot of work but need to be done anyway if we 
want to get rid of the frames in BE.




>>That is easy simple enough but needs to be done before we think about
>>views (I'd like a smarty view though ;)) and models.
>>
>>Two questions still:
>>1. Joerg, where is your code?
> 
> 
> I have already seen it. :-)
> 
> 
>>2. Elmar, what's the difference between front and action controllers?
> 
> 
> The Zend style answer to "controller recursion"? See the mentiond
> article.

Ah, okay. I didn't see the need to give the controllers different names 
but this is what I meant.

>>Why bother with PHP4?
> 
> 
> I still have customers that run on php4 and I can't forsee when they
> will upgrade. A lot of people think "Never change a runnig system".

Argh, the dreaded legacy ;) I tend to be a lot less conservative here 
because a) PHP5 has been out for ages and b) I don't see the point in 
implementing all goodies from PHP5 in PHP4 because it wastes development 
time. Let's see how much PHP5 is really needed, though.

Greetings,
Michael