* Michael Graham <[EMAIL PROTECTED]> [2005-09-12 19:36]: > > > What is this incompatibility for? This makes me i.e. change all the > > references to HTML::FillInForm->fill > > Is it just HTML::FillInForm that's causing problems or are there other > problems with returnin a reference? > > I ask, because I'm thinking of making the "return a string" behaviour > optional. > > I was thinking that as a convenience, I might make > CGI::Application::Plugin::FillInForm accept a reference to a reference. > > So you would be able to write: > > my $html = $template->output; > $self->fill_form(\$html, ...); > > And not care about whether $html is already reference or not.
1. I have faced this problem only with HTML::FillInForm module. I also use templates with generating some complex SQL queries and I need output as a string, but there is no problem with dereferencing a scalarref. It looks very reasonable to me to let CAP::FillInForm accept both styles. Making returning a string by CAP::AnyTemplate as an option can be a little unnecessary and confusing. 2. BTW, I would expect CAP::AnyTemplate to have a kind of 'add_config' function. After importing my default enterprise configuration into cgiapp_init with 'config' function I would like sometimes to change some options like paths, cache etc. just before loading a template. As far as I know 'config' function clears all parameters and replaces with new ones. IMO there is a need for a function, that is able to change or add new parameters to the configuration defined earlier. Regards, Wojciech Pietron --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
