Learning about CGI::Application, specifically how to combine it with HTML::Template. Call me crazy, but this looks like a fairly powerful solution I'd be able to use anywhere that provides Perl at all. (Mason and Embperl and whatnot all seem to require lots of other funky things (and yes, I realize Mason can be used as a straightforward template solution, but I don't want to do that, it feels like a waste) or else have a learning curve I haven't quite managed to travel much of yet. (Despite being essentially finished with my first reading of the Mason book, I still have these very vague notions of what I can do with it, and my urges waver between wanting to learn how to use Bricolage and wanting to learn how to use Mason itself. It won't go away, but for now I want some quick results, plus I've been meaning to get around to fiddling with CGI::Application for a while now.)
Felt like tossing _On The Night_ into the CD player tonight. I haven't listened to it in ages, and I realize now that I kinda miss it. Haunting in places and cavalier in others.
Not really tired. Felt tired all day at work. Cranky is a very understated way of putting how I was -- I was actively angry with just about everybody I had to talk with, and that makes for a bad, bad day sometimes. I got lucky this time.
I spoke with my father last night, and he tried again to convince me I should be writing. I'm not at all convinced.
CGI::Application (Score:1)
Good luck!
CromeDome
No need to appologize! (Score:2)
Welcome aboard.
-sam
Re:No need to appologize! (Score:1)
I don't see it as that, frankly. I see it as different tools for different jobs. I don't see why I can't standardize my use of CGI with CGI::Application and my use of HTML through HTML::Template, considering that they're both pretty easy to have anywhere.
However, should I need to have components that stay in memory for quick use and work in a mod_perl-enabled env
------------------------------
You are what you think.