It is a subjective decision, but I agree with you that converting data values which are stored as kilobytes into a different human-readable format is something that should be in the view. In particular, you might decide to give users the option as to how they want that number displayed (straight kilobytes or human-readable), in which case it's definitely a view concern.

As to how to go about that, I would go with a template filter. You'd set up a function which accepts the number as input and returns the "pretty" formatted string. Then you set the option in your template configuration to call that function as a filter. Say you named your function pretty_size, then you'd do something like this:
$template = Template->new({ FILTERS => { 'pretty_size' => \&pretty_size, }, });
Update: Under Catalyst, that'd probably be somewhere in your view module, for example in TT.pm, e.g.:
__PACKAGE__->config({ #...existing config... FILTERS => { 'pretty_size' => \&pretty_size, }, });
And then, use | pretty size in your template directive to change the kilobytes value to your formatted string, for example if the data is in the template variable kilobytes:
<td>[% kilobytes | pretty_size %]</td>

In reply to Re: Catalyst & Pretty Data by bellaire
in thread Catalyst & Pretty Data by pileofrogs

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.