[Typo3-dev] how to create an individual search-form in an extension

[Jonas Dübi]

Hi

Dmitry Dulepov wrote:
> page.70.value = </div>
> ======================================
> is not the best way of templating. 

I don't talk about Templates for whole websites, I talked about 
extension templating...


> See "important thing" below. I only want to note that MTB (and
> TemplaVoila) is also "not TYPO3" way than :)
Your mixining up a lot of things. I'm talking about extension templates, 
and TemplaVoila is not even similar to the thing we'r talking about...

> Well, this is not the problem of PHP, this is a problem of the world...
I was talking about the problem, that most PHP code uses a completely 
different concept and to do similar things. There are only a few PHP 
programmers and projects which use clear patterns and frameworks...

I think that's because PHP is realy easy to learn. There are a lot of 
PHP programmers which doesn't even know OOP concept for real. You just 
don't need to read anything about programming concept to start hacking 
applications with PHP.

But I realy like PHP, because it's realy efficient and flexible...

> Well, I rather see it as connecting Ferrari engine to a BMW car. Gives
> new powers though may require integration effort.
If Typo3 is a BMW car and Smarty is a Ferrari Engine, why do you even 
drive BMW? Buy or build a porsche and you'll be happy. A BMW has a BMW 
engine, and a Porsche engine doesn't fit in, as long as you don't realy 
integrate it and replace the BMW engine...

> One important thing: I do not vote for Smarty to become TYPO3's template
> engine! This would be really bad idea. But I think (and proved to
> myself) that Smarty can be used as a local template engine in
> specialized plugins. Often this is much easier than MTB way.
If you use it for your own "user_" extensions, nobody will be bothered, 
but if you try to use it withing important wide spred used extensions, 
it's just not the right way.

> Actually Smarty templates is much easier to localize than MTB templates.
> Imagine that you need to put markers for each label in the template and
> replace them. Many of them! With Smarty I just added a custom extension
> function (PHP file with 5 lines in it) and now I can use text from
> locallang files directly in Smarty templates! One template works with
> all languages, I neither need to modify template, nor to add other
> templates when extension is translated or translation is modified.
Ok if MTB is such a crab, as you tell us, let's improve it. Everyone 
will be happy if you improve Typo3 Templating, and nobody will blame you 
if you take some ideas from smarty...

It's just my opinion not the holly grale :-)

Greets from switzerland