[TYPO3-ect] new version of smartyView

[ries van Twisk]

Hey Simon,

I have been using functions a lot for the reason
that it was more extendible for me..

This was particular the case when rendering images,
I simply gave the TS name of the image rendering object.
And I could generated images from smarty whenever
I needed it in any configuration.

I did the same for links aswell to give it a proper alt/title tag
on demand.

Can I do the same for 'your' method?

For example

{link open="blank"}Some link ID??{link}

Ries

On Oct 22, 2007, at 3:27 AM, Simon Tuck wrote:

> Hi Steffen,
>
> I have some feedback for the smartyView class:
>
> I have a minor issue with the render function:
> The parameter sent to the display method ($this->pathToTemplates .  
> '/' .
> $view) isn't wrong, but strictly speaking you shouldn't need to define
> the templates directory, the latest version of rtp_smarty will use the
> pathToTemplates declared in the controller. At best it's redundant, at
> worst running $view->render('my/other/path/myTemplate.tpl.html')  
> will fail.
>
> I have a basic issue regarding the printAsUrl method in the smartyView
> class. It's a matter of opinion, but I think it makes more sense to  
> use
> the Smarty tags {url} or {link}label{/link} than to start using PHP
> functions. The tags described above are provided via Smarty plugins
> which implement TYPO3 features (i.e. the {link} tag implements the
> typolink function). I think it would make sense if we could agree  
> on the
> approach here: do we include methods such as printAsUrl in the
> smartyView class or do we implement Smarty plugins that provide the
> equivalent functionality as tags in Smarty. What do you think?
>
> Cheers,
> Simon
>
> Steffen Kamper wrote:
>>
>> Any ideas from you for the smartyView are welcome ;-)
>>
>
>
>