Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Re: Organizational strategies when using HTML::Template

by thraxil (Prior)
on Jan 10, 2004 at 22:08 UTC ( #320388=note: print w/replies, xml ) Need Help??


in reply to Organizational strategies when using HTML::Template

i prefer to just have a 'templates' subdirectory in each application's directory that contains the templates and use CVS to let the designers tweak them. then i'm the only one who can update the production site and i only do so after testing on a staging site. that will prevent the designers from ever really screwing up something production. when you first try to teach your designers how to use CVS, they may kick and scream a bit and don't be alarmed if blood streams out of their eyes and ears, but eventually they'll usually manage to understand enough to do a basic 'cvs commit' and 'cvs update'.

however you do it, i'd also recommend having a function somewhere in a common library that lets you just call it like my $template = template("foo_template.tmpl") and returns the loaded HTML::Template object with all the options you want and with the template file from whatever template directory you've settled on. this will prevent you from accidently forgetting to add 'die_on_bad_params' or 'loop_context_vars' every time (if you want them) and it makes it easier if you change your mind on where your templates live later on.

  • Comment on Re: Organizational strategies when using HTML::Template

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://320388]
help
Chatterbox?
[tye]: I don't know if you can just dismount, but I thought so.
[davido]: yeah, umount -f isn't powerful enough.
[tye]: probably something in the init subsystem that does the mounting that you could disable and reboot.
davido needs to close laptop to board flight home from yapc.
[davido]: I'll look into it in a few hours probably.
[davido]: when i do get to that point I think I'll do it in a vm snapshot just in case. :)
[oiskuu]: tye, you were right: loginuid/sessionid are part of task struct if compiled with AUDITSYSCALL. I have some doubts if you should actually depend on that feature.
[Corion]: oiskuu: Depends on what you want to do with that information
[tye]: I'm not depending on that feature. But I could in this environment. I'm using getlogin(). shrug
[Corion]: For benign logging (which user started this DB instance), it's OK

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (5)
As of 2017-06-23 20:06 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How many monitors do you use while coding?















    Results (555 votes). Check out past polls.