CUFP
metaperl
snippet
<div class="Description">I repeat my <a href=https://rt.cpan.org/Ticket/Display.html?id=44105>bug report</a>:
<BLOCKQUOTE>
Not all templating systems are string-oriented. [mod://HTML::Seamstress] is not.
It works with HTML::Element instances.
As such, it would be nice if the result of filling in the form could be
returned as a tree for further processing by HTML::Element methods.
As it stands, I am forced to parse the results of [mod://HTML::FillInForm] back
into a tree (even though it was a tree before HTML::FillInForm
stringified it).
</BLOCKQUOTE>
Now, just consider how much is being done.
<OL>
<LI>seamstress has an HTML tree that it wants the form filled in on
<LI>seamstress converts this to a string
<LI>FillInForm parses the string into an HTML tree and then fills in the form
<LI>FillInForm converts the HTML tree to a string
<LI>seamstress re-parses the HTML for additional processing
</OL>
If FillInForm could receive and return trees, my apps would be much faster.
<P>
For the time being, I at least need to turn this multiline process into a single function call, so here it is.
<P>
Of course,
</div>
<CODE>
# https://rt.cpan.org/Ticket/Display.html?id=44105
sub tree_fillinform {
my ($tree, $hashref)=@_;
my $html = $tree->as_HTML;
my $new_html = HTML::FillInForm->fill(\$html, $hashref);
HTML::TreeBuilder->new_from_content($new_html);
}
</CODE>