I'm itching to start working with Mason right away, but I know this is a bad plan. Need to give it a little time, go back a chapter and reread...I need a lot of mental logistics or else I go through a lot of mental gymnastics. I'm going to do something else, something explicitly unrelated to Mason, and then go back to the book before I start smashing components around and breaking stuff.
Today, that other thing is a programming project presented by ITA Software. It's concerning a palindrome containing all the letters of the alphabet. (And I would appreciate it greatly if anybody who finds this trivial would please not tell me how to solve it or what the word(s) is. Thank you.)
Not to be a party pooper (Score:1)
You might with to look at the differnences in your choices before proceding with Mason.
This kind of thing can mean the difference in your quality of life down the road.
Good Luck!
Re:Not to be a party pooper (Score:1)
one more that may be more relavant
cmp template systems [apache.org]Re:Not to be a party pooper (Score:1)
If you're implying that it's not wise to fall in love with a specific templating system, then consider that lesson taken -- I've already done work with HTML::Template, though it's not huge and advanced.
If you're implying that something about Mason is obviously inferior, I have yet to come across it, and would like to know about it as quickly as possible. Please let me know what it is, if this
------------------------------
You are what you think.
Re:Not to be a party pooper (Score:1)
I am a CGI::App user, but that is what works best for my needs, and they may not be the same as your's.
qq{The callback model can get a bit hairy when you have to code logic that can result in totally different content being returned. For example, if you have a system that processes some form input and takes the user to different pages depending on the data submitted. In these situations, it's easy to end up coding a spaghetti of includes and redirects, or putting what are really multiple pages in the same