Anytime i run into problems with Krang, instead of emailing the Krang mailing list, i just send an email to myself describing the problem and reply to it with "RTFM."
Accomplishes basically the same thing.;)
One of the worst things i can think of about using Krang is when you try to see what your element tree looks like. You simply cannot use Data::Dumper to inspect it, as the output is usually about 10,000 lines of info. Right now i am trying to replicate my DVD website in Krang. It's not a perfect fit for Krang, but it has allowed me to learn.
So far, what i have learned is that coding Krang is like coding Java. No where near as fun as coding Perl.
Maybe some of the filtering capabilities built into Data::Dump::Streamer will come in useful? For hairy data structures its much easier to work with than DD.
Yes, I admit DDS is my creature so im inclined to say this anyway, but resolving issues like you describe here was one of my motivations for writing it.
Krang and Data::Dumper (Score:1)
Yes, I admit DDS is my creature so im inclined to say this anyway, but resolving issues like you describe here was one of my motivations for writing it.
Re:Krang and Data::Dumper (Score:1)