[Typo3-dev] drawbacks to using smarty in extensions?

Christian Jul Jensen christian at jul.net
Fri May 14 14:07:53 CEST 2004


"Leendert Brouwer [Netcreators]" <leendert at netcreators.nl> writes:

> "Ingmar Schlecht" <ingmars at web.de> wrote in message
> news:mailman.1.1084466673.28934.typo3-dev at lists.netfielders.de...
> 
> >
> > Well, the approach the article is talking about does not discourage
> > writing templates, however, it evangelizes the use of PHP as a
> > templating language.
> > Well, but I got your point and will shut up know ;-)

I read the article as well, and was of the same opinion untill I
actually started to work with smarty... I think it's very easy to work
with, it has an easy understandable syntax (close to php: nice for
programmers, simple: nice for designers). It has the best separation
of presentation and business logic, although it is possible to screw
this up, it somehow encourages this seperation.

Anyway, I've discussed that topic enough for this month already

> So, without getting into heated debates about whether or not using template
> engines is a good thing (had that debate a few times already), I'm assuming
> from the reactions that it would technically not lead to any difficulties
> within Typo3?

No. I'm currently implementing a project with it, works like a charm.

I did a nice litlle prefilter for smarty as well, that allows <!--{
and }--> as smarty tags, so you can hide the tags from the browser
when working on the template and hide.

I can mail it to you if you like.

--
Julle




More information about the TYPO3-dev mailing list