When you want something nested you have to render the sub-templates within the controller, add the resulting html as variables to the main template ...

*sigh* been there, done that. i was working with a template system (which basically was implemented as just a big regex), which actually supported nesting, but usually you would put together big loops in the perl script, because template-loops were slow. the whole templating was

• slow (as some of you might know, that hurt me as a performance freak)
• it had no elsif tag and other nice features
• it was unreadable - no possibility to put whitespace in the tags, and together with the missing elsif-tag that forced you to write veeeeery long lines with nested if/else and no whitespace
• it never died - wrong nested tags were just ignored, and it was difficult to find out where the error in the template was

my sin? i critisiced the system and basically said that any templating out there on cpan would be a better choice. from other jobs i knew that it is often ok to gripe about the templating system because everybody knew it was bad and only there because of historical reasons. here, though, i think i offended the one who had written it. also i suggested my own templating system on cpan, and starting at a company and basically saying "your templating is bad, mine is better" is probably not the best you can do. my learning: try to be more diplomatic.

i quit because it was, besides from the templating, very limited on what modules you were allowed to use. the company has a very successful website, and i was convinced at that time that the system could be made more comfortable for the programmers in order to get new features in faster. i still think that and i hope for the company that someday it will happen because otherwise it is very likely that someday a php/ruby/python/java guy comes along and just replaces the whole system. and it would be a pity to lose such a successful perl-powered website to a different language.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.