[TYPO3-ect] New template standards WAS: Improvement of the template engine

[Elmar Hinz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

I try to summerize the discussion now. Talking is good, but one should come to
results in the end:

Results:

0.) Nobody proposes an improvement of the standard templating mechanisms with
the ###-pattern. Alternative template engines like smarty are much more advanced.

Crashcourse on Smarty: <http://smarty.php.net/crashcourse.php>

1.) The Konzept of Kasper and Elmar needs some plannings and preparings to be
realized. I propose to take up this thread as soon as Kasper can invest more
thoughts into the field of extension coordination after release of TYPO3 4.0.

2.) The Solution of Ernesto and Peter is a solution that can be reached with the
existing tools.  I will experiment with it and will publish it as a standard
solution in the next galileo handbook for developers. It would be (backward)
compatibel with the proposal of Kaspar and also the standards we want to find.

3.) Kai Laborenz has stressed the point, that it should be as easy to set up and
configure TYPO3 and that it is necessary for this, that extension configuration
allways follows the same scheme. This is right. On the other hand TYPO3 is an
enterprise system. It should stay most flexible and not reduce the
possibilities. That is why we have worked out 1.) and 2.).

Both targets can best be reached with following Best Practice Guidelines as
Ernest has already proposed. I volunteer to implement the proposals into the
Project Coding Guidelines as soon as decisions are made.


Still open:

The decisions have not been made. There are three worlds to combine.

Requirements of the 3 advocates:

1.) Ernesto: cObject as the heart of TYPO3 rendering, flexible and mighty.

2.) Kai: A xHtml based template, because that is the language most people
understand.

3.) Elmar: It should be possible to have simple output conditions on the
template level. The requirements, which conditions are needed, occur in the
moment of templating. The PHP developer can't foresee all possibilities.


Let's compare:

* The traditional ###-Templates answer to the requirements of: Kai
* cObjects answer to the requiremts of: Ernesto, Elmar
* Smarty (or similar) answers to the requirements of: Kai, Elmar

To combine all I come to the conclusion:

PHP => cObject => Smarty (or alternative)

That is very similar to Ernestos proposal:

PHP => cObject => XML



A Proposal for  standards:

1.) Export the data with cOjects
2.) Provide one smarty template

The advantages:

* The non TS world can template in xHtml
* The TS world can template in TS
* Conditions can be implemented in both cases


What stands against it? Bring in your drawbacks now!!!


Regards

Elmar































































- --
Climate change 2006 is killing people: floods in California, drought and fires
in Australia, Texas, Sahel, Oklahoma, South Africa. The Bush administration is
responsible for corruption of the Kyoto Protocol. The US majority is responsible
to the world for reelection of a convictable [...censored by Echelon...].

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD2ourO976RNoy/18RAv9hAKCIKHs2NZwXLww8Kp97I1154L796wCfb9X/
MZ8Q+xspMZVKY82r+bJkOeU=
=pl4u
-----END PGP SIGNATURE-----