Re: [htmltmpl] Re: Patches for HTML-Template-2.5.tar.gz

[Sam T. <sa...@tr...>]

On Thu, 25 Jul 2002, David Kaufman wrote:

> i don't like having a complex expression in the value of an attribute called
> "name", either.  if the patch really improves expression evaluation speed,
> maybe it should be resubmitted as a patch for HTML::Template::Expr?  since
> we who don't use template expressions now can continue to simply not use
> HTML::Template::Expr, and get the best performance of all :-)

That would be one way to go, but I'll admit I'm hesitent.  I went a long
way to avoid eval()ing Perl code in HTML::Template:Expr.  Maybe that was a
mistake but I think I had some good reasons (security, speed, memory
usage).

> dangerous!, Sam? :-)  might it melt the browser or burn the users' fingers?
> heheh.  seriously, though.  systems evolve, and programs change.  if an html
> editor who maintains templates can "hard-code" or "override" a variable
> value in a template in 30 seconds, to alter it in a way that would normally
> require calling in the original programmer to change perl code, the only
> "danger" i see is the danger that, by giving the "users" of a system more
> control over (and therefore more responsibility for) the system, the
> programmers (us!) might be given LESS control, responsibility, and thus, pay
> :-)

You're right - I don't see HTML designers as "users" of the module in the
same way that Perl programmers are.  I see them as working in an entirely
different way - providing formatting for data provided by the Perl
programmer.  The system, by design, doesn't allow the HTML designer to
reconfigure the data structures coming from Perl.  This is the price we
pay for not having to work with HTML - we do have to work with the data!
In my perfect fantasy world each side has its domain, Perl and HTML, and
neither should be allowed undo influence on the other.

> by adding __count__ (and <tmpl default> and <tmpl_def>), i think we work
> toward making good on those claims, empowering HTML designers to do as
> much as possible without needing to re-hire us to alter the code.

I never made those claims.  I see HTML::Template as delivering a
collaborative environment between Perl coders and HTML designers.  I never
envisioned a system where either could "engineered out" at any stage of
the development.

-sam