comment on

I repeat my bug report:

Not all templating systems are string-oriented. 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 HTML::FillInForm back into a tree (even though it was a tree before HTML::FillInForm stringified it).

Now, just consider how much is being done.

seamstress has an HTML tree that it wants the form filled in on
seamstress converts this to a string
FillInForm parses the string into an HTML tree and then fills in the form
FillInForm converts the HTML tree to a string
seamstress re-parses the HTML for additional processing

If FillInForm could receive and return trees, my apps would be much faster.

For the time being, I at least need to turn this multiline process into a single function call, so here it is.

Of course,

# 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);

}
[download]

In reply to tree-oriented use of HTML::FillInForm by metaperl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks