[TYPO3-ect] Controller for Typo3

[Elmar Hinz]

Joerg Schoppet schrieb:
> Hi all,
> 
> shortly I'm ready with a MVC-concept implementation, which was inspired
> a very, very little bit from the Zend Framework [1][2] and a lot from
> Michael Scharkow's implementation of a simple controller [3].
> Actually I'm at the point, that the only thing you have to do for a
> "normal" output (e.g. no ajax) is to define the pi1-class, which extends
> a lib-class, set the three variables (scriptRelPath, prefixId, extKey)
> and define a specialized controller-class.
> The complete execution is encapsulated.
> My last thing is the view-implementation.
> 

Hello Joerg,

we are doing this in parallel. So we can compare ideas and combine the
best of both in the end. My model is not so much inspired by Michaels
implementation but a little more by Zend Framework [1][2].

> 
> [1] http://framework.zend.com/
> [2] http://phparch.org/zftut
> [3] http://www.underused.org/code/a-simple-controller-class-for-typo3/
[4] http://www.php.net/manual/en/ref.simplexml.php


I have uploaded the current status this afternoon to TER.

Keys: div, lib


Controllers

I offer both front controllers and action controllers. Only bigger
projects need a front controller as additional switch. Each inherit
from a matching class.

Data carrier

Additionally i have implementet two central SPL classes for PHP4 to
prepare our code for PHP5. The target is to carry the data of the
model to the view. ArrayIterator and ArrayObject will be used as
DataIterator and DataObject.

Recursive data trees

I plan to provide recursive itarable SPL Objects. That can build a
data tree with nodes and leafs if you like.

Meta data

Each component can carray additional meta infomation (TCA parts) as
information tree that is accessible by xPath. [4]

This data trees are flexible enough to carry any possible data we
need, and very simple for beginners as long as you only use a single
node (a typical dataset).


Exchangable Views

We should offer exchangable views. The common interface between model
and view would be represented by the tree of iterable data carriers.

1.) My first type of view is currently implemented as PHP templates
like in [2].

2.) The next type we could implement, is the proposal of Franz Koch
the extended TYPO3 template:

###NAMEPART::NAMEPART::NAMEPART###
###NAMEPART::NAMEPART###

3.) Then there is clever proposal of Ernesto to deliver COA that are
configurable by


So far the current snapshot


Regards

Elmar