We do something similar, with a little more structure. We have a parent class that all apps inherit from, and in that class we do something like this:
__PACKAGE__->reflect->addSlot(
tt_data => {},
perl_data => {},
);
This creates empty data slots that you can use as a sort of data store. In our code, we can then do things like this:
$self->perl_data->{pass_around} = 'some calculated data';
$self->tt_data->{some_stuff} = $self->get_some_stuff();
if ( $self->perl_data->{pass_around} ){
blah
This is basically a simple way to create object data that can be accessed from anywhere without having to pass it. We use separate structures for perl_data and tt_data as an internal standard. Data for the template goes in tt_data and internal data is in perl_data.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.