Your plan won't help you. TT concatenates all the output of a script to a single string before spitting it out. At least it does so until you tell it to do otherwise.

That hack might be useful, I'll definitely look into it. But won't avoiding populating those data structures in the first place potentially cut down on the size of the memory footprint at any given time? I'm still not certain that the returns will be worth the optimization, but it should be work something, shouldn't it?

Why do you use CGI::Prototype just to build a popup menu? Why not just use TT's loops and perhaps the DBI-Plugin?

Because we use CGI::Prototype for a whole lot more than loading popup menus :) otherwise your advice would be absolutely applicable. In fact, the generation of dropdowns is really view code, but it's complicated enough (lots of dropdowns loaded from the database) that a decision has been made to avoid doing too much of that type of heavy lifting in TT. It's not necessrily optimal, but that decision is mostly beyond my control. 

perl -e 'split//,q{john hurl, pest caretaker}and(map{print @_[$_]}(joi
+n(q{},map{sprintf(qq{%010u},$_)}(2**2*307*4993,5*101*641*5261,7*59*79
+*36997,13*17*71*45131,3**2*67*89*167*181))=~/\d{2}/g));'

[download]

In reply to Re^2: Passing a sth to CGI form element methods by agianni
in thread Passing a sth to CGI form element methods by agianni

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.