note
MidLifeXis
<P>I agree mostly with that sentiment. However, I have found myself putting display oriented variables in my perl code lately.</P>
<P>For example, with HT, I would need to do a ...</P>
<CODE>
# In the perl
$template->param(SHOULD_I_DISPLAY_THIS => ($foo + $bar) > 2);
-------
<!-- In the template -->
<TMPL_IF SHOULD_I_DISPLAY_THIS>this</TMPL_IF>
</CODE>
<P>With HTE, I could use...</P>
<CODE>
<TMPL_IF EXPR="(FOO + BAR) > 2">this</TMPL_IF>
</CODE>
<P>It leaves the display decisions in the hands of the interface / html coder, and the data collection to the perl program. It is hard (you mentioned not having a TMPL_ELSIF) to do an N (where N>2) way decision, or a decision based on the quantity of something.</P>
<P>Another example...</P>
<P>Without creating display variables in your perl code (x_gt_3, x_gt_5, ...), how would you change the style of something based on its value?</P>
<UL>
<LI>Green if X < 3</LI>
<LI>orange if 3 <= X < 5</LI>
<LI>red if 5 <= X</LI>
</UL>
<P>As I said above, I typically don't like using HTE, but I am running into more instances where it could prove to be useful, and would remove some of the variables controling display from my perl code.</P>
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-272364">
<P>--MidLifeXis</P>
</div></div>
409012
409047