[TYPO3-ect] New template standards
Elmar Hinz
elmar.DOT.hinz at team.MINUS.red.DOT.net
Mon Jan 30 07:55:01 CET 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hallo Patrick,
Patrick Gaumond schrieb:
> Elmar Hinz wrote:
>
>> 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.
>
>
> AFAIfeel...
>
> I don't really like the idea of having PHP on the template level.
Did I really propose PHP on the template level? No, I proposed smarty, the most
establish templating engine in the PHP world, maybe in the overall world. It is
only indircet usage of PHP. But there are others possible, too.
>
> Saying to your clients "sorry I've updated your template and now the
> server is gone...".
>
I expect that smarty is seasoned enough not to let the server go. By the way, a
professional would not develop on the life server.
> I've always like the idea of complete separation between HTML and TYPO3
> and still like the idea of Mr. Raphael not knowing how Mr Benoit use his
> work... ; )
>
I like a separation between the tasks of the extension programmer and the tasks
of the interface builder. It can't be that Mr. Benoit needs to allways ask Mr.
Raphael to modify the extension only because he want's to do a new combination
of the templates.
It also can't work that the extension programmer is expected to forsee all
possible combinations of the templates and to provide an nearly unlimited number
of premade conditions in anticipation. In a bigger extension he never can't
provide all usefull combinations.
It may be that some or other "Mr. Benoit" can tolerate to display inclompete
addresses, headers without content below them or empty table data. If he does
his work seriously he can't tolerate such defect output. He want's to decide
himself from aspects of the interface designer under wich conditions to display
what.
You may argu that there shouldn't be empty fields in the database. But that
isn't real life. No user would practically accept a form with all fields set to
mandatory. It mostly would not make any sense.
> Do we really need a fourth way of templating ?
>
> Patrick
Not a fourth way, but a better way. In the original title I was asking for
improvement of the templete engine. Nobody proposed an improvement. You
difficultly can improve a system that is constructed on a ###something###
pattern. I would be the reinvention of the wheel, when there is a standard like
smarty available.
The practical porposals were to use TS or a combination of TS and the
HTML-template.
Does Mr. Raphael prefer to struggle with TS and HTML at the same time?
Or does he prefer to do it all in one kind of template?
That is the question. From the point of productivity I think the answer is a
clear one.
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
iD8DBQFD3bhEO976RNoy/18RAhh9AJ9QXCkJoV0pW+BnRPzljL6KokTxawCg32hJ
gyAiuFXlY3ctIafSq/trB70=
=TJLF
-----END PGP SIGNATURE-----
More information about the TYPO3-team-extension-coordination
mailing list