Kohana Forums

i have heard its easy enough to implement it with Kohana, try this link

It can look pretty good with use of short tags

<dl class="videos">
<? foreach ($product->videos as $video): ?>

    <dt>Video: <?=$video->track ?></dt>
    <dd><?=$video->title ?>. <?=$video->description ?></dd>

<? endforeach; ?>
</dl>

with in my editor it looks like this:

Discussions about template engine always make good troll. Let's feed it ;)

I definitely agree with yinkei : in a server environment where you have full control over configuration (like Geert says), using php short tag is the way to go. PHP is a template engine by itself.

Posted By: Isaiah

PHP is a template engine by itself.

I agree! However there are still times when you need a template system. Templates are very useful when you want to limit what someone can do, for example I recently finished a Kohana based project that allowed the user to customize an email template before sending it. I don't want to give them full access to the php interpreter, so I used the Temper library to give them access to a few different tags.

Yes, in that case a tempting system would make sense.

@Delapouite: I could be wrong, but don't most web hosts allow you to either set php ini options either via .htaccess or ini_set() ? I am not familiar with shared hosting.

Thanks groadin, Dwoo looks very interesting.
Just one question (or simply an observation). It seems that Dwoo can handle arrays rather than objects; so we should pass/convert objects into arrays to be treaten in Dwoo, isn't it?

Ah, OK. So, the "{$array.element}" form is simply a shortcut served by Dwow to access handle arrays.

Posted By: alle

Ah, OK. So, the "{$array.element}" form is simply a shortcut served by Dwow to access handle arrays.

Yes, Dwoo is very similar to Smarty in syntax, but also supports PHP syntax {$array['element']}, or {foo($bar)} for functions. You can read more in Dwoo wiki docs, they are not comprehensive though.

I'm looking at a way to offer some 'create your own template' functionality in my app. Users would be able to create their own HTML/CSS and the app would insert the output into user defined places in the HTML. Allowing users to write PHP in their templates would be a bit of a security risk :-) so I'm looking at some sort of templating.

The main thing is; there would be a limited list of tags that the user can place in their HTML ([%%author], [%%date], [%%blogpost], [%%home_link] etc) so there's no need for anything complicated.

Now I'm thinking of two options:

1) Upon request: Load template. Run a preg_replace_callback and have the callback return the right code. Push the template into an empty Kohana view file ( <?php echo $view; ?>) and have the view rendered as normal.

2) Upon uploading template: turn template into Kohana View supported code - remove any user inserted PHP and replace all [%%..] code by actual PHP code ([%%author] would become <?php echo $author; ?>. Upon request: use view as a regular Kohana view.

What about these approaches?! Would the 2nd be significantly faster because it doesn't use any pregs on rendering?! Any other suggestions? I'm looking for simple and fast :-).