On Apr 17, 2004, at 11:25 AM, Karen J. Cravens wrote:
On Sat, 17 Apr 2004, Puneet Kishor wrote:
PK>What is/are a typical circumstance(s) where I would not already know
PK>what vars exist in a template and would want to use query to find out?
It's the split between template and programming thing. I've considered
On Apr 17, 2004, at 11:18 AM, Roger Burton West wrote:
On Sat, Apr 17, 2004 at 11:10:35AM -0500, Puneet Kishor wrote:
What is/are a typical circumstance(s) where I would not already know what vars exist in a template and would want to use query to find out?
The most obvious case is the one in which someone else is being given the HTML design part of the job.
Interesting. I have approached this always with the attitude that I have to separate programming from display as much as possible. I've just finished a relatively complicated app -- a single cgi script about 2000 lines long, and about 45 different templates. My approach has been to create the templates in such a way that they could exist as a standalone website even if there was no H-T involved. In other words, if a designer-type decided to load the entire templates folder with its stylesheets and javascripts and whatnot in a designer-type program (GoLive or Dreamweaver, etc.), a complete, well-formed website would manifest, of course, with tmpl_vars intact. It may look a bit kooky since tables won't be fleshed out, and a few unavoidable tmpl_ifs won't be logic-ed out, but nonetheless -- it would be a website with all its links and scripts and behaviors and whatnot.
On Apr 17, 2004, at 11:25 AM, Karen J. Cravens wrote:
I can't speak to the original poster's exact situation, but I've been
mulling over something along these lines. Problem *I* have is that the
script really needs to know more than just the parm name... it should know
whether the end-user obeyed the form length, actually picked one of the
SELECT options or hand-built a bogus submission, things like that.
sure... the user's actions would arrive to you (the cgi) as cgi params. Most all decisions can be made based on those. In fact, even before that, quite a few illogical user acts can be trapped with judicious use of javascript.
On Apr 17, 2004, at 11:18 AM, Roger Burton West wrote:
ok. This might make sense. I've usually just rolled my own debug breakpoints simply because I am really scared of the perl debugger.A secondary case is general debugging - if the template passes the syntax check but doesn't show the expected results, it's helpful to be able to show H::T's idea of its internal structure.
Thanks folks, for your insights.
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Html-template-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/html-template-users
