[TYPO3-50-general] Beer3, really a good solution?

[Ernesto Baschny [cron IT]]

Fernando Arconada wrote: on 22.10.2008 10:42:
> Beer3 is the next-generation templating engine for the FLOW3 and TYPO3 
> projects.
> http://forge.typo3.org/wiki/package-beer3/Start
> 
> is Beer3 a good solution?
> 
> Sebastian Kurfürst and Bastian said that they had evaluated Smarty and 
> PHPtal and other and technically they have problems. But may be we need 
> to think not only about technical details. would be better a philosophy 
> similar to symfony? for example, smarty it is already a good solution, 
> with a huge amount of users and doc. May be smarty isnt the best 
> technically talking but could be the best for most of the users (you must 
> think that most of them already know it), also the investment in smarty 
> knowledge could be reused in other TYPO3 and non-TYPO3 projects.
> 
> If I could reuse the knowledge that i made in TYPO3 (cause TYPO3 use 
> other known frameworks) then it is easy for my to invest in TYPO3 cause 
> my investment it is protected
> 
> In my opinion:
> Lets get beer (smarty, xtemplate ....) but not BEER3

I used to think like that (being a Smarty fan for years). Recently I
changed to phptal and I was "there" in just one or two days. I don't
really see the burden to learn a templating engine markup. It is not
rocket science.

We need to think about our needs (as TYPO3 developers which will create
TYPO3!) also.

If we use smarty/phptal or other, we will need to adapt and "extend" it
to accomplish our tasks (even "stretch" it with stuff not possible there
right now). It will probably be more work than creating a brand new and
nice framework on our own which comes with exactly the syntax to "fit"
with TYPO3.

We need some nice "TypoScript-integration", we want to see and use the
FLOW3 MVC concept in the templating engine, we need localization and
internationalization in our templates, etc. I expect the "glue" needed
to make Smarty or phptal or any other existing templating engine provide
all those conectors to FLOW3 to be more complex than to learn (and
create) our brand new BEER3.

I think it is great that Sebastian and his team has come to this
conclusion and are wanting to work on that matter. Expect my input and
contribution, maybe even some coding if I have some time. :)

Cheers,
Ernesto