I am not saying you should move the HTML to a plugin, only the data-prep.

Looking at your example, I would return a your data already sorted and have everything in arrays of objects. Loop through your arrays and your data will be easier to work with in TT. Example;

[% USE MyPlugin;
   classifications = MyPlugin.classifications( data ); 
%]

[% FOREACH year = classifications %]
    <tr><td colspan=x>Year [% year.no %]</td></tr>

    [% FOREACH class = year.classes %]
        <tr><td>spacer</td><td colspan=x-1>Class [% class %]</td></tr>

        [% FOREACH sub_class = class.sub_classes %]
            <tr><td colspan=2>spacer</td><td colspan=x-2>Sub-Class [% 
+sub_class %]</td></tr>
            <tr>

            [% FOREACH element = sub_class.elements %]
                <td>[% element %]</td>

            [% END %]
        [% END %]
    [% END %]
[% END %]

[download]

As you can see this is a lot cleaner than what you are doing. You can get away with not using objects by just setting a variable which is reference to the nested hash. You should really avoid having to type all this to get the data you want.

FOREACH element IN data.$year.$class.$sub-class.keys.sort

[download]

In reply to Re^3: Reverse sort order in FOREACH in Template Toolkit by Herkum
in thread Reverse sort order in FOREACH in Template Toolkit by punch_card_don

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.