They say that Mathew Robertson, on or about 03.Dec.2006 19:27, declaimed:
> One could argue that a template variable of "user_some_funky_permission"
> should be created by the application. But then why should the
> application programmer create the cross-product of every template
> variable; it i
he kids say these days, it
teh r0xors. Or something like that.
Cheers,
Chris
--
Chris Beck - http://pacanukeha.blogspot.com
"I don't think anybody anticipated the breach of the levees."
- President Bush, September 1, 2005
---
T
ot_ of people come across the same issue with a framework and there
is a clear scenario that spans most people's use cases, then it makes sense to
do it in H:T.
H:T, in my view, is most useful to separate display from code. Adding more
layers and wrappers of code to affect display is counter-p
for the help. I am already using filters so I can embed tags
in form fields. I was just hoping for a new XHTML aware version :)
--
Chris Beck - http://pacanukeha.blogspot.com
Hanlon's Razor:
Never attribute to malice that which is adequately explained by stupidity.
--
Hey all,
Is there any way I could request that XHTML style also
be valid?
Cheers,
Chris
--
Chris Beck - http://pacanukeha.blogspot.com
"Privacy is what they take away when they want to torture you.
-- The Earl of Spencer
---
This S
w do people do cookies?
Cheers,
Chris
--
Chris Beck - http://pacanukeha.blogspot.com
The other day, in the park, I was wondering why frisbees look bigger and
bigger as they get closer to you. And then it hit me.
-- http://bash.org/?479067
---
ntent-Type: text/html\n\n";
> print $template->output;
>
> |
> |
> V
>
> Form.tmpl
> -
> - displays
> - user fills form
> - user presses submit
>
> |
> |
> V
>
> SubmitData.cgi
> -
> my $template = HT