The second thing is that I wanted to keep all display-related logic in the template. Passing in the Date::Calc::Object instance into the template for each row is a good idea, but I wanted to have the template compare it to Today() and do the logic there.
The basic reason is that, eventually, I want to have a $preferences object that I pass in to the template and the template figures out all the display concerns.
Essentially, I view MVC as thus - the language that deals with the displaying (TT, in this case) should handle all logic that can be seen as display-related. Does that make sense?
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
In reply to Re: Re: Template Toolkit and Date plugin
by dragonchild
in thread Template Toolkit and Date plugin
by dragonchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |