Skip Menu |

This queue is for tickets about the HTML-FillInForm CPAN distribution.

Report information
The Basics
Id: 44105
Status: rejected
Priority: 0/
Queue: HTML-FillInForm

People
Owner: MARKSTOS [...] cpan.org
Requestors: metaperl [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 2.00
Fixed in: (no value)



Subject: option to return a HTML::Element instead of string desired
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).
On Fri Mar 13 13:15:59 2009, TBONE wrote: Show quoted text
> 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.
It would also be nice if I could pass an HTML::Element instance to fillinform() instead of a string of HTML.
On Fri Mar 13 13:15:59 2009, TBONE wrote: Show quoted text
> 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).
TJ may disagree and re-open this, but my inclination is to reject this change request. HTML::FillInForm is an HTML processor, not an object processor. If you want something that takes objects or spits objects out, I think that's a great candidate for a sub-class, plugin, or separate project. I don't think it makes sense to add in the core HTML::FillInForm module. Mark (a new co-maintainer).