Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Ovid (2709)

  (email not shown publicly)
AOL IM: ovidperl (Add Buddy, Send Message)

Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.

Journal of Ovid (2709)

Saturday October 02, 2004
02:05 AM

Perl Template Toolkit book

[ #21151 ]

The surgery on my ear went well, so I've spent much of the day with a new book. It's been about a year since I've had a chance to do any serious work with the Template Toolkit, so I was quite happy when I bought Perl Template Toolkit. The book is wonderful and the examples are great. What really makes it refreshing is that this book is clearly written by experienced programmers who understand the need of laying things out properly, not duplicating code and maintaining a proper separation of concerns.

One thing I was curious about, though, was chapter 11. Try as I might, I can't quite get the hyperlinks right in the nested menus. Typing straight from their examples, I still have single menu items getting forced into their own directories.

  • Home - index/index.html
  • About - about/index.html
  • News - news/index.html
  • Documentation - docs/index.html
    • - Introduction docs/index/index.html
    • - FAQ docs/faq/index.html
    • - Manual docs/manual/index.html

I assume the intent wasn't to force me to create all of those subdirectories with one file each, but for the life of me, I can't find my typo. (Maybe it's the morphine or the codeine they gave me. I'm still a bit groggy and shouldn't be coding.) I checked the errata, but no dice. Has anyone else worked through those and are you seeing the same thing?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • When I went into hospital last year, to have my cancer removed, I was able to read "Designing With Web Standards" by Zeldman. A very interesting book, and though he was preaching to the converted in me, I found it a very useful book from the business perspective.

    I personally don't like TT2, I think it's a fundamentally flawed design, but for a broken design, it's quite a powerful implementation, and with the help of the book I've been able to get quite a bit out of it. I personally like the idea of XSLT f

    -- "It's not magic, it's work..."
    • I didn't know you had cancer. Is everything OK now?

      What don't you like you about TT2? Some people don't like templating systems as a matter of preference but it sounds like your reasoning goes beyond that (hence the XSLT reference?)

      • Everything seems to be okay, but I have to live in hope it stays that way. Next Friday is my next CT scan, everything is okay at the moment, and I'm hoping that confirms it. Once that's done I'll have been a year clear, and the odds of a full, and medication free recovery increase significantly thereafter.

        I know they do their best, but there is all sorts of code mixed up with the mark-up. It's better than ASP/JSP, but I still believe it's a flawed design. For example the templates aren't valid mark-up so

        -- "It's not magic, it's work..."